Skip to main content

Phase 5: Validation Results Summary

Phase 5: Validation Results Summary — 14 PASS / 1 PARTIAL / 1 FAIL across 16 rule checks

Full run: ansible-playbook playbooks/validate.ymlok=70 changed=42 failed=0

StepDetectionRuleResult
21det_mw_0001Process spawnPASS
22det_mw_0002Shell from servicePASS
23det_mw_0003Rule A (-e + Base64)PASS
23det_mw_0003Rule B (IEX + DownloadString)PASS
24det_mw_0004EID 7 ImageLoadPARTIAL
25det_mw_0005Rule A (OutlookMicrosift)PASS
25det_mw_0005Rule C (WSF in Startup)PASS
26det_mw_0006schtasks /mo 43PASS
27det_mw_0007Rule A (RMM from \Temp)PASS
27det_mw_0007Rule B (RMM from PS parent)PASS
28det_mw_0008aEID 3 TelegramFAIL
29det_mw_0008bEID 22 DNS tunnelingPASS
30det_mw_0009Rule A (SecurityCenter2 EID 4104)PASS
30det_mw_0009Rule B (wmic SecurityCenter2)PASS
31det_mw_0010Rule A (LSASS EID 10)PASS
31det_mw_0010Rule C (.dmp EID 11)PASS

14 PASS / 1 PARTIAL / 1 FAIL across 16 rule checks.

PARTIAL — det_mw_0004 (DLL Side-Loading)

Root cause: a 4-byte MZ stub is not a valid loadable DLL — the Windows loader rejects it before generating an EID 7 event. The detection rule and Sysmon config are correct. Fix requires a real compiled DLL or Google Chrome installed on the lab VM to provide a genuine Goopdate.dll. Coverage score: 3.

FAIL — det_mw_0008a (Telegram Bot API C2)

Root cause: VirtualBox NAT translates outbound connections — Sysmon captures a connection to 10.0.2.2:443, not api.telegram.org:443. The detection rule is correct. Fix requires a host-only or bridged NIC with direct internet access on the VM. Coverage score: 3.