API gateway hardening checklist
Answer each point for your API or gateway. You get a score and a to-do list ordered by importance, with the OWASP API Security Top 10 (2023) category for each point. Your answers stay in your browser and in the page address (so you can bookmark or share the link); nothing is uploaded.
To do first
How to use this checklist
- Go through the five groups and mark each point Yes, No or Not applicable. Leave a point blank if you do not know: it counts as unknown and appears in the to-do list after the confirmed gaps.
- Start with the "To do first" list: confirmed gaps come first, heaviest first.
- Test, do not assume: for authorization points, try the request with a different user's token.
Example
If you answer "No" to rate limits (OWASP API4) and "Yes" to token validation, the to-do list starts with the rate limit point, because it is a heavy point with a confirmed gap, and then lists everything you left blank.
Limits
A checklist shows common gaps; it cannot prove that an API is secure. The points follow the OWASP API Security Top 10 (2023), the OAuth security best current practice (RFC 9700) and related RFCs. Weights are our judgement of typical impact, not a standard. Your own threat model comes first.
Privacy and security of what you enter
Answers are processed in your browser. They are stored only in the page address; we do not receive them. See the privacy notice.
We review API gateways, WSO2 deployments and OAuth setups. See the services, try the OpenAPI security check or the WSO2 config check.
Message us on LinkedIn