Incident › Module 1 › Lesson 2
Lab Scenarios Only
Lab scenarios only means YOUR fictional tabletop injects under $IR_LAB — labeled courseware cases, self-authored timelines — document scenario scope in notes before any IR drill.
Visual · t34_lab_scenarios_only
Lab scenario scope. $IR_LAB only. Original Cyberlium.
Opening
The scenario owner is part of scope — Cyberlium refuses IR drills on live victim breaches or stranger production networks you do not have authorization to touch.
Your IR lab scenarios are fictional injects YOU authored — CYBERLIUM-LAB-001 phishing tabletop, ransomware tabletop with no payload, insider-threat paper exercise on example.local assets. Drills live in $IR_LAB only — never copied from live breach reports or run against stranger cloud tenants. Cyberlium maps allowed scenario inventory on YOUR $IR_LAB — inject title, phase, fictional org label — never 'borrowed' employer production incidents or scraped live victim timelines. Next: No Stranger IR.
1. Allowed lab scenario surfaces (named)
Self-authored tabletop injects with fictional org names. Courseware IR packs with explicit training labels. Paper exercises on example.local or lab-only VLAN diagrams. Ransomware tabletop narratives with zero payload deployment.
On $IR_LAB, list scenario title, PICERL phase focus, and fictional org label — never paste live victim breach timelines from public dumps.
Command guide
Try these commands — Allowed lab scenario surfaces (named)
═══ LINUX / BASH (SOC Analyst Triage) ═══
Filter system logs for security-relevant warnings and errors
Command — copy this
journalctl -p 3 -xb --no-pager | head -20
Search for suspicious persistent cron entries or service changes
Command — copy this
ls -lat /etc/cron.* /etc/systemd/system/ | head -15
═══ WINDOWS POWERSHELL ═══ Triage recent system service installations (Event 7045)
Command — copy this
Get-WinEvent -FilterHashtable @{LogName='System';Id=7045} -MaxEvents 5 -ErrorAction SilentlyContinue | Format-Table TimeCreated, Message -WrapCheck open listening network connections with process owners
Command — copy this
Get-NetTCPConnection -State Listen | Select-Object LocalAddress, LocalPort, OwningProcess | Sort-Object LocalPort
Primary tools to practice this lesson: grep, curl. Reference sites: NIST SP 800-61 (https://csrc.nist.gov/publications/detail/sp/800-61/rev-2/final); CISA Stop Ransomware (https://www.cisa.gov/stopransomware); FIRST (https://www.first.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Why lab scenario scope matters before drills
IR tools — ticketing, EDR isolation, firewall rules — are powerful on any network. Scope is what keeps practice legal and ethical. Employer production incidents, live breach replays, and stranger-network isolation are out of scope.
If you cannot answer 'who authored this scenario and is it labeled lab-only?', pause and fix scope notes before running the drill.
3. Lab scenario inventory habit
Forbidden: importing live ransomware incident timelines because they 'look like training.' Allowed: scenario inventory row — title, phase, fictional org, source = $IR_LAB self-authored.
Ship: lab scenario inventory row for three fictional injects. Next: No Stranger IR.
4. What you ship: lab scenario inventory row for $IR_LAB
Three fictional tabletop injects with phase labels. $IR_LAB named. NEVER live victim replays. chmod 600.
5. What you record before the next lesson
Date. Lab scenario inventory row. $IR_LAB named. File t34-m01-l02-lab-scenarios-only.txt chmod 600.
6. Wrong vs right: stranger networks vs YOUR IR tabletop
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Import live breach timeline because lab scenarios are boring. Skip scenario label because 'it's just a drill.'
Right
Write lab scenario inventory row for YOUR $IR_LAB. Next: No Stranger IR.
Mission: document YOUR lab scenario inventory
1) Write three fictional tabletop injects. 2) Label each as lab-only with PICERL phase focus. 3) Confirm zero live victim scenarios. 4) chmod 600.
Stuck? Ask Cyberlium AI Mentor
Tabletop injects exist for documentation — use them instead of live victim breach replays.
Knowledge Check
APPLY: Lab scenarios only on Cyberlium means:
Multiple choice
Knowledge Check
APPLY: True or False: Ransomware tabletop on $IR_LAB uses narrative only — no payload deployment.
True or False
Knowledge Check
APPLY: Before running IR drills you should:
Multiple choice