Interactive Pentest Report Sample
See how a pentest finding becomes work your team can act on: affected scope, request and response evidence, impact, and remediation context. Explore the tabs using fictional example data.
Interactive sample · Fictional data · No target traffic
Assessment / PT-042 · illustrative
Review scope, findings, and follow-up.
Scope: app.example.test · authorized lab scenario
Sample finding / F-007
Inspect the request behind the finding.
GET /api/projects/42 HTTP/1.1 Host: app.example.test Authorization: Bearer [sample-redacted] HTTP/1.1 200 OK {"project_id":42,"owner":"sample-user-b"}
Illustrative observation: a sample user can access another sample user's project. This is fictional report content; no request was sent.
Sample fix verification / R-003
Compare the original evidence and retest.
F-007 · original sample response: 200 OK
Analyst note · authorization control changed
Sample response: 403 Forbidden · no live retest ran
Give your team the context to act
A severity label tells only part of the story. Follow the affected flow, inspect the request and response, and understand the conditions behind the finding. That context helps an analyst validate impact and a developer plan the fix.
What does one free high-severity finding include?
Your first scan is free. If it identifies high-severity vulnerabilities, one complete high-severity finding is included at no cost—with evidence and remediation guidance. Use evidence from your own authorized target to judge how the workflow fits your team.
The free first-scan offer is planned and redemption is not open yet. Create a workspace and explore the sample report while you evaluate the workflow.
Make the next review easier
The Retest tab shows the original observation beside a separate remediation conclusion. See how the format helps your team keep the finding and the follow-up connected.