---
title: Manage cloud misconfiguration status
source: https://docs.newrelic.com/docs/vulnerability-management/cloud/manage-misconfiguration-status
---

New Relic Security RX Cloud can detect misconfigurations across your cloud resources. While most misconfigurations need remediation, some might not be applicable to your environment. For example, your internal policies might categorize them as low risk or limited exposure due to how your cloud resources are configured or used.

For misconfigurations you're not interested in tracking, you can set the **Status** to **Ignored** so they no longer appear in the UI. Since each misconfiguration is tied to one or more cloud resources, you can:

-   Ignore individual misconfigurations for a specific resource
-   Ignore a misconfiguration that appears across multiple resources

You can always change the status from **Ignored** back to **Affected** if you decide a misconfiguration is worth tracking again.

> #### 💡 TIP
>
> Before you ignore a misconfiguration, keep in mind that this change prevents other users with account access from seeing that misconfiguration.

## Ignore a misconfiguration [#ignore-misconfiguration]

When you choose to ignore a misconfiguration, you'll be prompted to explain the rationale behind the decision. For example, you might say that the resource is not exposed to the internet or that compensating controls are in place. We recommend that when you give this context, you also provide supplemental documentation when possible.

You'll also be prompted to set a duration for the **Ignored** status. Security RX Cloud will automatically change it from **Ignored** to **Affected** when the time period expires. If a misconfiguration is already **No Longer Detected**, the status will remain no longer detected.

**Ignore a misconfiguration for a specific resource**

You can manually ignore misconfigurations for specific resources. Once you set the status to **Ignored**, we'll exclude this from the summary tiles and misconfiguration list by default. Other instances of this misconfiguration on other resources will still keep the **Affected** status.

1.  Go to **[one.newrelic.com](https://one.newrelic.com/) > All capabilities > Security RX > Cloud**
2.  Click the **Misconfigurations** tab
3.  Select the misconfiguration you want to review
4.  In the **Area of Impact** section, find the specific resource you want to ignore
5.  Select the resource
6.  Click the **Change to ignored** button
7.  Fill out the form to explain the reasoning behind ignoring this misconfiguration, including a time period

**Ignore a misconfiguration across multiple resources**

1.  Go to **[one.newrelic.com](https://one.newrelic.com/) > All capabilities > Security RX > Cloud**
2.  Click the **Misconfigurations** tab. By default, this view filters to misconfigurations where at least one resource is marked **Affected**
3.  Choose the misconfiguration you want to ignore
4.  In the **Area of Impact** section, select each resource you want to ignore
5.  Click the **Change to ignored** button
6.  Fill out the form to explain the reasoning behind ignoring this misconfiguration, including a time period

## Restore ignored misconfigurations [#restore-ignored]

It's good practice to review ignored misconfigurations and validate whether they should stay ignored. We recommend reviewing your misconfigurations every 90 days to ensure you aren't introducing risk into your cloud environment.

If you change the status from **Ignored** to **Affected** for a specific resource, that reintroduces the misconfiguration into default views and counts against this resource. Instances of this misconfiguration on other resources remain ignored.

**Remove ignored status for a specific resource**

1.  Go to **[one.newrelic.com](https://one.newrelic.com/) > All capabilities > Security RX > Cloud**
2.  Click the **Misconfigurations** tab
3.  Update the filter from **Status = Affected** to **Status = Ignored**. This displays all ignored misconfigurations
4.  Choose the misconfiguration you want to update
5.  In the **Area of Impact** section, select the resource you want to update
6.  Click **Change to affected**
7.  Fill out the form to explain the reasoning behind changing this misconfiguration to **Affected**

**Remove ignored status across multiple resources**

1.  Go to **[one.newrelic.com](https://one.newrelic.com/) > All capabilities > Security RX > Cloud**
2.  Click the **Misconfigurations** tab
3.  From the settings cog, click the **Ignored** checkbox. This adds an ignore column to your misconfiguration table
4.  Select a misconfiguration with an **Ignored** count greater than 0
5.  Update the filter from **Status = Affected** to **Status = Ignored**
6.  In the **Area of Impact** section, select the resources you want to mark **Affected**
7.  Click **Change to affected**
8.  Fill out the form to explain the reasoning behind changing this misconfiguration to **Affected**

## What's next?

[Set up alerts](https://docs.newrelic.com/docs/vulnerability-management/advanced/set-up-alerts)

Get notified when cloud misconfigurations are detected

[Query security data](https://docs.newrelic.com/docs/vulnerability-management/advanced/query-examples)

Track status changes and remediation metrics with NRQL

[Understand prioritization](https://docs.newrelic.com/docs/vulnerability-management/cloud/prioritization)

Learn how cloud misconfigurations are ranked by risk

[Manage cloud misconfigurations](https://docs.newrelic.com/docs/vulnerability-management/cloud/manage-cloud-security)

View and manage cloud misconfigurations across your organization