api-security-testing
Skill47 starsChanged 5 months agoMITView on GitHub
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- storlay/crypto-alert-apitheir own version, first seen Oct 20, 2026
- Gopyr/gopyr-skills-hubtheir own version, first seen Oct 11, 2026
- usestrix/strixtheir own version, first seen Oct 8, 2026
- Ghosteken/agent-harnesstheir own version, first seen Oct 1, 2026
- andfrancot-alt/claude-skillstheir own version, first seen Aug 17, 2026
- Kur1sulab/blackboxtheir own version, first seen Aug 12, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- usestrix/strix★ 74ksame name
- Wang200935/security-agent-skills★ 4same name
- Kur1sulab/blackbox★ 3same name
- Ghosteken/agent-harness★ 2same name
- xAmirHamza77/PenKit51★ 2same name
- lschGSL/claude_code_template★ 1same name
- andfrancot-alt/claude-skills★ 0same name
- Gopyr/gopyr-skills-hub★ 0same name
- storlay/crypto-alert-api★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- access-control-testingSkill
- active-pentestSkill
- authentication-testingSkill
- business-logic-testingSkill
- client-side-exploitationSkill
- file-upload-and-ssrfSkill
- injection-testingSkill
- pentest-reportingSkill
- recon-and-osintSkill
- secrets-management-auditSkill
- security-code-auditSkill
- security-hardeningSkill
- security-testingSkill
- threat-modelingSkill
- vulnerability-chainingSkill
The file
Files
API Security Testing (FIND/EXPLOIT — OWASP API Top 10)
Overview
Modern apps are API-first, and APIs fail differently from web pages: the bugs are in authorization per object/field and resource limits, not rendering. Test the API directly, bypassing the UI entirely.
Core principle: The UI is one client; attackers talk to the API raw. Every endpoint, field, and method must enforce authz and limits on its own — the front-end protects nothing.
Applies when / Skip when
- Applies when: the app exposes a programmatic API — REST, GraphQL, gRPC, or WebSocket — including the API behind a SPA or mobile client.
- Skip when: the app is purely server-rendered HTML with no API anyone calls → N/A.
- If N/A: report "api-security-testing: N/A — no API surface" and stop.
⚠️ Authorization
Your own/authorized API. Use test accounts and a non-production instance for stateful tests.
Get the spec first
Pull the contract, then test every operation it (and the UI) reveals:
- OpenAPI/Swagger (
/swagger,/openapi.json,/api-docs), GraphQL introspection, gRPC reflection, Postman collections, mobile-app traffic via proxy. - Diff documented endpoints vs. what the app actually calls — undocumented endpoints are gold.
OWASP API Top 10 — the checklist
| # | Risk | Test |
| API1 | BOLA (object authz) | Swap object ids across accounts → see access-control-testing |
| API2 | Broken authentication | Weak tokens/JWT/keys → see authentication-testing |
| API3 | BOPLA (property authz) | Read fields you shouldn't (excessive exposure) / write fields you shouldn't (mass assignment) |
| API4 | Unrestricted resource consumption | No rate/size/page limits; expensive queries; cost/DoS |
| API5 | BFLA (function authz) | Call admin/privileged operations as a normal user |
| API6 | Unrestricted access to business flows | Automate a flow meant to be human-paced (scalping, spam) |
| API7 | SSRF | Server fetches a URL you supply → see file-upload-and-ssrf |
| API8 | Misconfiguration | Verbose errors, permissive CORS, missing security headers |
| API9 | Improper inventory | Old /v1 next to /v2, staging APIs, undocumented endpoints |
| API10 | Unsafe third-party consumption | App trusts an external API's response blindly |
See references/api-attacks.md for REST, GraphQL, gRPC, and WebSocket recipes.
Excessive data exposure vs. the UI
The API often returns more than the UI shows (full user objects with passwordHash, internal
flags, other users' fields). Inspect raw JSON responses, not the rendered page.
GraphQL specifics (high-value)
- Introspection enabled → full schema map. Pull it.
- Batching / aliasing → bypass rate limits, brute-force via one request.
- Query depth/complexity → nested recursive queries for DoS.
- Field-level authz → a field guarded in one query exposed via another path/mutation.
Output
Per finding: endpoint/operation, method, account used, the raw request/response, which API-Top-10 class, and impact. BOLA/BFLA findings are typically High–Critical.
Hand-off
Deep authz → access-control-testing; auth/JWT → authentication-testing; flow abuse →
business-logic-testing; reproduce → active-pentest; fix → security-hardening.
Common mistakes
- Testing through the UI only — hit the API directly; that's the real attack surface.
- Reading the rendered page instead of the raw JSON — that's where over-exposure hides.
- Forgetting GraphQL introspection/batching and gRPC reflection — they hand you the whole map.
- Ignoring old API versions —
/v1often lacks/v2's fixes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.