OWASP Top-10 API Security, AuthZ & Secret Hygiene Audit Skill

Systematic security audit for REST and GraphQL APIs: detect Broken Object Level Authorization (BOLA/IDOR), mass assignment, SSRF, JWT algorithm confusion,

---
name: owasp-api-security
description: Systematic security audit for REST and GraphQL APIs: detect Broken Object Level Authorization (BOLA/IDOR), mass assignment, SSRF, JWT algorithm confusion, and leaked secrets. Use when working with OWASP API Top 10, BOLA / IDOR, JWT Security, SSRF Prevention.
triggers:
  - owasp api security
  - owasp api top 10
  - bola / idor
---

# OWASP Top-10 API Security, AuthZ & Secret Hygiene Audit Skill

## 1. When to Use This Skill
Load `skill-owasp-api-security` whenever an engineering or operations task involves **OWASP API Top 10, BOLA / IDOR, JWT Security, SSRF Prevention**. Specifically:
- Systematic security audit for REST and GraphQL APIs: detect Broken Object Level Authorization (BOLA/IDOR), mass assignment, SSRF, JWT algorithm confusion, and leaked secrets.
- Designing, reviewing, or debugging production configurations without guesswork or deprecated flags.
- Running deterministic pre-flight and post-execution verification checks before reporting completion.

## 2. Prerequisites & Required Environment
- **Target Stack:** OWASP API Top 10, BOLA / IDOR, JWT Security, SSRF Prevention
- **Permissions:** Read-only inspection by default; ask for explicit confirmation before executing destructive mutations or production deployments.
- **Reference Repository:** `https://owasp.org/www-project-api-security/`

## 3. Step-by-Step Execution Playbook
1. **Context & Configuration Discovery:**
   Inspect existing project manifests (`package.json`, `wrangler.jsonc`, schema files, or environment declarations) before proposing changes. Never overwrite existing bindings or credentials blindly.
2. **Deterministic Implementation:**
   Apply the canonical patterns for **OWASP API Top 10**:
   - Enforce strict schema/type validation at every external boundary.
   - Include explicit error handling, structured logging, and idempotency keys on all mutating calls.
   - Keep secrets in environment variables or secret stores—never hardcode tokens in source files.
3. **Verification & Regression Gate:**
   Run the verification commands below and inspect both exit codes and output payloads before marking the task complete.

## 4. Reference Commands & CLI Workflow
```bash
npx gitleaks detect --source .
npm audit --omit=dev
```

## 5. Edge Cases & Anti-Hallucination Guardrails
- **Zero Unverified Claims:** Never claim a deployment, migration, or API call succeeded without inspecting the command output or HTTP status code.
- **Rollback Readiness:** Always record the previous state or migration version so changes can be reverted cleanly if downstream health checks fail.

Synthesized Engineering Blueprint & Setup Guide