Repository navigation
Purple Team Playbook Simple
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.
Integrate offensive and defensive techniques to continuously test, measure, and improve detection and response capabilities.
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.
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.
- 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
- 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
| 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 |
- Isolated test network
- Endpoint hosts (Windows/Linux)
- EDR installed
- SIEM ingesting logs
- C2 / automation tools (Atomic Red Team, CALDERA, Metta)
| 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 |
โ
Pick from MITRE ATT&CK
โ
Document tactic, technique ID, scenario
โ
Example: T1110 - Brute Force
โ Run manual or automated attack:
Invoke-AtomicTest T1110OR
# Python custom brute force tester
import requests
# loop over credsโ Confirm:
- Logs generated?
- SIEM parsing correct fields?
- Alert fired?
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 |
โ Adjust:
- Detection thresholds
- Log source configs
- Parser mappings
โ Re-run until detection is reliable.
| 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 |
| 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) |
| 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) |
| 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 |
| TTP | Status | Next Test Date | Notes |
|---|---|---|---|
| T1003 - Credential Dumping | Not Tested | July 2025 | Needs lab config |
| T1547 - Persistence | Tested | Quarterly | Verify detection resilience |
- Python scripts to run tests nightly
- Jenkins or GitLab CI to run pipelines
- Alerts โ Slack, Teams, or Email
0 2 * * * python3 ~/purple/run_tests.pyโ
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!
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 |
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.
- README.md - PlayBooks section index
๐ Source: PlayBooks/PurpleTeam_Simple.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Playbooks
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics