From e5dd8135e0ab8dc60d71f9d6b33a61ad0456f2d6 Mon Sep 17 00:00:00 2001 From: Nikhil George <ngeorge@gitlab.com> Date: Thu, 6 Mar 2025 13:40:06 +0000 Subject: [PATCH] Update file vulnerability_management_policy.md --- .../policies/vulnerability_management_policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/application_security/policies/vulnerability_management_policy.md b/doc/user/application_security/policies/vulnerability_management_policy.md index 20860d163e8be..72bc3172b1506 100644 --- a/doc/user/application_security/policies/vulnerability_management_policy.md +++ b/doc/user/application_security/policies/vulnerability_management_policy.md @@ -33,7 +33,7 @@ consistently. For example, you can create a policy that marks as resolved those are no longer detected on the default branch, but only those created by SAST and are of low risk. The vulnerability management policy is applied when a pipeline runs against the default branch. -For each vulnerability that is no longer detected and matches the policy's rules: +For each vulnerability that is no longer detected by the same scanner and matches the policy's rules: - The vulnerability record's status is set to **Resolved** by the **GitLab Security Policy Bot** user. -- GitLab