Ship AI
with proof,
not promises.
An independent technical assessment of your AI endpoint. 600+ adversarial tests, every finding evidenced, and a report your compliance team can file — mapped to EU AI Act Article 15, ISO 42001, NIST AI RMF and OWASP LLM Top 10.
A binder your regulator, your board and your engineers can all read.
Four artefacts. Each one stands alone — and together they cover every conversation an AI security audit needs to settle.
The Technical Assessment Report
A Technical Assessment Report is an evidenced, framework-mapped document detailing every vulnerability discovered in your AI endpoint — with severity, the exact prompt and response that triggered it, the remediation, and a clause-level mapping to OWASP LLM Top 10, ISO 42001, NIST AI RMF and EU AI Act Article 15. PDF, HTML, JSON and Markdown — ready for filing, procurement, and the board.
An evidence package on every finding
The exact prompt sent. The exact response received. The pattern or judge that flagged it. Reproducible proof — not just claims.
Severity, mapped four ways
OWASP category, EU clause, ISO control, NIST function — every vulnerability tagged across all four frameworks.
Remediation guidance, per finding
What to change, where to change it, and how to test it. Written for engineers, not auditors.
A fix-verification re-test
You patch. We retest. You get a fix rate — and the artefacts to prove it. One re-test included on every audit.
Eight attack surfaces. Six hundred ways in.
Every category in the OWASP LLM Top 10 — and the adversarial chains real attackers use to stitch them together.
One audit. Four compliance conversations.
Every finding is pre-mapped to the four frameworks that matter for AI today — so the same evidence answers the regulator, the procurement team, the security review, and the board.
EU AI Act, Article 15
Accuracy, robustness and cybersecurity for high-risk AI. Enforcement begins in 2026–2027.
ISO/IEC 42001
The recognised standard for AI management systems and governance maturity.
NIST AI RMF 1.0
The risk-management framework expected for US federal AI procurement.
OWASP LLM Top 10
The de-facto security checklist for any application built on a large language model.
A report that looks like a document, not a dashboard.
Designed to be printed, filed, and forwarded. Cover sheet, executive summary, findings ledger, evidence appendix — and a separate cross-framework mapping table for the legal team.
Every finding, on one page.
Severity, OWASP category, regulator clause, and a one-line summary — so a non-technical reader can scan the risk surface in under sixty seconds. Detail and evidence sit one page deeper.
ART. 15 · ISO 42001
Three engagements. One straight upgrade path.
Start with Discovery to map the risk. Move to Technical Compliance when it's time to file. Step to High-Assurance when stakes — or stakeholders — call for it.
Discovery
- Full vulnerability sweep across all OWASP LLM categories
- Critical & high-severity findings with summary remediation
- Executive summary (5 pages) plus findings list
- Framework mapping at the summary level
- Credit applies in full toward a Technical Compliance upgrade — upgrade lands at $6,000
Technical Compliance
- Full 600+ test suite plus adaptive escalation on critical findings
- Accuracy verification against the metrics you've declared
- Multi-framework mapping — OWASP, ISO 42001, NIST AI RMF, EU AI Act
- Full evidence package suitable for compliance filing
- Detailed engineering-grade remediation per finding
- One re-test within 30 days included
High-Assurance
- Everything in Technical Compliance, scaled to your environment
- Unlimited adaptive red-team escalation
- Industry-specific attack scenarios (finance, health, infra)
- Board-level risk narrative and remediation roadmap
- Multi-round retest cycles and forensic-grade evidence
- Direct advisory time with senior assessors
Questions we get every week.
Plain answers, written for the people who'll actually read the report — security leads, compliance officers, and the engineers on the receiving end of the remediation.
An audit before the next
board review.
Hand us an endpoint and an auth header. We hand you a report your legal team, your security team and your board can all open.