50% of OWASP API Security Top 10 you already have
ISO/SAE 21434 already covers about 50% of OWASP API Security Top 10, leaving
4 of 8 controls as genuinely new work.
Already covered 0
Likely covered 4
New work 4
No control in ISO/SAE 21434
maps directly to one in OWASP API Security Top 10. Everything counted as covered is covered because both
map to the same third standard, which is what a crosswalk is, but it is an inference rather
than a lookup.
What is genuinely new work
Nothing in ISO/SAE 21434 reaches these. This is the list to scope.
OWASPAPI-4Unrestricted Resource Consumption and Sensitive Business Flows
OWASPAPI-5Server Side Request Forgery (SSRF) and Input Validation
OWASPAPI-7Improper Inventory Management and Unsafe API Consumption
OWASPAPI-8Automated Security Testing, Logging, and Monitoring
Show the 4 you already have
OWASPAPI-1Broken Object Level Authorization (BOLA) and BFLA
OWASPAPI-2Broken Authentication and Token Management
OWASPAPI-3Broken Object Property Level Authorization (BOPLA)
OWASPAPI-6Security Misconfiguration and Secure API Design
How this is calculated
Already covered means a mapping runs from a control in ISO/SAE 21434 to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition