Back to catalog
Static reviewDevelopment

Skill dossier

conducting-api-security-testing

Source declaration

Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic. The tester uses the OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections and custom scripts to test endpoint security at every privilege level. Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing.

The author's original description, preserved in English. It describes intent, not verified performance.

Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic. The tester uses the OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections and custom scripts to test endpoint security at every privilege level. Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic. The tester uses the OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections and custom scripts to test endpoint security at every privilege level. Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/conducting-api-security-testing/SKILL.md:L55]
  • Step 1: API Discovery and Documentation [Source statement; provisional, not tested. Evidence: skills/conducting-api-security-testing/SKILL.md:L57]
  • Step 2: Authentication and Token Testing [Source statement; provisional, not tested. Evidence: skills/conducting-api-security-testing/SKILL.md:L70]
  • Step 3: Authorization Testing (BOLA/BFLA) [Source statement; provisional, not tested. Evidence: skills/conducting-api-security-testing/SKILL.md:L83]
  • Step 4: Input Validation and Injection Testing [Source statement; provisional, not tested. Evidence: skills/conducting-api-security-testing/SKILL.md:L102]
  • Step 5: Data Exposure and Response Analysis [Source statement; provisional, not tested. Evidence: skills/conducting-api-security-testing/SKILL.md:L113]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/conducting-api-security-testing/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/conducting-api-security-testing/LICENSEOther11 KB
skills/conducting-api-security-testing/references/api-reference.mdReference2.5 KB
skills/conducting-api-security-testing/scripts/agent.pyScript8.2 KB
skills/conducting-api-security-testing/SKILL.mdInstruction11.6 KB

SKILL.md frontmatter

{
  "name": "conducting-api-security-testing",
  "description": "Conducts security testing of REST, GraphQL, and gRPC APIs to identify vulnerabilities in authentication, authorization, rate limiting, input validation, and business logic. The tester uses the OWASP API Security Top 10 as the testing framework, combining Burp Suite interception with Postman collections and custom scripts to test endpoint security at every privilege level. Activates for requests involving API security testing, REST API pentest, GraphQL security assessment, or API vulnerability testing.\n",
  "domain": "cybersecurity",
  "subdomain": "penetration-testing",
  "tags": [
    "API-security",
    "OWASP-API-Top10",
    "REST",
    "GraphQL",
    "authorization-testing"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "ID.RA-01",
    "ID.RA-06",
    "GV.OV-02",
    "DE.AE-07"
  ],
  "mitre_attack": [
    "T1190",
    "T1213",
    "T1552.001",
    "T1078",
    "T1071.001"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: API Discovery and Documentation

    Source-described action candidate under “Step 1: API Discovery and Documentation”; not verified execution.

  4. 04
    Input

    Import API documentation: Load OpenAPI/Swagger specs into Postman or Burp Suite to catalog all endpoints, methods, parameters, and authentication requirements

    Source-described input candidate under “Step 1: API Discovery and Documentation”; not verified execution.

  5. 05
    Output

    Reverse-engineer undocumented APIs: Proxy the mobile app or web frontend through Burp Suite and exercise all features to capture API calls. Export the Burp sitemap as the baseline endpoint inventory.

    Source-described output candidate under “Step 1: API Discovery and Documentation”; not verified execution.

  6. 06
    Action

    GraphQL introspection: Send an introspection query to discover the full schema:

    Source-described action candidate under “Step 1: API Discovery and Documentation”; not verified execution.

Inspect all extracted workflow candidates (53 candidate steps)
  1. 07
    Action

    Endpoint enumeration: Fuzz for hidden API versions (`/api/v1/`, `/api/v2/`, `/api/internal/`), debug endpoints (`/api/debug`, `/api/health`, `/api/metrics`), and administrative endpoints

    Source-described action candidate under “Step 1: API Discovery and Documentation”; not verified execution.

  2. 08
    Decision

    Document authentication mechanisms: Identify if the API uses API keys, OAuth 2.0 Bearer tokens, JWT, session cookies, or mutual TLS

    Source-described decision candidate under “Step 1: API Discovery and Documentation”; not verified execution.

  3. 09
    Action

    Step 2: Authentication and Token Testing

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  4. 10
    Action

    JWT analysis: Decode the JWT and inspect claims (sub, exp, iss, aud, role). Test:

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  5. 11
    Action

    Algorithm confusion: Change `alg` to `none` and remove the signature

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  6. 12
    Action

    Key confusion: Change `alg` from RS256 to HS256 and sign with the public key

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  7. 13
    Action

    Weak secret: Brute-force the HMAC secret with `hashcat -m 16500 jwt.txt wordlist.txt`

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  8. 14
    Action

    Token expiration: Verify tokens expire and cannot be used after expiration

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  9. 15
    Action

    Claim tampering: Modify role, userId, or permission claims and re-sign

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  10. 16
    Action

    OAuth 2.0 testing: Check for redirecturi manipulation, authorization code reuse, token leakage in Referer headers, and missing state parameter (CSRF)

    Source-described action candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  11. 17
    Decision

    API key security: Test if API keys are validated per-endpoint, if revoked keys are immediately rejected, and if keys in query strings appear in access logs or analytics

    Source-described decision candidate under “Step 2: Authentication and Token Testing”; not verified execution.

  12. 18
    Action

    Step 3: Authorization Testing (BOLA/BFLA)

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  13. 19
    Action

    BOLA (IDOR) testing: For every endpoint that returns user-specific data, replace the object identifier with another user's identifier:

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  14. 20
    Action

    `GET /api/users/123/orders` -> `GET /api/users/456/orders`

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  15. 21
    Action

    Test with numeric IDs, UUIDs, usernames, and email addresses

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  16. 22
    Action

    Automate with Burp Autorize extension: configure it with two sessions (attacker and victim) and replay all requests

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  17. 23
    Action

    BFLA testing: Using a low-privilege token, attempt to access administrative endpoints:

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  18. 24
    Action

    `DELETE /api/users/456` (admin-only delete)

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  19. 25
    Action

    `PUT /api/users/456/role` (role modification)

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  20. 26
    Action

    `GET /api/admin/dashboard` (admin panel data)

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  21. 27
    Action

    Mass assignment: Send additional JSON properties not shown in the documentation:

    Source-described action candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  22. 28
    Decision

    HTTP method testing: If GET works on an endpoint, try PUT, PATCH, DELETE, and OPTIONS to discover unprotected methods

    Source-described decision candidate under “Step 3: Authorization Testing (BOLA/BFLA)”; not verified execution.

  23. 29
    Input

    Step 4: Input Validation and Injection Testing

    Source-described input candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  24. 30
    Action

    SQL injection in API parameters: Test all parameters (path, query, body, headers) with SQL injection payloads. JSON APIs are often overlooked: `{"username": "admin' OR 1=1--", "password": "test"}`

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  25. 31
    Action

    NoSQL injection: For MongoDB backends, test with operator injection: `{"username": {"$gt": ""}, "password": {"$gt": ""}}`

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  26. 32
    Input

    SSRF via API: Test any parameter that accepts URLs (webhook URLs, avatar URLs, import endpoints) with internal addresses and cloud metadata endpoints

    Source-described input candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  27. 33
    Action

    GraphQL-specific injection: Test for query depth attacks, alias-based batching for brute force, and field suggestion enumeration

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  28. 34
    Action

    XXE in XML APIs: Submit XML content with external entity declarations to API endpoints that accept XML

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  29. 35
    Action

    Rate limiting validation: Send 100+ rapid requests to authentication endpoints, password reset, and OTP verification to test for brute force protection

    Source-described action candidate under “Step 4: Input Validation and Injection Testing”; not verified execution.

  30. 36
    Action

    Step 5: Data Exposure and Response Analysis

    Source-described action candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  31. 37
    Action

    Check for excessive data exposure in API responses:

    Source-described action candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  32. 38
    Output

    Verbose responses: Compare the data returned in API responses with what the UI displays. APIs often return more fields than needed (internal IDs, creation timestamps, email addresses of other users, role information).

    Source-described output candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  33. 39
    Decision

    Error message analysis: Trigger errors by sending malformed input, invalid tokens, and non-existent resources. Check if error messages reveal stack traces, database queries, internal paths, or technology details.

    Source-described decision candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  34. 40
    Decision

    Pagination and enumeration: Test if enumeration is possible by iterating through paginated responses (`/api/users?page=1`, `page=2`, etc.) to extract all records

    Source-described decision candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  35. 41
    Action

    GraphQL data exposure: Query for fields not intended for the current user's role. Test nested queries that traverse relationships to access unauthorized data.

    Source-described action candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  36. 42
    Action

    Debug endpoints: Check `/api/debug`, `/api/status`, `/metrics`, `/health`, `/.env`, `/api/swagger.json` for exposed internal information

    Source-described action candidate under “Step 5: Data Exposure and Response Analysis”; not verified execution.

  37. 43
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  38. 44
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  39. 45
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  40. 46
    Input

    Import Swagger spec into Postman, generating 87 endpoint collections across 12 controllers

    Source-described input candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  41. 47
    Action

    Discover BOLA on `/api/v1/accounts/{accountId}/transactions` allowing any authenticated user to view any account's transaction history

    Source-described action candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  42. 48
    Action

    Find mass assignment on the user update endpoint where adding `"dailyTransferLimit": 999999` bypasses the configured transfer limit

    Source-described action candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  43. 49
    Action

    Identify that the fund transfer endpoint lacks rate limiting, allowing unlimited transfer attempts without throttling

    Source-described action candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  44. 50
    Action

    Discover that JWT tokens have a 30-day expiration with no refresh token rotation, enabling long-lived session hijacking

    Source-described action candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  45. 51
    Action

    Find that the admin endpoint `/api/v1/admin/users` is accessible with a standard user token (BFLA)

    Source-described action candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  46. 52
    Output

    Report all findings with CVSS scores and specific API code-level remediation guidance

    Source-described output candidate under “Scenario: API Security Assessment for a Fintech Mobile Application”; not verified execution.

  47. 53
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

20 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

11 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 11 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

8 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/conducting-api-security-testing/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/conducting-api-security-testing/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/conducting-api-security-testing
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.