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 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/api-testing-checklistScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettob8bb3314…409850b5
b8bb3314d7dc…19a5409850b51 file · 2.0 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/api/api-testing-checklist@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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.
File di questa versione
- SKILL.md3.7 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | b8bb3314 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in API, SaaS e identità
Vai alla 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login