Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Update): Legal recommended changes to change-vulnerability-status.mdx #17288

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -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]

Expand Down Expand Up @@ -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]

Expand Down
Loading