liveBook · Manning

API Security Top 10

As explained in Secure APIs

The OWASP Top 10 API Security Risks is a published list of the most critical and prevalent security risks specific to application programming interfaces.

The OWASP API Security Top 10 is a practical list of common, critical threats specific to application programming interfaces. It provides a mental model for recognizing API risks beyond traditional web security. section 4.0

The risks group into several recurring failure modes:

  • Weak authentication and authorization let attackers access other users’ objects, restricted operations, or administrative functions. section 4.11
  • Poor input and data controls expose hidden properties or allow mass assignment and excessive data exposure. section 4.11
  • Abused business flows, unrestricted resource consumption, server-side request forgery, misconfiguration, and unmanaged API versions expand the attack surface. section 4.11 section 5.0

A practical API failure

If user A changes an object identifier in a request and receives user B’s private data, the API has broken object-level authorization. Validate every object request against the caller’s permissions, constrain input, and use strict data models. section 4.11

How Secure APIs covers it

How deep it goes
Explains attack patterns through coding examples and practical mitigations, covering access control, configuration, and management risks.
Examples
Uses BOLA, non-admin access, scalper bots, hidden properties, old API versions, internal endpoints, and vulnerable Python servers.
What you can do after
Diagnose API vulnerability patterns and apply access controls, strict models, standard authentication, threat detection, and safer configuration.
How it connects
Connects authentication, authorization, access control, business logic, input validation, SSRF, configuration, and API attack-surface management.

Also explained in

Compare how 2 books explain API Security Top 10 →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.