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

- Skill: `itsual/red-team-basics` (Agent Skill)
- Install (CLI): `npx get-skill add itsual/red-team-basics`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/red-team-basics/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/itsual/red-team-basics

---


# 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

