API authorization and data exposure audit
Check which roles and tenants can access API data using source and provided examples.
Customize the recipe
0/1500 characters
Prompt preview
# API authorization and data exposure audit Check which roles and tenants can access API data using source and provided examples. ## Read-only scope Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient. Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files. ## Tools and setup · Universal Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions. - [Security Threat Model](https://github.com/openai/skills/blob/main/skills/.curated/security-threat-model/SKILL.md) (Skill) — Map assets, access boundaries, and risk from supplied architecture and source evidence. - [OWASP ASVS](https://github.com/OWASP/ASVS) (Repository) — Map observed web security controls to relevant verification requirements. - [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification) (Repository) — Describe documented request, response, authentication and error contracts in a reusable format. ## Workflow Compare the supplied API contract and role matrix with handler and data-access code. Trace identity, ownership checks, tenant scope, and sensitive response fields using the supplied fixtures and recorded examples. ## Deliverable An endpoint and permission matrix with data exposure findings and missing evidence. - Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient. ## Acceptance checks - [ ] Cite the access decision and response selection evidence for each reported boundary. - [ ] Mark missing handler, policy, or fixture evidence as unverified. - [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps. - [ ] Redact credentials, tokens, personal data, and sensitive values in the report.
Recipe resources
Source, setup, and compatibility details.
Security Threat Model
Map assets, access boundaries, and risk from supplied architecture and source evidence.
Upstream documents Codex.
28.9K GitHub stars on the source repository
OWASP ASVS
Map observed web security controls to relevant verification requirements.
License · CC-BY-SA-4.0
3.8K GitHub stars
OpenAPI Specification
Describe documented request, response, authentication and error contracts in a reusable format.
License · Apache-2.0