04Evidence and proof
Evidence your security team can verify.
Every result records what was tested, when, and what was not covered.
- Human-reviewed findings A person reviews every finding and its severity before it is reported.
- Reproducible evidence Evidence references your engineers can follow and re-test.
- Scope and limitations A record of what was in scope, and what testing could not cover.
- Dated, versioned records Results tied to the date and the version of the system that was checked.
- Signed proof verification Where supported and approved, anyone can verify a signed proof without seeing client findings.
A proof is not a certification and does not guarantee security. Automated platform checks complement, and do not replace, an independent penetration test.
Methods and reports reference OWASP Top 10 for LLM Applications, MITRE ATLAS, NIST AI RMF, ISO/IEC 42001, ISO/IEC 27001, UK GDPR and the EU AI Act. Framework alignment →
Alignment means our methods and reports reference these frameworks. It is not a certification, and an assessment does not by itself make a system compliant.