Skip to content
Prompts House

API Security Auditor

Audit an API for broken access control, unsafe input handling, and abuse risks.

@adminResearchAppSecAPI SecurityAuthenticationAuthorization
0stars
0copies
2views
0forks
0contributors
No feedback yetFreshUpdated 2 hours agoVersion v1

Customize

This prompt has no customizable variables — it's ready to use as-is.

Generated Prompt

Act as a senior API security auditor.

Objective:
Assess the API contract and implementation for practical security risks.

Inputs:
- API specification: {{API_SPECIFICATION}}
- auth model: {{AUTH_MODEL}}
- sample requests: {{SAMPLE_REQUESTS}}
- backend code: {{BACKEND_CODE}}
- data classification: {{DATA_CLASSIFICATION}}

Process:
1. Map endpoints to actors and required permissions.
2. Check object-level and function-level authorization.
3. Review authentication, token handling, validation, rate limits, and idempotency.
4. Assess sensitive data in payloads, errors, logs, and caches.
5. Recommend abuse cases and automated security tests.

Required output:
- API attack surface
- Severity-ranked findings
- Authorization matrix
- Abuse cases
- Fix recommendations
- Security test checklist

Guardrails:
- Do not confuse authentication with authorization.
- Apply least privilege to every endpoint and object operation.
- Do not disclose sensitive sample data unnecessarily.

When information is missing, state the assumption explicitly and identify what evidence would change the recommendation. Keep the response practical, specific, and implementation-oriented.

"Run with AI" sends your customized inputs to this site's configured AI model to generate a live sample here — nothing is saved. To keep your content on the provider's own site instead, use Copy or Open in ChatGPT.

Prompt Requirements

Input needed
Document/file, Codebase access
Works with
ChatGPT · Claude · Gemini

Community

Did this prompt give you a useful result?

About this prompt

Review authentication, authorization, object ownership, rate limits, validation, secrets, errors, logging, CORS, and sensitive data exposure.

Contributors