Reading a report
Every activity produces a Markdown report in a fixed shape. Knowing the shape lets you read one in a minute and judge how far to trust it.
Where to find a report
| Where | How |
|---|---|
| Dashboard | Open an assessment, then a run. The report is rendered with severity badges and, after secfoo vendor mermaid, diagrams. The run page also lets you download report.md and prompt.md. |
| Terminal | secfoo show <run-id>. Use secfoo list to find the run ID. |
| Disk | ~/.secfoo/reports/<run-id>/report.md, next to the prompt and the agent's logs. |
Start at the top: summary and risk rating
Every report opens with a short executive summary and a line like:
**Overall risk rating:** High
That's the agent's judgement of the target as a whole. It isn't simply the worst finding: one high finding in a test helper may still leave the overall rating at Medium. For Responsible AI Compliance, this line becomes the assessment's risk badge.
The register: every finding at a glance
Right after the summary comes a table of every finding, most severe first. Activities add their own columns, but each row has an ID (F1, A3, T7, D2, S1…), a short title and a severity. Use it to decide what to read in full.
| Severity | Meaning |
|---|---|
| Critical | Exploitable now with serious impact. Fix before anything else. |
| High | Serious, and likely exploitable. Fix soon; good candidates for a CI gate. |
| Medium | Real weakness with limited impact, or needing conditions to exploit. |
| Low | Hardening and hygiene. |
Each finding in detail
Below the register, each finding gets its own section headed ### [SEVERITY] ID: title, with:
unverified means it wasn't.The severity counts secfoo prints after a run, and that --fail-on gates on, come from these headings.
Activity-specific verdicts
| Activity | Look for | Values |
|---|---|---|
| Security Architecture Review | Design verdict, in the last section | Sound · Sound with conditions (conditions listed) · Not sound |
| Threat Modeling | Disposition column in the Threat Register | Mitigated · Gap · Accepted · Transferred. A Mitigated threat with test reference none is a claimed but unproven mitigation. |
| SCA | Reachability column in the Risk Register | Reachable · Conditionally reachable · Not reachable |
| Secret Scanning | Validity column in the Findings Register | Looks live (rotate now) · Unclear · Placeholder |
| Third-Party Risk | Recommendation section | Approve · Approve with conditions · Needs more documentation · Reject |
Read the coverage notes
The last section says what the agent reviewed, what it skipped or couldn't reach (a Confluence page without an MCP connection, an excluded folder, files it ran out of time for) and how confident it is. A clean report with thin coverage notes means less than one that says it read everything. At quick depth, expect the agent to say it sampled.
How far to trust it
A report is a capable reviewer's first draft, not a verdict. The briefs push agents to be honest: to write unverified instead of guessing a CWE, never to invent a CVE ID, to give each finding a location and a concrete fix, and to say what they didn't cover. secfoo computes CVSS scores itself and checks dependencies against OSV.dev rather than trusting the model. Even so:
- Check each finding against the code before acting on it, especially
Conditionalones. - Record your decision. In the dashboard you can mark a SAST finding confirmed, a false positive, or an accepted risk. See Recording risk decisions.
- Expect some variation between runs. The report's shape is fixed, but the wording isn't, and a later run may surface a finding an earlier one missed. SAST, SCA and secret findings are matched by the code they point at, not their wording, so rephrasing doesn't create duplicates.
- See exactly what the agent was asked. Each run's prompt is saved as
prompt.md, downloadable from the run page.