GHOSTNET›MOD-11 // RED TEAM OPERATIONS
CONCEPTLAB →
ADVANCED MODULE · MOD-11

RED TEAM OPERATIONS

Full campaign methodology · C2 frameworks · EDR evasion · Lateral movement · Persistence · Exfiltration · TIBER-EU

9
CHAPTERS
~3.0hr
TOTAL READ
EXPERT
DIFFICULTY
MOD-11
IDENTIFIER
BEGINNER~6 min READCHAPTER 1 OF 9

Red Team vs Pentest vs Bug Bounty

KEY POINTS · THE QUICK VERSION
  • 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
Scan these first, then read below for the depth and examples — or jump straight to the lab.

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.

◈ PICTURE IT — MTAANI EDITION

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.

DisciplineDurationObjectiveStealthSocial/PhysicalDeliverable
Bug BountyOngoingFind individual bugs in scopeNoUsually noVulnerability report per bug
Penetration Test1-4 weeksFind as many vulns as possibleOptionalRarelyComprehensive report
Red TeamWeeks-monthsReach crown jewel objectiveCriticalYes — full spectrumAttack narrative + detection gaps
Purple TeamOngoing cyclesImprove detection togetherNoVariesDetection rule improvements
👁 WATCH THIS · you don't need to run it yet — just read along
// THE SPECTRUM IN PRACTICE
# Bug Bounty
# Focus: individual CVEs in defined scope
# Mindset: find it, report it, collect reward
# NOT a full security assessment — just bug hunting

# Penetration Test
# Focus: find ALL weaknesses in defined scope
# Methodology: PTES, OWASP Testing Guide, NIST 800-115
# Deliverable: prioritised vuln list with remediation steps
# Stop before achieving real-world impact (usually)

# Red Team Engagement
# Focus: simulate a SPECIFIC threat actor reaching a SPECIFIC goal
# "Crown jewel" = domain admin creds, customer PII, source code, finance data
# Only 2-3 people in the org know it's happening (excluding blue team)
# Tests: can defenders DETECT this? Can they RESPOND in time?
# NOT just about finding vulns — about measuring defender readiness

# Purple Team
# Red attacks → Blue watches in real time → tune detection rules
# Collaborative, transparent, iterative
# Best ROI for mature security programs
What you're seeing: The same four disciplines from the table, in plain words. Notice how the focus narrows and the stakes change: a bug bounty hunts single flaws, a pentest lists them all, and a red team cares about one thing — can the defenders detect and stop a real intruder reaching the crown jewels. Read it to feel the difference in intent, not to memorise terms.
↪ Nothing to run — this just frames why red team work is planned so differently from the rest.
WARNING
Red team engagements require explicit written authorisation covering every TTP you intend to use. Social engineering employees, physical access attempts, and attacking production systems all need separate sign-off. "Get to Domain Admin" is not sufficient scope documentation.

► 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.

// TIBER-EU PHASES
# 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
RECAP · CHECK YOURSELF
  • 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
Read to the end to count this chapter
▸ READY TO PRACTISE
You've now covered enough for Lab steps 1–2 of 18. Try them in the lab while it's fresh.
OPEN LAB ▸
⚡ TEST YOURSELF
End-of-chapter quiz
A dozen questions — recall and practical. Graded, earns up to 20 XP.
PRACTISE IN THE LAB ▸
READY TO PRACTICE?
MOD-11 Interactive Lab
18 steps · 465 XP · Real commands · Flag captures
LAUNCH LAB →
← MOD-10: SOCIAL ENGINEERINGMOD-12: WIRELESS ATTACKS →