# SP-030 API Security

Status: active. Release 26.10. Modified 2026-10-08. Licence: CC BY-SA 4.0.

Scope: Security pattern for APIs across their lifecycle. Maps 47 NIST 800-53 controls to authentication, authorisation, input validation, rate limiting, transport security, API inventory and monitoring, and traces them to the OWASP API Security Top 10.
Use when: Use this pattern wherever the organisation publishes or consumes APIs. It matters most for public APIs used by third-party developers, mobile apps on REST or GraphQL, microservices with heavy service-to-service traffic, open banking and PSD2, partner integrations, and IoT fleets.
Not when: It is overhead for an internal monolith that exposes no APIs, and of little use where integration is file-based only (SFTP, batch).

## Controls (47, NIST SP 800-53 ids)
- Critical (14): AC-03, AC-04, AC-06, AC-07, AU-02, CA-07, CM-08, IA-02, IA-05, IA-09, SC-07, SC-08, SI-04, SI-10
- Important (25): AC-12, AC-17, AC-20, AC-21, AU-03, AU-06, AU-12, CA-02, CM-02, CM-03, CM-07, IA-04, IA-08, IR-04, IR-05, PL-08, RA-03, RA-05, SA-08, SA-11, SC-05, SC-13, SC-23, SI-11, SI-15
- Standard (8): AC-10, AT-02, AT-03, SC-06, SC-28, SI-03, SR-02, SR-03

## What each critical control mitigates (14)
- AC-03 Access Enforcement: T-API-002, T-API-004, T-API-006
- AC-04 Information Flow Enforcement: T-API-002, T-API-003, T-API-004, T-API-006, T-API-007
- AC-06 Least Privilege: T-API-002, T-API-004, T-API-006
- AC-07 Unsuccessful Logon Attempts: T-API-001, T-API-005, T-API-012
- AU-02 Event Logging: T-API-005, T-API-012
- CA-07 Continuous Monitoring: T-API-010, T-API-012
- CM-08 System Component Inventory: T-API-008, T-API-010
- IA-02 Identification and Authentication (Organizational Users): T-API-001
- IA-05 Authenticator Management: T-API-001, T-API-011
- IA-09 Service Identification and Authentication: T-API-008, T-API-009
- SC-07 Boundary Protection: T-API-003, T-API-005, T-API-007, T-API-012
- SC-08 Transmission Confidentiality and Integrity: T-API-009
- SI-04 System Monitoring: T-API-001, T-API-002, T-API-003, T-API-004, T-API-005, T-API-006, T-API-008, T-API-011, T-API-013
- SI-10 Information Input Validation: T-API-003, T-API-006, T-API-007, T-API-012

## Threats and the controls that mitigate them (13)
- T-API-001 Broken authentication and credential stuffing: AC-07, IA-02, IA-04, IA-05, IA-08, SI-04
- T-API-002 Broken object level authorization (BOLA/IDOR): AC-03, AC-04, AC-06, AU-06, SI-04
- T-API-003 Injection attacks via API parameters: AC-04, SC-07, SI-03, SI-04, SI-10, SI-11
- T-API-004 Excessive data exposure in API responses: AC-03, AC-04, AC-06, AU-06, SI-04, SI-15
- T-API-005 Rate limiting bypass and API abuse: AC-07, AC-10, AC-12, AU-02, SC-05, SC-06, SC-07, SI-04
- T-API-006 Mass assignment and parameter tampering: AC-03, AC-04, AC-06, CM-02, SA-08, SI-04, SI-10
- T-API-007 Server-side request forgery via API input: AC-04, SC-07, SI-03, SI-10
- T-API-008 Third-party API supply chain compromise: AC-20, CM-08, IA-09, SA-11, SI-04, SR-02, SR-03
- T-API-009 Man-in-the-middle on API traffic: IA-09, SC-08, SC-13, SC-23
- T-API-010 Shadow API and zombie API exposure: CA-07, CM-02, CM-03, CM-07, CM-08, RA-05
- T-API-011 Token theft and replay attacks: AC-12, IA-05, SC-23, SI-04
- T-API-012 API denial of service via resource exhaustion: AC-07, AC-10, AC-12, AU-02, CA-07, SC-05, SC-06, SC-07, SI-10
- T-API-013 Exploit hardware or platform vulnerabilities: CM-07, RA-05, SI-04

## More
- The critical controls and what each mitigates, as JSON (a few KB): /api/v1/patterns/SP-030/crosswalk?emphasis=critical
- The same for every control, with its clauses in a framework: /api/v1/patterns/SP-030/crosswalk?framework={framework id}. Framework ids are listed in /llms.txt
- The pattern's prose, examples and references as JSON, 40 KB: /api/v1/patterns/SP-030
- Page for people: /patterns/sp-030/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.
- Built a pattern? Report it at https://github.com/opensecurityarchitecture/osa-data/issues/new?template=implementation-report.md with what you built, how you tested it and what the pattern should say.
- Related: SP-002 Server Module; SP-004 SOA Publication and Location Pattern; SP-005 SOA Internal Service Usage Pattern; SP-008 Public Web Server Pattern; SP-011 Cloud Computing Pattern; SP-016 DMZ Module; SP-028 Secure DevOps Pipeline; SP-029 Zero Trust Architecture

This card, the API and the page are generated from one file. Checking one against another adds no evidence.
