Red Team Basics

Understand red team operations at a program level — objectives, rules of engagement, detection testing, and how to consume findings for defense improvement. Use when establishing offensive security programs or integrating red team outcomes into blue team capability.

itsual Updated 7 repo stars

File contents

Red Team Basics

Overview

Red teams emulate adversaries to test detection and response, not only to find vulnerabilities. Program value is measured in defensive improvement.

When to Use

  • Building offensive security capability
  • Testing SOC detection and response
  • Adversary emulation exercises
  • Executive understanding of real-world attack paths

Core Practices

  • Define objectives tied to business-relevant scenarios
  • Set strict rules of engagement and safety constraints
  • Emulate tactics relevant to your threat model
  • Collaborate on detection opportunities during/after operations
  • Track purple outcomes: new detections, control fixes
  • Avoid purely “gotcha” culture that destroys trust

Principles

  • Red teaming ≠ vulnerability scanning
  • Permission and scope are non-negotiable
  • Finding paths is useful; measuring detection gaps is more useful
  • Secrecy levels should match exercise goals (announced vs limited-know)

Verification

  • RoE and objectives are written
  • Findings map to detection or control improvements
  • Safety and escalation paths are clear

itsual/agent-skills-collection commit b661e45eaa

Frequently asked questions

npx get-skill add itsual/red-team-basics