Fundamentals for API Securitys
API security fundamentals cover the threat model of an API and the transport layer beneath it. A threat model lists assets, entry points and attackers, while transport security means enforcing TLS so traffic cannot be read or altered in transit. Everything else in the roadmap rests on these two ideas.
Stage: Threats · Part of the API Security roadmap · Last reviewed 19 November 2026
What to learn in Fundamentals
- Draw a data-flow diagram of an API and mark trust boundaries
- Apply STRIDE to list likely threats against an endpoint
- Configure TLS with modern protocol versions and redirect plain HTTP
- Explain HSTS and certificate validation and why they stop downgrade attacks
- Name the entries of the OWASP API Security Top 10 and their causes
Fundamentals interview questions
What is threat modelling and when do you do it?
Threat modelling is a structured review of a system to find what could go wrong before it is built or changed. You map assets, data flows and trust boundaries, then list threats, for example with STRIDE, and decide mitigations. It is done at design time and when features change.
Is HTTPS enough to secure an API?
No. HTTPS protects data in transit between client and server, but it does nothing about broken authorisation, injection, leaked fields or abuse by a legitimate account. It is a necessary baseline, with authentication, access control, validation and monitoring layered on top.
Where Fundamentals fits in the API Security roadmap
Fundamentals belongs to the Threats stage (intermediate level), which takes about 15 hours. Know the risks.
Other units in this stage
Back to the full API Security roadmap