Infrastructure for API Securitys
API infrastructure security covers the components around the application code: API gateways and web application firewalls that enforce authentication, limits and filtering at the edge, plus the handling of secrets and third-party dependencies. It reduces risk from misconfiguration, leaked keys and vulnerable libraries.
Stage: Platform and Operations · Part of the API Security roadmap · Last reviewed 19 November 2026
What to learn in Infrastructure
- Configure an API gateway to enforce authentication, quotas and request validation
- Explain what a WAF can and cannot block for APIs
- Store secrets in a vault or secret manager and rotate them
- Scan dependencies and container images for known vulnerabilities in CI
- Inventory all API versions and hosts to find forgotten endpoints
Infrastructure interview questions
Does a WAF replace secure API code?
No. A web application firewall filters known attack patterns at the edge, but it cannot understand business rules, so it will not catch broken authorisation or logic flaws. It is an extra layer that buys time and blocks noise, while the application must still enforce its own checks.
Why should secrets never be committed to Git?
Git history is permanent and widely copied, so a leaked key stays exposed even after deletion, and bots scan public repositories within minutes. Keep secrets in environment injection or a secret manager, scan commits with a secret detector, and rotate any key that was ever exposed.
Where Infrastructure fits in the API Security roadmap
Infrastructure belongs to the Platform and Operations stage (advanced level), which takes about 11 hours. Defence in depth.
Other units in this stage
Back to the full API Security roadmap