- Home
- Skills
- APIs & Backend
- API Authentication & Authorization Auditor
Works with the AI Agents you already use
API Authentication & Authorization Auditor
Audit API authentication designs and access controls to identify BOLA, token flaws, and permission gaps.
$29.99
API Authentication & Authorization Auditor
Example session with this skill installed
Audit this OpenAPI spec and JWT config. Users should only access their own orders. Admin role is required for /admin/stats. JWTs expire in 1 hour. [Attached: api-spec.json, auth-config.yaml]
- Read your context and instructions
- Compiled the api authentication
I have completed the authentication and authorization audit for your API based on the provided OpenAPI specification and JWT configuration. The review identified 3 confirmed findings related to object-level access and token expiration.
API Authentication & Authorization Audit
Assessment metadata
- API and environment: Order Management API (Staging)
- Authorized scope: All routes defined in api-spec.json
- Authentication mechanism: OAuth 2.0 / JWT
- Authorization model: Role-Based Access Control (RBAC) + Ownership checks
- Evidence sources: OpenAPI v3.0, auth-config.yaml
Endpoint Access Matrix
| Method | Route | Authentication | Required permission | Resource/tenant rule | Review status |
|---|---|---|---|---|---|
| GET | /orders/{id} | JWT Required | user | Must own order.id | Finding ID-01 |
| POST | /orders | JWT Required | user | N/A | Verified |
| GET | /admin/stats | JWT Required | admin | N/A | Verified |
| DELETE | /orders/{id} | JWT Required | user | Missing ownership check | Finding ID-02 |
Detailed Findings
ID-01: Broken Object Level Authorization (BOLA)
- Severity: High | Confidence: High
- Category: Object-level access
- Affected routes:
GET /orders/{id}
Observed behavior: The specification defines the route and requires a valid user token but does not define a server-side check ensuring the sub in the JWT matches the owner_id of the resource.
- Security impact: A validated user could potentially access any order by guessing or enumerating order IDs.
Remediation: Implement a middleware check to query the database and verify resource ownership before returning the payload.
ID-02: Missing Permission Consistency
- Severity: Medium | Confidence: Medium
- Category: Function-level authorization
- Affected routes:
DELETE /orders/{id}
Observed behavior: Config shows the delete method lacks the admin override or specific owner verification present in other methods.
- Remediation: Align authorization logic with the
GETmethod to ensure consistent ownership enforcement.
ID-03: Excessive Token Lifespan
- Severity: Low | Confidence: High
- Category: Token management
Observed behavior: auth-config.yaml shows access_token_ttl set to 3600s, but no refresh token rotation is enabled.
- Remediation: Enable refresh token rotation to mitigate risk if an access token is intercepted.
Next steps
- Implement ownership validation middleware for all
/{id}routes. - Update the identity provider config to enable refresh token rotation.
- Provide a sanitized log export of a failed access attempt to verify the new 403 Forbidden responses.
Connects securely to your tools. The creator never sees your data.
About this skill
API security reviews often suffer from vague findings or missed edge cases in complex identity flows. This skill provides a structured framework to audit authentication and authorization controls using your existing specifications, configuration files, and test evidence. It identifies high-risk weaknesses like broken object-level authorization (BOLA), inconsistent permission enforcement, and token lifecycle flaws without requiring manual checklist management.
What it does
- Authentication coverage audit to detect public route leaks and inconsistent identity requirements across API versions.
- Token lifecycle review assessing JWT claims, expiration policies, refresh rotation, and revocation mechanisms.
- Authorization mapping to verify server-side enforcement of roles, scopes, and permission policies.
- Access boundary analysis identifying risks in multi-tenant isolation and resource ownership checks.
- Remediation planning providing prioritized fixes with specific verification tests and rollback considerations.
How it works
- Confirm scope by providing API specifications, environment details, and authorized evidence sources.
- Build inventory to map every method and path to its required authentication and permission level.
- Analyze controls by comparing your current identity provider settings and access policies against the intended security model.
- Generate report including a detailed access matrix, severity-rated findings, and a structured remediation roadmap.
Frameworks & tools
Works with OpenAPI/Swagger specifications, OAuth 2.0, OpenID Connect, JWT, mTLS, and custom API key implementations. Compatible with identity providers like Auth0, AWS Cognito, Okta, and Firebase Auth.
Why this beats prompting it yourself
Generic prompts often miss subtle authorization failures like cross-tenant ID substitution or inconsistent HTTP method protections. This skill enforces a rigorous eight-step workflow that treats authentication and authorization as distinct layers, ensuring no endpoint is left unverified.
Use cases
- Pre-release security review to catch access control flaws before deploying new API versions.
- Compliance auditing by generating evidence-based reports for SOC2 or internal security standards.
- Identity provider migration to ensure new token scopes and audience claims match existing requirements.
- Post-incident analysis to identify configuration gaps after an unauthorized access event.
Known limitations
Does not perform live penetration testing, credential stuffing, or direct API interaction. Findings are based strictly on provided documentation and sanitized configuration evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Requires sanitized evidence; no live API interaction. Effectiveness depends on the accuracy of provided OpenAPI specs and identity provider configs. No automated exploit validation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 10 days ago
Permissions
No special permissions declared or detected