Framework overlap

Does ISO/IEC 27010:2015 cover OWASP API Security Top 10?

You hold ISO/IEC 27010:2015 and have been told to do OWASP API Security Top 10. Here is how much overlaps, control by control.

50% of OWASP API Security Top 10 you already have

ISO/IEC 27010:2015 already covers about 50% of OWASP API Security Top 10, leaving 4 of 8 controls as genuinely new work.

Already covered 2 Likely covered 2 New work 4

What is genuinely new work

Nothing in ISO/IEC 27010:2015 reaches these. This is the list to scope.

OWASPAPI-4
Unrestricted Resource Consumption and Sensitive Business Flows
OWASPAPI-5
Server Side Request Forgery (SSRF) and Input Validation
OWASPAPI-7
Improper Inventory Management and Unsafe API Consumption
OWASPAPI-8
Automated Security Testing, Logging, and Monitoring
Show the 4 you already have
OWASPAPI-1
Broken Object Level Authorization (BOLA) and BFLA
OWASPAPI-6
Security Misconfiguration and Secure API Design
OWASPAPI-2
Broken Authentication and Token Management
OWASPAPI-3
Broken Object Property Level Authorization (BOPLA)

How this is calculated

Already covered means a mapping runs from a control in ISO/IEC 27010:2015 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