Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
D1YRS5lJx3…n9rpkpAg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteb53c0468…0785f799
b53c0468acdb…05f40785f7991 arquivo · ⁦1.6 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-scope-roe@ee0e0c5

Este item ainda não foi escrito no seu idioma, então aparece em 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.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNã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ãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.10.14-ee0e0c513 de nov. de 2026ee0e0c5b53c0468Assinada–

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. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login