Reports
A report your board and your engineers can both use.
Every engagement ends with a document you can act on. Here is what is inside, shown with sample data.
Executive summary
Broken access control on the invoice API
Evidence
GET /api/invoices/1043 (signed in as user A)
200 OK {"customer":"user B","total":"48,200"}
Fix
- Check on the server that the invoice belongs to the signed-in account.
- Add an automated test for cross-account access.
- Use unguessable identifiers as a second layer.
Sample layout with fictional data. Real reports are confidential to each client.
Inside every report
Six parts, always in the same order
Executive summary
One page for leaders: overall risk, what matters most and what to do first.
Scope and method
Exactly what we tested, when, and how, so nothing is assumed.
Findings
Each issue with a severity, CVSS score, affected asset and real impact.
Evidence
Screenshots, requests and steps so your team can reproduce every finding.
Fixes
Clear, prioritised remediation for developers, not generic advice.
Retest results
Confirmation of what you fixed, plus a letter you can share with customers.
Severity
How we rate risk
We use the industry-standard CVSS score, then adjust for how exposed the asset really is in your business.
| Severity | CVSS score | Our suggested timeline |
|---|---|---|
| Critical | 9.0 – 10.0 | Fix immediately |
| High | 7.0 – 8.9 | Fix within days |
| Medium | 4.0 – 6.9 | Fix within weeks |
| Low | 0.1 – 3.9 | Plan a fix |
| Informational | 0.0 | Good practice |
Confidentiality
Your findings stay yours
- Reports are shared only through encrypted, access-controlled links.
- Test data from your systems is deleted or returned when the engagement ends.
- We never name clients or share findings without written permission.
Not sure where to start? Tell us in plain words.
We reply within one working day with a clear next step.
Start your request