Read a security report and verify a fix
Distinguish findings from coverage gaps, inspect evidence and compare a targeted retest with the original security report.
1. Start with coverage
Check the target, environment, time and scan profile. “No findings” only makes sense alongside the checks that completed. WAF blocks, timeouts, missing identities or scenarios are not evidence of safety.
2. Inspect the evidence
Identify the affected address, detection condition, test role and expected behavior. Severity helps order findings; priority also depends on exposure and data sensitivity. Do not paste raw tokens into tickets or chat.
3. Fix and retest
Fix the cause, then repeat the original scenario using the same object and identity. Compare the new report with the original. An unreachable target does not verify a fix; retain an incomplete outcome and restore reachability.
View sample PDF and JSON reportsContinue
Security for AI-built applications · User and tenant isolation · Coverage limits
If anything gets in the way, contact support. Contact support