roe-template
Rules of Engagement document creation — scope definition, prohibited/permitted actions, testing windows, escalation contacts, incident procedures.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- roe-template
- metadata
- { "tags": "roe, scope, engagement, authorization, legal", "subdomain": "planning", "when_to_use": "create RoE, define scope, engagement boundaries, start new engagement", "upstream_ref": "Soundwave Rules of Engagement template — scope / window / escalation / incident procedures" }
- description
- Rules of Engagement document creation — scope definition, prohibited/permitted actions, testing windows, escalation contacts, incident procedures.
- allowed-tools
- Read Write Edit
02 资源文件 2
- 参考文档references/roe-example.json1.9 KB
- 参考文档references/validation-checklist.md1.2 KB
03 SKILL.md 正文
Rules of Engagement (RoE) Generator
The RoE is the legally binding foundation of every red team engagement. All other documents build on it.
When to Use
- Starting a new engagement
- User says "create RoE", "define scope", "set boundaries"
- Before any other planning document can be created
Workflow
Step 1: Interview the User
Drive each dimension through one ask_user_question call (per CRITICAL_RULES #8 — every operator-facing question goes through the tool). Cover these roughly in order, never bundling multiple questions in one turn:
Identity & Scope
- Engagement name (free-form,
allow_other=truewith sensible guesses) - Client organization (free-form,
allow_other=true) - Engagement type — single-select:
external/internal/hybrid/assumed-breach/physical - Start date / end date / testing window with timezone (free-form,
allow_other=true— suggest defaults like "Mon-Fri 09:00-18:00 client TZ") - In-scope targets (free-form,
allow_other=true— domains, IP ranges, cloud resources, applications) - Out-of-scope targets (free-form,
allow_other=true)
Boundaries & Escalation
7. Additional prohibited actions beyond schema defaults (multi-select with sensible options + allow_other=true)
8. Special permitted actions — phishing, password spraying, raw-socket scans (multi-select)
9. Escalation contacts — minimum 2 (client + red team lead). One ask per contact slot covering name, role, channel
10. Authorization reference / contract # (free-form, allow_other=true)
Step 2: Generate plan/roe.json
Use the RoE schema from decepticon.core.schemas. Write to the engagement directory.
See references/roe-example.json for a complete example and ../references/schema-quick-reference.md for all required fields and valid values.
Step 3: Validate
Run through the checklist in references/validation-checklist.md before presenting to user.
Generation Rules
- Always include default prohibited actions — DoS, unauthorized social engineering, unauthorized physical access, real data exfiltration, production data modification
- Scope must be specific — CIDR notation for IPs, wildcard notation for domains
- Testing window must include timezone
- At least 2 escalation contacts required
- Authorization reference must not be empty
Output
Write plan/roe.json to the engagement directory, then present a human-readable summary to the user for confirmation.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.