API Security
Protecting application programming interfaces from abuse and data exposure.
What it is
The discipline of securing the endpoints applications expose for programmatic access, covering authentication, authorization, input handling, and exposure of data and functions to ensure only intended callers can do intended things.
Why it matters
APIs now carry the bulk of sensitive traffic, and broken object-level authorization and excessive data exposure are leading breach causes, so reviewing API authz and inspecting API logs is core modern work.
In practice
An endpoint that returns any user's record by ID because it never checks the caller owns that record.
What to look for
- Endpoints that return more data than the client shows.
- Missing authorization on object IDs.
- Old API versions still running.
Common mistake
Securing the UI and forgetting the API behind it. Attackers call the API directly.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- Rate Limiting: Capping how many requests a client can make in a time window.
- Parameter Tampering: Altering request fields to change application behavior or access.