SOC › Module 2 › Lesson 4
Lab — Hunting
Pack methodology, hypothesis, and hunt loop cards — hunting basics file from $HUNT_LAB only.
Visual · t30_hunting_lab
Lab: hunting basics pack. $HUNT_LAB only. Original Cyberlium.
Opening
Hunting pack ties methodology to hypothesis to loop — paperwork before ATT&CK mapping module.
Lessons 2-1–2-3 named hunt methodology, hypothesis writing, and the hunt loop. This lab merges three cards into one $HUNT_LAB hunting artifact with optional jq intent on YOUR auth jsonl. No live tenant access — hunt literacy paperwork only. Next: Quiz — Threat Hunting Basics.
1. Lab contract: hunting basics pack
Create $HOME/cyberlium-lab/t30-m02-l04-hunting-lab.txt merging methodology, hypothesis, and loop sections with $HUNT_LAB scenario ID and M1 ethics cross-reference.
Optional: paste conceptual jq one-liner for failed-auth count on YOUR jsonl — no real usernames from production.
Command guide
Try these commands — Lab contract: hunting basics pack
═══ 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: jq, python3. Reference sites: jq manual (https://jqlang.github.io/jq/manual/); MITRE T1078 (https://attack.mitre.org/techniques/T1078/); Splunk hunt (https://docs.splunk.com/Documentation/ES). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Cross-check refusal boundaries
Grep pack for production tenant URLs, live hunt IDs, exploit scripts, offensive playbooks — redact or delete. Hunting pack stays documentary.
Update pack if you rotate lab sample — note new jsonl filename.
3. Lock the proof
chmod 600 on the pack. Quiz next — then ATT&CK Mapping.
Hunting basics literacy feeds ATT&CK lessons in M3.
4. What you ship: hunting basics pack for $HUNT_LAB
Merged methodology, hypothesis, loop sections. $HUNT_LAB named. NO live consoles. chmod 600.
5. What you record before the next lesson
Date. Hunting pack path. $HUNT_LAB named. File t30-m02-l04-hunting-lab.txt chmod 600.
6. Wrong vs right: stranger prod vs YOUR hunt telemetry
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Include production Splunk savedsearch in pack. Skip hypothesis section.
Right
Write YOUR hunting basics pack for $HUNT_LAB. chmod 600. Next: Quiz — Threat Hunting Basics.
Mission: freeze YOUR hunting basics pack
1) Merge M2 literacy sections. 2) Confirm zero production tenant refs. 3) Link M1 ethics cross-ref. 4) chmod 600.
Stuck? Ask Cyberlium AI Mentor
One governed hunting pack beats ten unauthorized dashboard screenshots.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: Hunting pack should reference $HUNT_LAB sample scenario.
True or False
Knowledge Check
APPLY: Hunting pack should include:
Multiple choice