summaryrefslogtreecommitdiff
path: root/doc/user/application_security/container_scanning/index.md
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2019-06-19 12:15:05 +0200
committerAchilleas Pipinellis <axil@gitlab.com>2019-06-26 16:56:11 +0200
commite49f7905c18d266554d56e21733d4caf5e4a2072 (patch)
tree313c801f2967ff18efae4bd17f252412ac213eea /doc/user/application_security/container_scanning/index.md
parent8db4a54df0d57399e7bfd1723a16639862ca456c (diff)
downloadgitlab-ce-e49f7905c18d266554d56e21733d4caf5e4a2072.tar.gz
Document the security tools maintenance and vulnerabilities DB updatedocs/secure-maintenance
Addresses the following questions: - How often do we update the vulnerability DB or analyzers? - Do we have to update GitLab to benefit from latest vulnerabilities definitions?
Diffstat (limited to 'doc/user/application_security/container_scanning/index.md')
-rw-r--r--doc/user/application_security/container_scanning/index.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/user/application_security/container_scanning/index.md b/doc/user/application_security/container_scanning/index.md
index 4a2fb1d7190..9dfbe326f1d 100644
--- a/doc/user/application_security/container_scanning/index.md
+++ b/doc/user/application_security/container_scanning/index.md
@@ -206,6 +206,11 @@ vulnerabilities in your groups and projects. Read more about the
Once a vulnerability is found, you can interact with it. Read more on how to
[interact with the vulnerabilities](../index.md#interacting-with-the-vulnerabilities).
+## Vulnerabilities database update
+
+For more information about the vulnerabilities database update, check the
+[maintenance table](../index.md#maintenance-and-update-of-the-vulnerabilities-database).
+
## Troubleshooting
### docker: Error response from daemon: failed to copy xattrs