OWASP API Security Top 10: every control, and what you already have

8 controls 103 frameworks share controls with it International verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

OWASP API Security Top 10 2023 Evidence & Implementation Kit

8 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you run	Shared controls
FDA 21 CFR Part 11	4	measure it →
FedRAMP Rev 5	4	measure it →
FISMA	4	measure it →
Ghana Cybersecurity Act	4	measure it →
HL7 FHIR Security Framework	4	measure it →
ISMAP (Japan)	4	measure it →
ISO/IEC 27400:2022	4	measure it →
MARS-E	4	measure it →
MDS2 (Medical Device)	4	measure it →
MITRE ATT&CK	4	measure it →
MITRE D3FEND	4	measure it →
MTCS (Singapore)	4	measure it →

Every control

Code	Control	Also in
`OWASPAPI-1`	Broken Object Level Authorization (BOLA) and BFLA	78
`OWASPAPI-2`	Broken Authentication and Token Management	45
`OWASPAPI-3`	Broken Object Property Level Authorization (BOPLA)	40
`OWASPAPI-4`	Unrestricted Resource Consumption and Sensitive Business Flows	0
`OWASPAPI-5`	Server Side Request Forgery (SSRF) and Input Validation	0
`OWASPAPI-6`	Security Misconfiguration and Secure API Design	86
`OWASPAPI-7`	Improper Inventory Management and Unsafe API Consumption	0
`OWASPAPI-8`	Automated Security Testing, Logging, and Monitoring	0

Tell me when OWASP API Security Top 10 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for OWASP API Security Top 10, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition