summaryrefslogtreecommitdiff
path: root/doc/user/application_security/index.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2022-11-02 21:09:03 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2022-11-02 21:09:03 +0000
commit03cd2a56f32310def67fefdc34797833a5daf770 (patch)
tree1cefc8769ffc7752183cab6dd9974e259295324d /doc/user/application_security/index.md
parent983f6954d19f269a059aab1754568737d9ab6f64 (diff)
downloadgitlab-ce-03cd2a56f32310def67fefdc34797833a5daf770.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/application_security/index.md')
-rw-r--r--doc/user/application_security/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/application_security/index.md b/doc/user/application_security/index.md
index 74791c5a7d3..30db267d891 100644
--- a/doc/user/application_security/index.md
+++ b/doc/user/application_security/index.md
@@ -487,7 +487,7 @@ Security and compliance teams must ensure that security scans:
GitLab provides two methods of accomplishing this, each with advantages and disadvantages.
-- [Compliance framework pipelines](../group/manage.md#configure-a-compliance-pipeline)
+- [Compliance framework pipelines](../group/compliance_frameworks.md#configure-a-compliance-pipeline)
are recommended when:
- Scan execution enforcement is required for any scanner that uses a GitLab template, such as SAST IaC, DAST, Dependency Scanning,