api-testing-checklist
A fast, ordered methodology for assessing an API end to end — REST/GraphQL/gRPC/SOAP — so nothing gets skipped. Load when the target is an API (or recon found one), on "test this API", "checklist", methodology triage, or to confirm coverage before reporting. Signals: /api, swagger/openapi.json, Grap
v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/api-testing-checklistGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacoteb8bb3314…409850b5
b8bb3314d7dc…19a5409850b51 arquivo · 2.0 KBVarreduraBaixonenhum achado
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-testing-checklist@ee0e0c5
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
Confirm scope first (tradecraft-scope-roe). Each phase links to the skill that goes deep — load it,
work its cheatsheet.md where present, and don't mark a phase failed until you've covered it
(house rule: fuzz every input/context/encoding, blind/OOB). This is your coverage map.
1 · Discover & map the surface
- Find the API:
/api, subdomains, JS files (recon-js-analysis), mobile/SPA traffic (recon-content-discovery) - Grab the spec:
swagger.json/openapi.json/ GraphQL introspection /.proto— enumerate every endpoint, method, param - Note auth model (Bearer/JWT/API key/cookie/mTLS), versions (
/v1,/v2), and content types - Map roles: create two accounts (and an unauth client) — you need them for access-control tests
2 · Authentication
- Token flaws — JWT alg/kid/key confusion (
web-auth-jwt), API-key leakage/predictability - Auth attacks — credential stuffing, weak/OTP flows, token not expiring/rotating (
api-auth-attacks) - Unauthenticated endpoints that shouldn't be
3 · Authorization (the #1 API bug class — go deep)
- BOLA/IDOR — swap object IDs between the two accounts on every object-taking endpoint (
api-bola,web-idor) - BFLA — call admin/privileged functions as a low-priv user; try hidden methods (PUT/DELETE/PATCH)
- Path/verb tampering,
X-Original-URL/method override, GraphQL field-level authz
4 · Input handling & injection
- Injection across params, JSON bodies, headers: SQLi (
web-sqli), NoSQL (api-mongo-agg-facet-bypass), command (web-command-injection), SSTI (web-ssti) - SSRF via URL params / webhooks / "fetch from URL" (
web-ssrf), XXE on XML endpoints (web-xxe) - Mass assignment — inject extra fields (
role,isAdmin,price) (api-mass-assignment)
5 · Data exposure & business logic
- Excessive data exposure — endpoints returning more fields than the UI shows (PII, internal flags)
- Business-logic abuse — price/quantity tampering, negative values, replay, race conditions (
web-race-conditions,web-business-logic) - Mass assignment → privilege/state change; parameter pollution (
web-http-parameter-pollution)
6 · Rate limiting & resource consumption
- Missing/bypassable rate limits (
web-rate-limit-bypass) — brute, enumeration, cost - Unbounded queries / pagination abuse; GraphQL depth/alias/batch amplification
7 · Protocol specifics
- GraphQL — introspection, batching, injection, field authz (
api-graphql) - gRPC — reflection, message tampering (
api-grpc) - REST/SOAP — verb tampering, content-type confusion, version drift (
api-versioning); fuzz systematically (api-fuzzing)
8 · Before you report
- Re-prove each finding from a clean session; anonymise data (
reporting-triage-validation) - Score it (
reporting-cvss-scoring), then write it up (reporting-bug-bounty-writeup)
Coverage bar
Every endpoint × method exercised; BOLA/BFLA tried across accounts on every object; injection fuzzed
on every input; rate-limit and business-logic checked. A phase is failed only after that — else open.
Arquivos desta versão
- SKILL.md3.7 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Não | Não |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
A varredura não encontrou nada para apontar nesta versão.
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 de nov. de 2026 | ee0e0c5 | b8bb3314 | Assinada | – |
Mais de NoorQureshi
Tudo deste publicadorMais em APIs, SaaS e identidade
Ver a categoria- testing-for-sensitive-data-exposuremukul975/testing-for-sensitive-data-exposure5
- performing-jwt-none-algorithm-attackmukul975/performing-jwt-none-algorithm-attack5
- sharp-edgestrailofbits/sharp-edges4
- hydraaeondave/hydra4
- implementing-google-workspace-admin-securitymukul975/implementing-google-workspace-admin-security4
- implementing-api-security-posture-managementmukul975/implementing-api-security-posture-management4
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login