Skip to main content

Reviewing Results

The assessment report is a single scrolling page — overview metrics at the top, then the findings list. The prompt-level data lives on its own Data page, linked from the report.

Overview Metrics​

Four cards summarize the run:

  • Attack Success Rate — The overall ASR, with a View N Prompts link through to the Data page. Reads Over Refusal Rate on an Over Enforcement assessment.
  • Risk Score — An overall score with a breakdown of how many attack vectors landed at each risk level (Critical, High, Medium, Low).
  • Scenarios — How many unique adversarial scenarios ran. Click the card to open the scenarios panel.
  • Techniques — How many distinct attack techniques were applied. Click the card to open the techniques panel, which shows the technique/policy heatmap.

Below the cards, Assessment Details carries the application, version, and run date, a Verdict summarizing what was found, and a per-category donut (Security, Safety, Privacy) with each category's ASR and pass count — click a category to open its policies panel. Alongside it, ASR Change by Policy vs. Previous Assessment plots each policy against the most recent prior run of the same version, or against the source assessment for a cloned-prompts run.

Download in the page header offers Download Data CSV and Download PDF Report.

Download PDF Report saves the report as a document, not a screenshot of the page: an overview page carrying the same cards and details as above, a page listing every finding, and one page per finding with the conversation that broke through, why it did, and the mitigation and remediation steps. It is the report as of the run, so it does not change with the filters you have applied on screen. The file is named AppName_AppVersion_AssessmentName_RunDate.pdf. It is prepared when the assessment finishes, so it normally arrives at once; for an assessment that ran before this existed, the first download builds it and can take a few seconds — the menu item says Preparing PDF Report… while it does, and later downloads are immediate. The same file is attached to the email you receive when the run finishes, so you have the report without opening the platform.

Findings​

Each finding is a row in the findings list, showing its severity, ASR, the number of scenarios that broke through, and the attack techniques that succeeded (the most effective one is named; the rest collapse into a +N badge whose tooltip lists them). The metric columns share a common axis down the list, so severity, ASR, scenario counts and techniques can be scanned as a table.

Click a row to expand it for the finding's description, its Mitigation Strategy and Remediation Steps, and a View all examples link that opens the Data page filtered to that policy's unsafe prompts.

The toolbar above the list filters the findings by free-text search, by policy, and by risk level.

The Data Page​

View N Prompts on the ASR card opens the Data page — granular access to every prompt-response pair from the assessment:

  • Filterable table with columns for Session ID, Scenario, Policy (with its policy version inline), Risk Level, Result, and Prompt Count.
  • Scenario — A link icon for the attack scenario behind each session. Hover it to see the scenario name, and click it to open that scenario on the Scenarios page.
  • Filter options: free-text search, Policy, Scenario, Evaluation, Attack Technique, Risk Level, and (for comparisons) Evaluation Change. The evaluation filter offers Safe and Unsafe — or None Violative and Violative on an Over Enforcement assessment, matching the result chips in the table.
  • Download in the page header exports the full results for offline analysis. When the results carry tool calls (collected through the version's Tool Calls Mapping), the export adds a Tool Calls column listing each prompt's calls in order, marking a call that failed or that the application reported an error for.
  • Select any session row to view the complete prompt text and response beside the table. When the version has a Tool Calls Mapping, the tool calls the application made for a prompt appear between the prompt and its response, in order, each with its status. Open a call to see its arguments, its result, and any other details the application reported for it.