Update set-up-vulnerability-scans.md (#3160)

This commit is contained in:
Wang Jie 2017-05-05 05:27:51 +08:00 committed by John Mulhausen
parent 9421e6e757
commit e75306d864
1 changed files with 3 additions and 3 deletions

View File

@ -25,7 +25,7 @@ If you will be allowing the Security Scanning database to update itself
automatically, make sure that the server hosting your DTR instance can access
`https://dss-cve-updates.docker.com/` on the standard https port 443.
## Get the security scanning license.
## Get the security scanning license
If your DTR instance already has a license that includes Security Scanning, skip
this step and proceed to [enable DTR Security Scanning](#enable-dtr-security-scanning).
@ -68,7 +68,7 @@ To enable security scanning in DTR:
4. Click the **Enable scanning** toggle so that it turns blue and says "on".
![](../../images/security-scanning-setup-3.png){: .with-border}
5. Next, provide a security database for the scanner. **Security scanning will not function until DTR has a security database to use.**
5. Next, provide a security database for the scanner. **Security scanning will not function until DTR has a security database to use.**
By default, security scanning is enabled in **Online** mode. In this mode,
DTR attempts to download a security database from a Docker server. If your
@ -111,7 +111,7 @@ them against a known CVE database. When new vulnerabilities are reported, Docker
Security Scanning matches the components in new CVE reports to the indexed
components in your images, and quickly generates an updated report.
Users with administrator access to DTR can check when the CVE database was last updated from the **Security** tab in the DTR **Settings** pages.
Users with administrator access to DTR can check when the CVE database was last updated from the **Security** tab in the DTR **Settings** page.
### Update CVE database - online mode