← ClaudeAtlas

api-security-auditlisted

Use when testing or auditing an API for security vulnerabilities — REST, GraphQL, gRPC, or WebSocket — including authentication/authorization, BOLA/IDOR, mass assignment, SSRF, rate limiting, and security misconfiguration. Maps findings to the OWASP API Security Top 10 (2023) and produces test steps, detection signals, and remediation for each. For authorized engagements only.
noahfranklin/gideon · ★ 2 · API & Backend · score 70
Install: claude install-skill noahfranklin/gideon
# API Security Audit A complete, standards-mapped methodology for assessing the security of an API you own or are **authorized** to test. Every technique below is paired with what to look for (detection) and how to fix it (remediation) so the output is actionable for the product team. ## 0. Authorization gate (do this first) Before any active testing, confirm: - [ ] Written authorization / rules of engagement (RoE) covering these hosts and endpoints. - [ ] In-scope base URLs, environments (prod vs staging), and accounts provided. - [ ] Out-of-scope paths, data, and destructive actions explicitly listed. - [ ] Testing window, rate limits, and an emergency contact. - [ ] Handling rules for any sensitive data encountered. If scope is unclear, pause and ask the engagement owner. Never test systems you don't own without documented permission. ## 1. Methodology overview ``` Scope & RoE ─► Recon & inventory ─► Map auth & roles ─► Per-endpoint tests ▲ │ └────────────── Report & remediate ◄──────────────────┘ ``` Work one endpoint at a time, tracking: method, path, params, auth required, roles allowed, object ownership model. ## 2. Recon & inventory - Collect the OpenAPI/Swagger, GraphQL introspection, or gRPC `.proto` definitions. - Enumerate versions (`/v1`, `/v2`), hidden/undocumented routes, and deprecated hosts. - Diff documented vs. observed endpoints (proxy your own client traffic to discover real call