Keep the investigation with the finding
Review the impact, reproduction steps and remediation when available. The record keeps the result connected to its context.
Findings and evidence
See the proof. Decide the next step.
Bring the observation, supporting evidence and suggested fix into one record your team can inspect.
Example findingVerified
Object-level access control
Tested scenarioCross-account access
- Observation
- A report is returned to a different test account.
- Evidence
- Request, response and reproduction steps.
- Remediation
- Check ownership before returning the report.
More context. A clearer handoff.
Evidence is useful when the next person can understand what happened.
VerifiedEvidence supports the finding
Needs reviewA person needs to assess it
PendingVerification is still in progress
Know what has been verified
Confirmed findings stay distinct from results that need manual review or are still being checked.
A handoff for the people who need to act.
Illustrative report outline
Application security review
- Summary
What was tested and what needs attention.
- Scope and method
The targets, access and tested conditions.
- Findings and evidence
Impact, reproduction and remediation.
Choose the findings that belong in the report
Select relevant records and keep the scope, method and supporting evidence with the narrative.
Write for your audience
Edit sections yourself or ask AI to refine them. Protect sections you want to keep unchanged, and review the saved revision as a PDF.
Review before sharing
Evidence inclusion and redaction options help prepare the document. Check the final PDF for confidential or personal information before it leaves your team.
Follow a finding through to the fix.
See an example investigation and the evidence your team would review.