Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
noorqureshi/tradecraft-scope-roeWeb y 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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tradecraft-scope-roe

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
D1YRS5lJx3…n9rpkpAg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paqueteb53c0468…0785f799
b53c0468acdb…05f40785f7991 archivo · ⁦1.6 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-scope-roe@ee0e0c5

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.10.14-ee0e0c513 nov 2026ee0e0c5b53c0468Firmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login