From 8f21139c1cdcfb8b26fbb3b6868808f019fdc4da Mon Sep 17 00:00:00 2001 From: Anish Malhotra Date: Mon, 13 May 2024 15:30:04 -0400 Subject: [PATCH 1/2] Update change-vulnerability-status.mdx Legal recommended changes --- .../change-vulnerability-status.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/content/docs/vulnerability-management/change-vulnerability-status.mdx b/src/content/docs/vulnerability-management/change-vulnerability-status.mdx index c7fd1b0c794..51d280e8bd2 100644 --- a/src/content/docs/vulnerability-management/change-vulnerability-status.mdx +++ b/src/content/docs/vulnerability-management/change-vulnerability-status.mdx @@ -32,11 +32,13 @@ import vmAffectedBulkDetails from 'images/security_screenshot-affected-bulk-deta import vmAffectedBulkForm from 'images/security_screenshot-affected-bulk-form.webp' -New Relic Vulnerability Management may detect an overwhelming amount of vulnerabilities across your system. Most of these vulnerabilities may need remediation, but many might be low risk, or have limited external exposure. You can manage your vulnerabilities by: +New Relic Vulnerability Management may detect a good amount of vulnerabilities across your system. Most of these vulnerabilities may need remediation, but some might be not be applicable to your environment or your internal policies might categorize them as low risk, or limited exposure due to how your systems leverage the potentially vulnerable component. -* Assigning individual entities the `Ignored` status so their vulnerabilities no longer appear in Vulnerability Management +Understanding that you may want to tailor your visibility by entity or criticality, New Relic Vulnerability Management allows you to manage your vulnerabilities by: + +* Assigning individual entities to an `Ignored` status so their vulnerabilities no longer appear in Vulnerability Management * Ignoring a certain kind of vulnerability in bulk so it no longer appears across multiple entities -* Removing the `Ignored` status at a later date if you want to detect those vulnerabilities again +* Removing the `Ignored` status at a later date if you want to view and review those vulnerabilities again ## Ignore a vulnerability [#ignore-vulnerability] @@ -189,7 +191,7 @@ Before you assign `Ignored` to a vulnerability or entity, it's important to unde * You can surface `Ignored` vulnerabilities with the filter bar. From the filter bar, you can add `Status = Ignored` to view `Ignored` vulnerabilities. * From the the **Vulnerabilities** table, select **Ignored** to surface ignored vulnerabilities. -At minimum, we recommend reviewing your vulnerabilities every 90 days to ensure you aren't introducing risk into your system. +At a minimum, we recommend reviewing your vulnerabilities every 90 days to ensure you aren't introducing risk into your system. ## Why ignore a vulnerability? [#why-ignore] From 7d6a498704689cfc58774bfb8bd8257c836610f1 Mon Sep 17 00:00:00 2001 From: jcol <116673918+jeff-colucci@users.noreply.github.com> Date: Mon, 13 May 2024 15:48:25 -0500 Subject: [PATCH 2/2] Update change-vulnerability-status.mdx Minor grammar fix --- .../vulnerability-management/change-vulnerability-status.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/vulnerability-management/change-vulnerability-status.mdx b/src/content/docs/vulnerability-management/change-vulnerability-status.mdx index 51d280e8bd2..fd785b798e5 100644 --- a/src/content/docs/vulnerability-management/change-vulnerability-status.mdx +++ b/src/content/docs/vulnerability-management/change-vulnerability-status.mdx @@ -32,7 +32,7 @@ import vmAffectedBulkDetails from 'images/security_screenshot-affected-bulk-deta import vmAffectedBulkForm from 'images/security_screenshot-affected-bulk-form.webp' -New Relic Vulnerability Management may detect a good amount of vulnerabilities across your system. Most of these vulnerabilities may need remediation, but some might be not be applicable to your environment or your internal policies might categorize them as low risk, or limited exposure due to how your systems leverage the potentially vulnerable component. +New Relic Vulnerability Management may detect a good amount of vulnerabilities across your system. Most of these vulnerabilities may need remediation, but some might be not be applicable to your environment, or your internal policies might categorize them as low risk or limited exposure due to how your systems leverage the potentially vulnerable component. Understanding that you may want to tailor your visibility by entity or criticality, New Relic Vulnerability Management allows you to manage your vulnerabilities by: