OWASP API Security Top 10
OWASP’s ranked list of the ten most critical security risks specific to APIs, last updated in 2023.
In more detail
It is led by broken object level authorization and includes broken authentication, unrestricted resource consumption and security misconfiguration, which map closely to the boundary checks an API contract should include. Use it as a checklist for design reviews and tests, not as a complete list of everything that can go wrong.
Related terms
- OWASP — The Open Worldwide Application Security Project, a non-profit community that publishes free guidance on software security, such as the Top 10 lists and cheat sheets.
- broken object level authorization — An API flaw where changing an identifier in a request, such as /tasks/2 instead of /tasks/1, lets a caller reach an object that belongs to someone else.
- resource exhaustion — Running a service out of memory, time, connections or money by making it do unbounded work, whether by accident or on purpose.
- vulnerability — A weakness in software or configuration that an attacker could use to cause harm.
- broken object property level authorization — OWASP's name for letting a caller read or write individual fields of an object they may access but should not see or change.
- unrestricted resource consumption — OWASP's name for APIs that let callers spend unlimited processor time, memory, connections, rows or money.
Taught in
- Security Best Practices — Modern API Architecture: REST, GraphQL & gRPC
- Broken Object Level Authorization — Application Security & Threat Modeling for Engineers
- Mass Assignment — Application Security & Threat Modeling for Engineers
- Rate Limiting And Resource Consumption — Application Security & Threat Modeling for Engineers