Read the findings list
A scanner tells you a thing is wrong. It doesn't tell you whether it's new, whether you already decided to live with it, or whether last week's fix actually held. Without that, every scan is a fresh pile of work.
Findings is the one list across all your resources, and it remembers. Each finding keeps its history from the first run that saw it to the run that stopped seeing it.
Prerequisites
findings:readon the organizations you want to see.- At least one completed scan. See Scan Center.
What the list shows
Open Findings in the left rail. Tabs across the top are categories, and All comes first. Each tab has its own columns, because a vulnerability and a leaked key need different facts: a vulnerability row shows the CVE, package and fix, and a secret row shows the rule and location.
The list is sorted worst first. Select any row to open its detail panel. On a desktop it takes half the screen to the right of the sidebar.
| Section | What it holds |
|---|---|
| Status | The status and severity, and where you change them |
| Impact | What the problem is |
| Details | Rule, Severity, EPSS, CISA KEV, Vulnerability, Weakness and Found by |
| References | The first three links, then "+N more" |
| Affected | The resource, the version and where the problem sits |
| Fix | Dwaar's recommendation, a prompt for a coding agent, and the actions you can take |
| Decisions | Waivers, severity changes, ignores and comments, with who made each, through what and why |
| Observations | What each scan run said about it, newest first, and which analyzers saw it |
| History | Found, fixed, reopened, and the scan's own severity changes |
Long sections fold. Select View more to open one, and Show less or Esc to fold it again.
Categories
| Tab | What it lists |
|---|---|
| Vulnerabilities | Known vulnerabilities in the packages and images you ship, plus malicious packages |
| Secrets | Passwords, tokens and keys in code, history, images and pipelines |
| Code quality | Weaknesses in your own code, found by static analysis |
| Licenses | Licenses that carry obligations or aren't allowed by policy |
| Provenance & signatures | Whether packages come from the repository they claim, and whether commits are signed |
| Attestations | Artifacts without a verifiable signature or build attestation, and unsafe model files |
| Skills | Agent skills and instruction files that can change how a coding agent behaves |
| Misconfiguration | Weak settings in infrastructure as code and CI workflows |
| Posture | Settings of your source control and cloud accounts that fall short of good practice |
| Privacy & PII | Personal data in code and images, and where it leaks |
| Base image freshness | Images on an outdated or end-of-life base |
Cryptography findings have no tab of their own. You'll find them under All, using the Type filter.
The console also shows Dependencies, MCPs, SBOM, IAM, Exposure and AI agent tabs. Scanners don't report these as findings yet, so they read empty. An empty tab here means nothing was reported, not that you're clean. Your packages are listed in Components.
Severity, and why there's no separate priority
Every finding has one of five severities: Critical, High, Medium, Low or Info. It reads Unknown when the tool gave none.
Findings don't carry a separate priority. Severity is the only ranking, and your team can change it. See Triage findings. Priority is a word Dwaar uses for scan runs, which wait in a queue.
Severity alone won't tell you what to fix first. So vulnerability rows add two facts from outside your environment, and they're worth more than the label:
- EPSS: the probability this vulnerability is exploited in the next 30 days.
- KEV: it's listed in CISA's Known Exploited Vulnerabilities catalogue, which means it's already being used in attacks.
A High on the KEV list beats a Critical nobody is exploiting.
Lifecycle
The Status column shows where a finding stands.
| State | What it means |
|---|---|
| New | Only the run that found it has seen it so far |
| Open | Later runs still see it |
| Reopened | It was fixed, and a run has seen it again |
| Fixed | A run of the current version looked and didn't see it |
| Waived | Someone accepted the risk or marked it a false positive |
| Ignored | A category or check setting matched it |
Watch Reopened. A finding that keeps coming back means the fix didn't reach the place that produces the problem, and no amount of re-closing will help.
Ignored findings leave the open counts and the default lists. To see them, set the Status filter to Ignored. See Ignore findings.
Try this next
Sort out your real exposure in one pass. On Vulnerabilities, set Status to Open and In current version to Yes, then read down the KEV column. That short list is where to start on Monday.