FAQ: Exclusions
Exclusions let you ignore findings or adjust their severity based on business context. For a full overview of how exclusions work, see the Exclusions documentation. For step-by-step guidance, see Create Pattern-Based Exclusions from Ignored Findings and Audit and Maintain Your Exclusions.
- [What is an exclusion?](#exclusion-definition) - [How do I decide what an exclusion should target?](#how-to-define-exclusions) - [How do I see which resources are excluded?](#view-excluded-resources) - [How can I see all exclusions affecting a specific policy?](#exclusions-per-policy) - [When does an exclusion take effect after I create or edit it?](#when-exclusions-take-effect) - [What happens when an exclusion expires or is deleted?](#exclusion-expiration-and-removal) - [What happens if two exclusions target the same finding? Who wins?](#conflicting-exclusions) - [Can I add specific findings to an existing exclusion?](#add-findings-to-an-existing-exclusion)
Exclusion Definition
An exclusion is a rule that adjusts how findings are treated by either ignoring them or changing their severity, based on defined conditions such as accounts, policies, resources, or severity.
Use exclusions to acknowledge intentional or accepted configurations while keeping visibility and auditability.
For example, if your Dev account intentionally exposes a Load Balancer is exposed to the internet, you can create an exclusion that ignores all findings from the Load Balancer is exposed to the internet policy for resources tagged env:dev.
To learn more, see: Define Exclusion.
How to Define Exclusions
Target only the findings that match a clear business case. Identify where the configuration is intentional, temporary, or lower-risk, and set the conditions needed to cover those findings.
For example, if your Dev environment intentionally uses public S3 buckets, you can target:
- The Dev account,
- The Public S3 Bucket policy,
- Resources tagged env:dev
To learn more, see Define Exclusions.
View Excluded Resources
In the Exclusions page, click the exclusion you want to review. In the slideout, open the Resources tab to see all resources that currently match the exclusion’s conditions.
This list updates after each scan cycle.
Exclusions per Policy
In the Policies page, click the policy you want to review. In the policy slideout, open the Exclusions tab to see all exclusions that target that policy, including their scope and action.
When Exclusions Take Effect
Exclusions created or updated from the Exclusions page take effect after the next scan cycle. Once the scan completes, all matching findings update based on the exclusion’s action (ignored or severity changed).
Exclusions created from the Findings page apply immediately to the selected findings, but full coverage still finalizes in the next scan.
To learn more, see Exclusions.
Exclusion Expiration and Removal
In both cases, the exclusion stops applying in the next scan cycle. Findings that were ignored or had their severity changed revert to their original state unless another exclusion still applies.
Conflicting Exclusions
When multiple exclusions target the same finding, the one with the more specific scope takes priority. If scopes are equally specific, the earlier exclusion (the one created first) applies.
Priority is evaluated separately for each action type (Ignore and Change severity). A finding can have one exclusion per action.
Priority order:
- More specific scope wins
- If scopes match, the older exclusion wins
To learn more, see Conflict Resolution.
Add Findings to an Existing Exclusion
Yes. In the Findings page, select one or more findings and choose Ignore. If the findings match an eligible exclusion, you’ll see Add to an existing exclusion as an option in the dialog.
If the option is unavailable, it means no existing exclusion is compatible with those findings. Compatibility depends on factors such as:
- Same policy
- Same scope
- Action set to Ignore
- No severity filter
- Same finding type (Cloud or IaC)
To learn more, see Create an Exclusion.