Skip to main content

Review decisions on findings

Your open count dropped by forty last month. Was that fixes, or did someone accept the risk? And if an AI agent did it, what did it look at?

Findings › Decisions answers that. It lists every decision made on the findings in your organization scope, newest first, with who made it, through what and the reason they gave. Fixes aren't here, because a scan proves those. Everything a person or an agent decided is.

Prerequisites​

  • findings:read on the organizations whose findings you want to see. The page shows decisions only on those.
  • findings:export as well, to download the report.

Open the page​

Open Findings in the left rail, then Decisions under it. The page is at /findings/decisions.

The Decisions page searched for "Compensating": tiles for Waived (28, 15 by AI agents) and the other kinds, then rows of waived findings, each with when, the decision, the finding and its rule, the resource, the reason, and who made it through Console or AI agent (MCP).

Tiles across the top count each kind of decision in the period you chose. Where AI agents made some of them, the tile says how many.

TileWhat it counts
WaivedFindings marked accepted risk or a false positive
Severity changedSeverities set or cleared on one finding
Waivers revokedWaivers someone ended before they expired
IgnoredFindings a Finding Configuration or a check setting ignored
No longer ignoredFindings that came back when such a setting was turned off
CommentsComments added to a finding

What each row shows​

ColumnWhat it holds
WhenThe date and time of the decision
DecisionWhat changed, in words, such as "Severity lowered from Medium to Low" or "Risk accepted until 12 Feb 2027"
FindingThe finding's title
ResourceThe resource the finding is on
WhyThe reason given, or the comment's text
ByThe person, or Dwaar for the scan pipeline, with a badge for how the decision was made

The badge in By tells you through what the decision came:

BadgeMeaning
ConsoleA person, in the console
AI agent (MCP)An AI agent connected to the MCP server, with the name of its API key, such as "Claude Code (MCP)"
API keyA script or pipeline calling the REST API with an API key
DwaarThe scan pipeline, for example when a check setting ignored a finding

Select a row to open the finding. Its Decisions section shows the same decision next to the finding's other decisions and comments.

Narrow the list​

ControlUse it to
Decision filterShow only waivers, severity changes, comments or another kind
Through filterShow only Console, AI agent (MCP), API key or Dwaar
Resource type filterStay within code, artifacts or cloud
SearchFind a finding, rule or reason
PeriodShow the last 7 days, 30 days, 90 days or All. The default is All.

Export the report​

  1. Set the filters and the period you want.
  2. Select Export CSV.

You should see a message with the row count, and a file named finding-decisions-YYYY-MM-DD.csv in your downloads.

GroupColumns
The decisionat, decision, from, to, reason, expires_at
Who made itby, via, credential
The findingfinding_id, finding_title, rule_id, vuln_id, severity_now, status_now
Where it isresource_id, resource_name, resource_type, org_id

via is console, mcp, api or pipeline, and credential names the API key when there was one. The file holds at most 50,000 rows. Every export is recorded in the audit log.

The audit log has them too​

Every change and comment is also in the audit log, at Settings › Security, with the API key as the credential and mcp, api or console as the way it came in. A comment's text isn't copied into the audit log, only its length. Read the text here or on the finding.

Try this next​

Check what your agents decided. Set Through to AI agent (MCP) and Period to 30 days, and read the Why column. Each reason should name what the agent looked at and what it found. If one doesn't convince you, open the finding and set its Status or severity back, with your own reason.