Skip to main content

Ignore findings

A leaked test password in a fixture isn't the same as one in production code. But a list that treats them the same teaches people to stop reading it, and that's how the real one gets missed.

Ignoring is how you keep the list worth reading. Find it at Scan Center, Configurations. There are two kinds, and they work differently.

Ignore FilesIgnore Checks
Decides byWhere the file isWhich rule raised the finding
Takes effectWhen each resource is next scannedAt once, and on later scans

Ignored findings leave the open counts and the default lists. They aren't deleted. Set the Status filter to Ignored on the findings list to see them.

Prerequisites​

findings.settings:update to change these settings. findings:read is enough to look.

Ignore Files​

There are two categories, and both are on by default.

CategoryWhat it matchesNever ignored
Tests and fixturesTest code, test data, fixtures and stubs, such as tests/, __mocks__/ and *_test.goSecrets and malicious packages
Docs and examplesDocumentation, examples, samples, demos and tutorials, and Markdown, reStructuredText, AsciiDoc and notebook filesSecrets, malicious packages and agent skills

The exceptions are the design, not an oversight. A leaked key works from a test, and CI installs test dependencies. In the docs category, instruction files for coding agents such as SKILL.md, AGENTS.md and CLAUDE.md are code for agents, so they stay visible too.

To change a category:

  1. Open Scan Center, then Configurations, then Ignore Files.
  2. Switch the category on or off. It saves at once.
  3. Rescan a resource if you want its findings updated now. Otherwise it applies when each resource is next scanned. See Rescans.

Each category shows how many current findings it's ignoring now, so you can see what you'd bring back before you do it.

Ignore Checks​

This tab has three sections.

Ignored by your team​

Checks you don't want to see anywhere.

  1. Select Add checks.
  2. Search by rule ID or title and pick the checks.
  3. Under Action, choose Ignore.
  4. Add a note saying why these checks don't apply here. Your future self will want it.
  5. Confirm.

Their findings are ignored at once, and later scans keep them ignored. Waived findings are left alone. To undo it, remove the check from this list and its findings open again.

Severity changes​

Checks whose findings all get a severity you chose. Use Add checks with the Change severity action, or do it from a finding's panel. A severity a person set on one finding still wins. Clear the change to go back to what the scanner reported.

Dwaar defaults​

Dwaar ignores some checks for every customer, because they're true but rarely worth acting on. Each one states its reason.

GroupWhy it's ignored
CloudTrail derivativesThey all follow from one missing multi-region trail, and that check reports it once
Resilience and operationsBackups, multi-AZ and support plans are reliability settings, not security posture
Unused services"Service X is not used" isn't a weakness
Network defaultsSecurity group and instance port checks carry the signal
S3 resilience, Log groups, ECS operationsCost, retention, resilience and operations choices

You don't have to agree. Search the list and switch one off to see its findings again. If your team also ignores that check, removing yours returns it to the default.

tip

The Check filter on the findings list tags these as Dwaar default, so you can tell our opinion from your team's.

What you should see​

The tab counts show how many categories are on and how many checks are ignored. A finding ignored by either kind says so in its panel, and links back to the setting that did it.

Try this next​

Look at what's being ignored before you trust it. Set Status to Ignored on the findings list and read a sample. If something there worries you, that's a setting worth turning off, and now you know before an auditor asks.