Sample finding
What a finding looks like
Every finding is built so an engineer can reproduce it in minutes and a manager can understand it in seconds.
August Cyber / Finding 001Severity: High
Every finding includes
- 01Title, severity and affected asset
- 02The exact request we sent
- 03The exact response we received
- 04The line of code that failed, when source is in scope
- 05The business impact in plain words
- 06Steps to reproduce
- 07The recommended fix
- 08Retest status
The example
- Cross-account invoice read
- User 1001 requested invoice 2002
- The API returned it with 200 OK
- Its owner was user 1002
- The lookup matched the ID without checking the owner
- Fix: check the owner before returning the record
- Retest: user 1001 denied, user 1002 still allowed
Built for two readers ›
Engineers get proof they can replay. Leaders get a clear answer to one question: what could someone have done, and is it closed now?
See what gets through.
Email us with the app, API or agent you want tested. We reply with a scope you can sign.