Export findings
Sooner or later someone wants the findings in a spreadsheet: an auditor, a customer, or a teammate building a pivot table. The export gives them the list as you've filtered it, so you decide the question before you download the answer.
Prerequisites
findings:exporton the organizations the export covers, along withfindings:read.
Without findings:export, the button doesn't appear. That's deliberate, because bulk data leaving Dwaar is a separate decision from being able to read it.
Export the list
- Open Findings.
- Pick a tab and set your filters. The export uses the same filters as the list.
- Select Export CSV.
You should see a message with the row count, and a file named findings-YYYY-MM-DD.csv in your downloads.
What's in the file
Rows come worst first. Each row has these columns:
| Group | Columns |
|---|---|
| The finding | id, title, type, category, rule_id, severity, status, lifecycle |
| Vulnerability data | vuln_id, vuln_ids, epss, epss_percentile, kev |
| Where it is | resource_id, resource_type, resource_ref, resource_version, connection_id, org_id |
| What it's about | subject_kind, subject, package, version, path, line |
| The rest | fix, sources, first_seen_at, last_seen_at, fixed_at |
Limits and rules
- At most 50,000 rows. If your filter selects more, narrow it and export in parts, for example one resource type at a time.
- Every export is audited, and the audit entry is written before the first row. You can review exports in the audit log.
- Ignored findings stay out unless your Status filter names Ignored, the same as the list.
A findings export can include file paths, rule names and package versions, which together make a useful map of your weaknesses. Treat the file with the same care as the console itself.
Try this next
Build the export your auditor will actually ask for. Filter Status to Risk accepted, and export. You get every accepted risk in one file, which is a much shorter conversation than scrolling through the list together.