Purple › Module 5 › Lesson 4
Lab — Testing
Pack unit test rules, replay logs, and baselines cards — testing file from $PURPLE_LAB only.
Visual · t35_testing_lab
Lab: testing pack. $PURPLE_LAB only. Original Cyberlium.
Opening
Testing pack merges unit tests to replay to baselines — paperwork before atomic simulation module.
Lessons 5-1–5-3 named unit test rules, replay logs, and baselines. This lab merges three sections into one $PURPLE_LAB testing artifact with M1 ethics and M4 Sigma cross-references. No live victim logs or stranger-network telemetry — detection testing paperwork only. Next: Quiz — Testing Detections.
1. Lab contract: testing pack
Create $HOME/cyberlium-lab/t35-m05-l04-testing-lab.txt merging unit test rules, replay logs, and baselines sections with $PURPLE_LAB fictional T1059 rule and M1/M4 cross-references.
Optional: link replay log set to purple exercise from M2 concepts pack.
Command guide
Try these commands — Lab contract: testing pack
═══ LINUX / macOS (Terminal Practice) ═══
Check system state and user context
Command — copy this
id whoami uname -a
Inspect network sockets listening for connections
Command — copy this
ss -tuln 2>/dev/null || netstat -tuln
Audit active processes
Command — copy this
ps aux | grep -v "\[" | head -15
═══ WINDOWS (POWERSHELL) ═══ Query user identity and system information
Command — copy this
whoami /all Get-ComputerInfo | Select-Object CsName, OsName, OsVersion
Primary tools to practice this lesson: jq, grep. Reference sites: jq manual (https://jqlang.github.io/jq/manual/); Sigma (https://sigmahq.io/); Elastic detection (https://www.elastic.co/guide/en/security/current/rules-ui.html). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Cross-check ethics
Grep for live victim logs, stranger-network telemetry, production SIEM exports — remove. Confirm all fixtures are $PURPLE_LAB fictional.
Test fixtures use synthetic or lab-captured data — no real victim events.
3. Lock the proof
chmod 600 on the pack. Quiz next — then Atomic Named.
Testing literacy feeds atomic simulation lessons in M6.
4. What you ship: testing pack for $PURPLE_LAB
Merged unit test, replay, baseline sections. $PURPLE_LAB named. chmod 600.
5. What you record before the next lesson
Date. Testing pack path. $PURPLE_LAB named. File t35-m05-l04-testing-lab.txt chmod 600.
6. Wrong vs right: stranger networks vs YOUR purple lab
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Include live victim log fixtures. Skip baselines section.
Right
Write YOUR testing pack for $PURPLE_LAB. chmod 600. Next: Quiz — Testing Detections.
Mission: freeze YOUR testing pack on disk
1) Merge M5 literacy sections. 2) Confirm fictional fixtures only. 3) Link M1/M4 cross-refs. 4) chmod 600.
Stuck? Ask Cyberlium AI Mentor
One governed testing pack beats deploying rules with zero validation.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: Testing pack should include baselines with FP thresholds.
True or False
Knowledge Check
APPLY: Testing pack supports:
Multiple choice