diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-10 21:10:45 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-04-10 21:10:45 +0000 |
| commit | 98692a8dd50b5325d3f846c70ec804d0a9442f55 (patch) | |
| tree | 7ec8d2d762f56e1124a846194b078c062f5de8a2 /doc/user | |
| parent | ed5add1c2f001c9bd54e664b32f212de172eca6a (diff) | |
| download | gitlab-ce-98692a8dd50b5325d3f846c70ec804d0a9442f55.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
| -rw-r--r-- | doc/user/application_security/offline_deployments/index.md | 2 | ||||
| -rw-r--r-- | doc/user/application_security/sast/index.md | 5 |
2 files changed, 4 insertions, 3 deletions
diff --git a/doc/user/application_security/offline_deployments/index.md b/doc/user/application_security/offline_deployments/index.md index 5a5f149a3bf..61b34901849 100644 --- a/doc/user/application_security/offline_deployments/index.md +++ b/doc/user/application_security/offline_deployments/index.md @@ -76,6 +76,6 @@ Each individual scanner may be slightly different than the steps described above. You can find more information at each of the pages below: - [Container scanning offline directions](../container_scanning/index.md#running-container-scanning-in-an-offline-environment) -- [SAST offline directions](../sast/index.md#gitlab-sast-in-an-offline-environment) +- [SAST offline directions](../sast/index.md#running-sast-in-an-offline-environment) - [DAST offline directions](../dast/index.md#running-dast-in-an-offline-environment) - [License Compliance offline directions](../../compliance/license_compliance/index.md#running-license-compliance-in-an-offline-environment) diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md index 3a711138a76..75afdfb5cf5 100644 --- a/doc/user/application_security/sast/index.md +++ b/doc/user/application_security/sast/index.md @@ -504,16 +504,17 @@ Once a vulnerability is found, you can interact with it. Read more on how to For more information about the vulnerabilities database update, check the [maintenance table](../index.md#maintenance-and-update-of-the-vulnerabilities-database). -## GitLab SAST in an offline environment +## Running SAST in an offline environment For self-managed GitLab instances in an environment with limited, restricted, or intermittent access to external resources through the internet, some adjustments are required for the SAST job to -successfully run. +successfully run. For more information, see [Offline environments](../offline_deployments/index.md). ### Requirements for offline SAST To use SAST in an offline environment, you need: +- [Disable Docker-In-Docker](#disabling-docker-in-docker-for-sast) - GitLab Runner with the [`docker` or `kubernetes` executor](#requirements). - Docker Container Registry with locally available copies of SAST [analyzer](https://gitlab.com/gitlab-org/security-products/analyzers) images. |