Pentests

Pentests is your record of penetration tests and security scans: who ran them, when, what they covered and how many issues of each severity they found. It is a register of results you can show an auditor or customer. It is not a findings feed.

Find it under Risk → Pentests. The page itself is titled Pentest Reports.

A pentest report records counts of issues by severity. The individual issues from a test are not turned into findings or actions. Track the remediation of a test's issues in your own tracker or as actions you create, and link the report for evidence.

The report list

Each row shows the report's name (or the provider's name when it has none), the provider, the scan date, a status pill and a pill for how it arrived: Manual or API. On the right, a pill per severity shows the number of issues, for example 2 High, from Critical down to Low. The sort options are Newest Scan, Oldest Scan and Recently Added.

Statuses

Status Meaning
ScheduledThe test is booked but has not started.
In progressThe test is under way.
CompletedThe test is finished and the results are in.

Adding a report

People who can make changes (owners, admins and members) see Add Manually at the top of the page. Viewers can read reports but not add them. It opens Add Pentest Report:

  • Provider: who ran the test, for example "CrowdStrike". It starts as "manual".
  • Scan Date: required.
  • Name: for example "Q1 2026 Application Pentest".
  • Scope: what was tested, for example "Production web application".
  • Summary: a short summary of the result.
  • Status: Scheduled, In progress or Completed (starts as Completed).
  • Findings: the number of Critical, High, Medium and Low issues. The report's total is the sum of these four.

Choose Add Report.

From a testing tool

Quant Sentinel and other tools can submit reports for you using an API key. Those reports arrive marked API (Via API on the report) and can carry a status, a link to the full report and extra details. See the API reference.

A report's page

Select a report to see it. The header shows its status, whether it came by API or manual entry, the provider and the scan date. Below are tiles for Total, Critical, High, Medium and Low, then the report's Scope and Summary when present, a Detailed Report link (View Full Report) when the submission included one, and a Metadata card for any extra details a tool supplied.

People who can make changes can correct a report with Edit Report, which opens the same form with the report's values, for example to move a test from Scheduled to Completed and enter its counts. They can also remove a report with Delete Report, after a confirmation. Deleting cannot be undone.

Showing reports to customers

Pentest reports can be published on your Trust centre as evidence of your security testing. Choose which ones under Settings → Trust centre. Only reports you select are shown, with the provider, name, date, scope and counts.

How pentests connect to the rest of QuantAssure

  • Trust centre. Published reports appear there, as above.
  • Audit log. A submitted report is recorded in the audit log with how it arrived.
  • Findings, risks and compliance. There is no automatic link. Reports are standalone evidence.
  • AI. No AI agent reads or scores pentest reports.