Read a report

A report is written after each test. You only ever read a published version. A draft, or a version still being reviewed, cannot be opened from the console.

​

Open a report

On the Reports tab press a row. Or open the agent and pick its Reports tab. The report opens with the toolbar at the top.

​

The sections

A report for a coding agent also has a Power check of its set-up, a Model supply chain section and Known backdoor triggers.

​

A finding

Each finding card has the title, the business impact, the rule it broke in quotes, What happened as numbered steps, Evidence as the tool calls we saw, Fix, and the OWASP LLM, OWASP Agentic and MITRE ATLAS codes. A badge says where the proof came from.

​

Levels

The level says how far the agent went.

​

Exposure bands

The band of a finding comes from its level and the rule’s level. The worst finding sets the report’s band. Caps: a finding from words alone, or one where the two judges disagree, never passes Moderate. A finding from your activity logs never passes High.

​

Automatic and reviewed reports

The Type filter on the Reports tab splits the two.

​

The AI grading notice

Every report prints: “This report was graded by AI. AI can be wrong. Treat each problem as something to check, not as a final verdict.” Read each finding’s evidence before you act on it.

​

What you will not see

• Drafts and reports still under review.
• The judges’ reasoning and the reviewer’s notes. You see the outcome only.
• DeepBlocker’s own measured cost and spending limits.
• A test conversation anywhere outside a published report.
• The attacker’s persona and goal on the test list.

​

Where to go next