What we check
What AuditGate checks
Every category of the OWASP API Security Top 10, in plain terms, and what each check needs.
The OWASP API Security Top 10 is the standard list of the most common ways APIs get broken into. AuditGate checks all ten. Some checks only run when you've set something up, such as a test user or write probes; each section says what.
| Category | In plain terms |
|---|---|
| API1 Broken Object Level Authorization | One user can read another user's data by changing an ID |
| API2 Broken Authentication | Weak tokens, sessions or login handling |
| API3 Broken Object Property Level Authorization | Responses leak fields, or requests can set fields they shouldn't |
| API4 Unrestricted Resource Consumption | No limits on attempts, page sizes, upload sizes or query depth |
| API5 Broken Function Level Authorization | Normal users can reach admin-only actions |
| API6 Unrestricted Access to Sensitive Business Flows | Sign-up, checkout or coupons can be automated at scale |
| API7 Server Side Request Forgery | Your server can be made to call addresses it shouldn't |
| API8 Security Misconfiguration | Missing headers, open CORS, debug output, exposed files, weak TLS |
| API9 Improper Inventory Management | Old versions, staging copies or undocumented routes left running |
| API10 Unsafe Consumption of APIs | Trusting webhooks and partner APIs without checking them |
API1: Reading other users' data#
Alice requests GET /orders/1042, sees her order, changes the number to 1043 and gets Bob's order.
How it's checked: with two test users, the scan reads an object as the first user and requests it as the second. It also checks whether objects can be read without signing in.
Needs: two test users for the cross-user test.
Fix: load every object through the signed-in user, for example WHERE id = ? AND owner_id = ?, never by ID alone.
API2: Authentication#
How it's checked: live traffic and scans look for tokens that never expire, unsigned or weakly signed JWTs, session cookies missing secure flags, and login routes with no limit on attempts. With a connected repository, code scanning finds disabled token checks and weak password hashing.
Fix: short-lived signed tokens, secure cookies, and limits on login and OTP attempts.
API3: Data in responses and requests#
How it's checked: responses are checked for passwords, card numbers, BVNs, NINs and phone numbers. The mass assignment test sends fields like role or isAdmin and checks whether they stick, then puts the value back.
Needs: write probes on a development or staging project for the mass assignment test.
Fix: return only the fields each screen needs, and accept only the fields each request should change.
API4: Unlimited use#
How it's checked: scans send a quick burst to login, OTP, payment and password-reset routes, ask each list for 5,000 records, send deeply nested and batched GraphQL queries, and try a 5 MB request body. Live traffic flags lists that return 1,000 or more records. Code scanning finds very high body limits, uploads with no size limit and page sizes taken straight from the request.
Needs: nothing for page size and GraphQL. Write probes for the burst and body size tests.
Fix: rate-limit by account and IP, cap page sizes on the server, keep body limits small, and limit GraphQL depth and batching.
API5: Admin-only actions#
A normal user calls GET /admin/users and gets the list, or reaches it as /admin/USERS because the check only matches the exact path.
How it's checked: every route that refuses a normal request is retried with path tricks (case changes, trailing dots, ;, encoded letters) and rewrite headers. With a low-privilege test user, the scan also calls admin routes as that user. Code scanning flags admin routes with no role check.
Needs: nothing for the path tricks. A low-privilege test user for the role tests.
Fix: check roles in one place on the server, deny by default, and check the cleaned-up path inside your app.
API6: Automated abuse of business flows#
A script buys all the limited stock, creates thousands of accounts for a sign-up bonus, or redeems one coupon over and over.
How it's checked: scans run sign-up, checkout, coupon, referral and booking routes several times in a row and report flows that keep succeeding with nothing slowing them down. Live traffic and code scanning flag these routes when nothing limits them.
Needs: write probes for the scan test.
Fix: limit how often one account, device and IP can complete each flow, and add a CAPTCHA where abuse pays.
API7: Server-side request forgery#
An endpoint that fetches a URL you give it, for previews, imports or webhooks, can be pointed at your internal network or your cloud provider's metadata.
How it's checked: the scan puts a unique callback address into URL parameters and webhook fields. If your server calls it, that's proof, even when nothing shows in the response. It also checks whether cloud metadata comes back.
Needs: nothing for URL parameters. Write probes for webhook fields.
Fix: allow only the destinations you expect, block private addresses, and don't follow redirects.
API8: Misconfiguration#
How it's checked: security headers, CORS settings, debug modes, error messages that reveal internals, TLS versions and certificates, exposed .env and .git files, admin consoles, secrets in your frontend JavaScript, and infrastructure files in your repository.
Fix: set headers in one place, turn off debug output in production, and keep secrets out of code.
API9: Forgotten versions and copies#
You moved to /v2/users, but /v1/users still works without the fixes added since. Or staging-api.example.com is open to the internet with real data.
How it's checked: scans try older versions of your routes by path, header and query parameter, and check common staging and old host names under your verified domain. Live traffic flags endpoints still answering after their own retirement date. With a repository and a published OpenAPI document, scans list routes the document leaves out.
Needs: a verified domain for the staging check. A repository and a JSON OpenAPI document for the documentation check.
Fix: switch old versions off on a set date, keep staging off the public internet, and keep your API description up to date.
API10: Trusting other APIs#
Your payment webhook accepts any request that says a payment succeeded, without checking it came from your payment provider.
How it's checked: scans send an unsigned test event to your webhook routes and report any that accept it. Code scanning finds webhooks with no signature check, calls to partners over plain http://, calls with no timeout, and partner responses loaded in ways that can run code.
Needs: write probes for the webhook test.
Fix: verify webhook signatures, use HTTPS, set timeouts, and validate partner data like user input.
