red-team-opslisted
Install: claude install-skill noahfranklin/gideon
# Red Team Operations (Engagement Lifecycle)
The umbrella methodology that ties the domain skills together into a coherent, **authorized** red-team engagement emulating a real threat actor against defined objectives. Mapped to **MITRE ATT&CK** and aligned with PTES / TIBER-style structured testing.
## 0. Authorization & safety gate
- [ ] Signed authorization / statement of work with named signatories.
- [ ] Rules of engagement: scope, objectives ("flags"), off-limits systems/data, allowed techniques, hours, intensity.
- [ ] **Deconfliction process** and 24/7 emergency contacts; SOC awareness level (announced/unannounced) agreed.
- [ ] Safety rules: no destruction, fragile-system exclusions, data-minimization, secure evidence handling.
- [ ] Legal review and get-out-of-jail letter for on-site work.
## 1. Threat model & emulation plan
- Choose a threat profile appropriate to the org; define objectives in business terms (reach X data, prove Y impact).
- Map planned TTPs to MITRE ATT&CK for coverage and later blue-team comparison. Pair with `threat-model`.
## 2. The attack lifecycle (orchestration map)
```
Recon ─────────────► recon-osint
Initial access ────► web-app-pentest / api-security-audit / social-engineering /
wireless-pentest / network-device-pentest / external network-pentest
Execution/foothold ► (payload delivery per RoE)
Priv esc ──────────► privilege-escalation
Discovery/cred ────► post-exploitation
Lateral movement ──► post-exploitation / ac