api-security-assessmentlisted

# API Security Assessment ## Purpose Create an API security assessment that delivers actionable, measurable results. **Category**: Cybersecurity & Information Security ## Inputs ### Required - **Objective**: What you want to achieve with this deliverable - **Context**: Relevant background information (systems, scope, environment) ### Optional - **Constraints**: Any limitations or requirements to consider - **Existing Work**: Previous documents or data to build on ## Context Before starting, read the repo's `CLAUDE.md` and any relevant notes under `memory/` (e.g. `memory/repo/<repo>/`, `memory/feedback/`) for prior decisions and constraints. ## Process ### Step 1: Context & Research - Review any existing api security assessment documents in the project - Identify key stakeholders and their requirements - Select the most appropriate framework: OWASP API Security Top 10, OpenAPI Specification Security Schemes, OAuth 2.0/OIDC ### Step 2: Analysis & Framework Application - Apply the selected framework to structure the api security assessment - Identify gaps, opportunities, and risks - Define success metrics: Vulnerability Count per API, Authentication Bypass Attempts, Authorization Test Coverage, Rate Limiting Effectiveness - Document assumptions and dependencies - Validate approach against industry best practices ### Step 3: Build the Deliverable - Structure the api security assessment using the output format below - Include specific, actionable recommendations — not