Skip to content

Purple Team Playbook Simple

github-actions[bot] edited this page Nov 15, 2026 · 1 revision

This playbook is designed to be modular and expandable - so you can plug in new techniques, scripts, and lessons learned over time. It's practical and organized for your own lab or for professional purple team exercises.

Your living guide for designing, executing, and improving detection and defense.


๐ŸŽฏ Purpose

Integrate offensive and defensive techniques to continuously test, measure, and improve detection and response capabilities.

โš™๏ธ Function

A three-role, lab-first exercise cycle (Red Operator attacks โ†’ Blue Analyst monitors/tunes โ†’ Purple Facilitator coordinates and documents) run against a defined lab environment (isolated network, EDR, SIEM, Atomic Red Team/CALDERA/Metta). This is the entry-level version - for the same purple-team concept with named enterprise tooling, formal workflow phases, and reporting/metrics dashboards, see PurpleTeam_Detailed.md; for a scripting-focused variant built around Python/PowerShell/Batch attack scripts specifically, see PurpleTeam_Multi-Scrip.md.

๐Ÿ† Goal

Get a small team or individual practitioner running a first purple team exercise in a home lab or small environment without needing enterprise SIEM/EDR licensing or a formal exercise framework first.

๐Ÿ“‹ When to Use

  • Standing up your first purple team exercise in a personal lab or small org
  • Validating that basic detection coverage (SIEM ingestion, EDR alerting) actually works before investing in a formal program
  • Training new red or blue team members on the collaborative purple-team concept

Scope:

  • Simulate real-world attacker tactics (Red Team)
  • Validate detection and log coverage (Blue Team)
  • Tune and test SIEM rules, EDR alerts, and response playbooks
  • Document tests and outcomes for audit & improvement

Roles

Role Responsibility
๐Ÿ•ต๏ธ Red Operator Design & run attack simulations
๐Ÿ›ก๏ธ Blue Analyst Monitor SIEM, review alerts, fine-tune detection
๐Ÿค Purple Facilitator Coordinate exercises, document findings, drive improvements

Lab Environment

โœ… Components:

  • Isolated test network
  • Endpoint hosts (Windows/Linux)
  • EDR installed
  • SIEM ingesting logs
  • C2 / automation tools (Atomic Red Team, CALDERA, Metta)

Common Tools

Category Tool Purpose
Simulations Atomic Red Team, CALDERA, Metta Run TTPs
C2 Mythic, Cobalt Strike (licensed) Advanced Red testing
SIEM Elastic, Splunk, Graylog Log collection & detection
EDR Microsoft Defender for Endpoint, CrowdStrike Endpoint telemetry
Scripting Python, PowerShell Custom tests & automations

Execution Workflow

๐Ÿ—‚๏ธ Step 1 - Select TTP

โœ… Pick from MITRE ATT&CK
โœ… Document tactic, technique ID, scenario
โœ… Example: T1110 - Brute Force

๐Ÿ—‚๏ธ Step 2 - Simulate

โœ… Run manual or automated attack:

Invoke-AtomicTest T1110

OR

# Python custom brute force tester
import requests

# loop over creds

๐Ÿ—‚๏ธ Step 3 - Monitor

โœ… Confirm:

  • Logs generated?
  • SIEM parsing correct fields?
  • Alert fired?

๐Ÿ—‚๏ธ Step 4 - Document

Record:

Field Example
TTP ID T1110
Attack Script Atomic Red Team
SIEM Rule Brute Force Detection
Outcome Pass/Fail
False Positives Yes/No
Improvement Add user lockout

๐Ÿ—‚๏ธ Step 5 - Tune

โœ… Adjust:

  • Detection thresholds
  • Log source configs
  • Parser mappings

โœ… Re-run until detection is reliable.


Example Playbook Entries

โœ… Playbook Entry - Brute Force Test

Item Details
TTP T1110 - Brute Force
Goal Confirm SIEM detects repeated login failures
Method Atomic Red Team Invoke-AtomicTest T1110
Logs Auth logs, Windows Event 4625
SIEM Rule Failed Login Attempts > 5
Expected Alert in SIEM dashboard
Notes Verify lockout policy

โœ… Playbook Entry - Malicious PowerShell

Item Details
TTP T1059 - Command and Scripting Interpreter
Goal Detect suspicious PowerShell
Method Python script to run Invoke-WebRequest
Logs PowerShell logs, Process CommandLine
SIEM Rule Process: powershell.exe with suspicious flags
Expected SIEM alert
Notes Tune for false positives (legit scripts)

โœ… Playbook Entry - DNS Tunneling

Item Details
TTP T1071.004 - Application Layer Protocol: DNS
Goal Detect unusual DNS query patterns
Method Python script to simulate repeated encoded DNS queries
Logs DNS server logs
SIEM Rule Excessive DNS TXT or long queries
Expected Alert or log spike
Notes Validate against legit big TXT queries (CDN, etc)

Reporting & Metrics

Metric Goal
๐Ÿ“ˆ Coverage % of ATT&CK techniques tested
๐Ÿšจ Alert Accuracy True positives vs false positives
โฑ๏ธ Response Time Time from detection to triage
๐Ÿ“‘ Documentation Detailed test evidence per TTP

Improvement & Backlog

โœ… Maintain a Purple Team Backlog:

TTP Status Next Test Date Notes
T1003 - Credential Dumping Not Tested July 2025 Needs lab config
T1547 - Persistence Tested Quarterly Verify detection resilience

Automation Ideas

โœ… Use:

  • Python scripts to run tests nightly
  • Jenkins or GitLab CI to run pipelines
  • Alerts โ†’ Slack, Teams, or Email

โœ… Example:

0 2 * * * python3 ~/purple/run_tests.py

๐Ÿ”‘ Tips

โœ… Test in a safe, isolated lab
โœ… Always get written approvals for live network tests
โœ… Version-control scripts & rules
โœ… Share findings with blue team for tuning
โœ… Log everything - repeatable evidence is gold!


๐Ÿ“Ž Template: New Playbook Entry

Use this for each new TTP test. The empty cells are engagement-specific and must be completed only from the authorized exercise plan and observed telemetry. Enter Not tested, Not observed or Unknown where appropriate. An expected SIEM alert is not evidence of a detected technique; use synthetic fixtures before performing any approved canary activity.

Field Example
TTP ID
Tactic
Goal
Method
Tools
Log Source
SIEM Rule
Expected Result
Actual Result
Improvement
Next Steps

Security and Ethical Considerations โš ๏ธ

IMPORTANT: These tools are for authorized security testing only. Unauthorized use is illegal.

  • Marauder Use: Get written permission before testing any network. Only test networks you own or have explicit authorization to test.
  • Cracking Use: All cracking attempts (Hashcat) must be done in an isolated lab environment against hashes you are authorized to possess.
  • Legal Compliance: Strictly comply with all local laws and regulations.

Legal Use Cases:

  • Penetration testing with client authorization.
  • Testing your own home or lab network security.
  • Security research in isolated lab environments.

Related Files


๐Ÿ“„ Source: PlayBooks/PurpleTeam_Simple.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Playbooks

Clone this wiki locally