Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/tradecraft-scope-roeWeb e bug bounty

tradecraft-scope-roe

⁨Establish and enforce the authorization envelope before any testing — the scope rule that governs everything. Load FIRST on every engagement, on "start", a new target, a program handle, or any ambiguity about what is allowed. Signals: a domain/IP to test, a bug-bounty program handle, a pentest state⁩

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/tradecraft-scope-roe

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
D1YRS5lJx3…n9rpkpAg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettob53c0468…0785f799
b53c0468acdb…05f40785f7991 file · ⁦1.6 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-scope-roe@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

When this governs

Always, before the first packet. Security Skills operates only inside a confirmed authorization envelope, and the envelope type is explicit. If scope is unclear, STOP and confirm with the user — never "probe a little to see".

The envelopes

  • Pentest / authorized engagement — boundary is the signed scope: the statement of work / authorization letter naming the in-scope hosts, IP ranges, apps, and the testing window. Record the authorized targets in scope.txt; treat the window and any carve-outs as hard limits. (Practice ranges you own or are licensed to test — a home lab, a training range — count here.)
  • Bug-bounty program — boundary is the program scope + rules of engagement. Before testing, capture:
    • scope.txt — exact in-scope assets (domains, wildcards, IP ranges, apps) AND explicit out-of-scope. Out-of-scope is a hard block, not a suggestion.
    • roe.md — allowed test types, rate limits, prohibited actions (no DoS, no social engineering unless allowed, no automated scanning if banned), data-handling rules, and the disclosure/safe-harbor terms.
  • Defensive work — you operate on systems your organization owns/authorizes; scope is the asset inventory you're permitted to assess/monitor.

The discipline

  1. Confirm authorization and write the envelope files before scanning.
  2. Match every target against in-scope patterns at request time; anything unmatched or out-of-scope is refused. Third parties (shared CDNs, SaaS the target merely uses) are out.
  3. Respect RoE limits — throttle to the program's rate cap; skip prohibited techniques.
  4. Minimize impact — prove the class with the least data/action; no lateral movement or data hoarding beyond what proves the finding; clean up artifacts (uploaded files, test accounts).
  5. Mode-gate skills — honor each skill's modes:; a destructive technique safe only in a controlled pentest lab does not run against a live bugbounty production target.

Anti-patterns

  • "It resolved so it's probably in scope" — verify against the program's list.
  • Testing an acquisition/subsidiary not named in scope.
  • Ignoring rate limits because the bug is interesting.
  • Keeping real customer data as "evidence" instead of a redacted proof.

Verify

scope.txt (and roe.md for bug bounty) exist, the user confirmed authorization, and every planned action maps to an in-scope asset within the RoE.

References

Program policy pages; HackerOne/Bugcrowd RoE; disclose.io safe-harbor.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

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.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c5b53c0468Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login