RED TEAM OPERATIONS
Full campaign methodology · C2 frameworks · EDR evasion · Lateral movement · Persistence · Exfiltration · TIBER-EU
Red Team vs Pentest vs Bug Bounty
- Bug bounty = individual bugs, no persistence, immediate disclosure
- Penetration test = time-boxed, find-as-many-vulns-as-possible, stop before exfil
- Red team = APT simulation, objective-based, stealth paramount, may last months
- Purple team = red + blue collaborate to improve detection in real time
- Only red team truly tests whether defenders can DETECT AND RESPOND
Understanding the distinction between these three disciplines is foundational before studying red team techniques. Each operates under different rules, incentives, and objectives. Mixing them up leads to scope creep, legal issues, and meaningless findings.
Imagine a SACCO that hires a team to attempt a full, after-hours break-in — past the askari, the cameras, the tellers — purely to see whether anyone notices and how fast they respond. That is a red team: one agreed objective, reach the vault, by any realistic means, in the dark. A penetration test is instead the auditor who walks the building in daylight rattling every padlock and listing the loose ones; a bug bounty is a passer-by paid per loose padlock they happen to report. Same goal of safer money — very different rules of play.
| Discipline | Duration | Objective | Stealth | Social/Physical | Deliverable |
|---|---|---|---|---|---|
| Bug Bounty | Ongoing | Find individual bugs in scope | No | Usually no | Vulnerability report per bug |
| Penetration Test | 1-4 weeks | Find as many vulns as possible | Optional | Rarely | Comprehensive report |
| Red Team | Weeks-months | Reach crown jewel objective | Critical | Yes — full spectrum | Attack narrative + detection gaps |
| Purple Team | Ongoing cycles | Improve detection together | No | Varies | Detection rule improvements |
► TIBER-EU and Threat-Led Frameworks
TIBER-EU (Threat Intelligence-Based Ethical Red Teaming) is the European Central Bank framework for testing financial institutions. It mandates that red teams base their TTPs on actual threat intelligence about actors likely to target the organisation — not generic penetration testing. Similar frameworks: CBEST (UK), iCAST (Hong Kong), AASE (Australia). These are increasingly required for critical infrastructure.
# Phase 1: Generic Threat Intelligence (GTI) # External threat intel provider maps threat landscape for the sector # Identifies most likely threat actors and their TTPs # Phase 2: Targeted Threat Intelligence (TTI) # Intelligence tailored to the specific target organisation # OSINT + dark web research + past incident analysis # Phase 3: Red Team Test # Red team executes TTPs from TTI — simulating the named threat actors # Tests specific detection scenarios mapped to threat intel # Phase 4: Closure # Purple team exercise — replay attacks with blue team present # Update detection rules based on gaps found # Formal attestation letter issued by regulator
- Bug bounty = individual bugs, no persistence, immediate disclosure
- Penetration test = time-boxed, find-as-many-vulns-as-possible, stop before exfil
- Red team = APT simulation, objective-based, stealth paramount, may last months
- Purple team = red + blue collaborate to improve detection in real time
- Only red team truly tests whether defenders can DETECT AND RESPOND