> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions-new.md).

# Monitoring Exclusions

## About exclusions

The Exclusions page is used to review and manage exclusions that have already been defined. To create a new issue exclusion, start from the issue on the Active Issues page.

You can use the filters and search on the Exclusions page to find exclusions by properties such as issue name, application name, policy, or exclusion type. These options filter existing exclusions; they do not define the matching criteria for a new exclusion.

<figure><img src="/files/bAhfpyYcLIpvwyyfs1gV" alt=""><figcaption></figcaption></figure>

It is commonly used to review all active exclusions before a compliance or security audit, identify long-lived exclusions that may require re-evaluation, track temporary (snoozed) exclusions and their expiration dates, and understand why certain issues do not appear in active findings.

The Exclusions page allows you to understand why an issue does not appear in active findings, who excluded it and when, whether the exclusion is permanent or temporary, and what matching logic is used.

The Exclusions page shows both fully-excluded issues and partial exclusions (where only some of an issue's aggregations were excluded).

This page is read-only and is intended for audit, review, and governance purposes. You can [define exclusions in the Active Issues page.](/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions-new/defining-exclusions.md)

### How exclusions work

You define an exclusion from an existing issue in Active Issues. OX uses the selected issue to determine the available exclusion scopes. You do not manually create an exclusion by entering an issue name, application name, or other matching criteria.

Depending on the finding, you can exclude:

* Only the selected issue.
* Issues generated by the same detection rule in the current application.
* Issues generated by the same detection rule across all applications.

The available exclusion scopes depend on the selected finding. Some findings support only issue-level exclusion.

For instructions on creating an exclusion and selecting its scope, see [Defining exclusions](/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions-new/defining-exclusions.md).

### Choosing what to exclude

OX provides different ways to exclude findings or content from security analysis, depending on what you want to remove from scope.

| If you want to...                                    | Use                                                       |
| ---------------------------------------------------- | --------------------------------------------------------- |
| Exclude one specific finding                         | **Exclude this issue only**                               |
| Exclude a detection rule for one application         | **Exclude the detection rule in this application**        |
| Exclude a detection rule across the organization     | **Exclude the detection rule in all applications**        |
| Temporarily exclude a finding                        | **Snooze** or set an expiration date for the exclusion    |
| Remove an application from scanning                  | **Make App Irrelevant**                                   |
| Prevent a policy from generating issues              | **Disable Policy**                                        |
| Prevent specific files or folders from being scanned | Configure **Exclude from Scan** under **Settings > Scan** |

## Exclusions table

The table lists all exclusions that match the current filters.

<table><thead><tr><th width="174">Column</th><th>Description</th></tr></thead><tbody><tr><td>Type</td><td>Indicates the category of the excluded issue, such as code, secret, or cloud.</td></tr><tr><td>Issue</td><td>The name of the excluded issue.</td></tr><tr><td>App Name</td><td>The application or cloud account where the exclusion applies.</td></tr><tr><td>Match</td><td>The logic used to apply the exclusion, such as file paths, resource identifiers, rule IDs, or code locations.</td></tr><tr><td>Count</td><td>Number of occurrences affected by the exclusion.</td></tr><tr><td>Excluded By</td><td>The user who created the exclusion.</td></tr><tr><td>Comment</td><td>Indicates whether a comment was added when the exclusion was created.</td></tr><tr><td>Snooze Till</td><td>Shows the expiration date for temporary exclusions.</td></tr><tr><td>Applied Date</td><td>The date the exclusion was applied.</td></tr></tbody></table>

## Filters and search

You can narrow down the list of exclusions using the filters panel or the search bar.

<figure><img src="/files/F8rxszhBUVizZGKzszwQ" alt=""><figcaption></figcaption></figure>

| Filter         | Description                                            |
| -------------- | ------------------------------------------------------ |
| App Name       | Filters exclusions by application or cloud account.    |
| Exclusion Type | Filters by the type of excluded issue.                 |
| Issue Name     | Filters by issue name.                                 |
| Created By     | Filters exclusions by the user who created them.       |
| Policy Name    | Filters exclusions originating from a specific policy. |

The search bar supports free-text search by issue name or application name.

## Managing exclusions

Although exclusions are created elsewhere in the platform, as explained in [Defining Exclusions](/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions-new/defining-exclusions.md), they can be managed from the Exclusions page.

Select the exclusion(s) you want to manage and click the three dots on the right.

<figure><img src="/files/cWFJiU2kR9a7W1pRDjcU" alt=""><figcaption></figcaption></figure>

Each exclusion row includes an actions menu. Available actions depend on the exclusion type, its current state, and your permissions.

| Action                        | Description                                                               |
| ----------------------------- | ------------------------------------------------------------------------- |
| Remove Exclusion              | Deletes the exclusion. The issue is evaluated again in future scans.      |
| Update Exclusion Expiry Date  | Updates the expiration date of a temporary exclusion.                     |
| Remove Snooze                 | Removes the time limit from a snoozed exclusion.                          |
| Make App Relevant: Always     | Marks the application as always relevant for evaluation, when applicable. |
| Make App Relevant: OX Dynamic | Restores dynamic relevance evaluation for the application.                |
| Enable Policy                 | Re-enables the policy associated with the exclusion, when relevant.       |

Actions that are not applicable to a specific exclusion appear disabled.

### Reviewing excluded issues in the Removed Issues page

The Exclusions page lists only the metadata for each exclusion. To see the excluded issue details, open the [Removed Issues](/scan-and-analyze-with-ox/analyzing-scan-results/resolved-issues.md#removed-issues) page and filter by Removed Reason.

## Related topics:

[Defining exclusions](/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions-new/defining-exclusions.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ox.security/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions-new.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.