Detection engineering

Detection engineering is where most of my work meets: collecting Windows and Sysmon telemetry, writing detection rules in the Sigma format, mapping each rule to the MITRE ATT&CK technique it is meant to catch, and then running that technique to see whether the rule actually fires.

The projects and write-ups below are that loop in practice: a SIEM built from scratch, an attack-simulation engine that measures its coverage, an Active Directory lab where each attack phase has a matching detection, and the threat detectors inside ARGUS.

Projects

Write-ups

Sigma rules

Three of the rules from my SIEM, each mapped to the ATT&CK technique it detects. The full set is on GitHub.

  • Credential Dumping Tool ExecutionT1003 OS Credential DumpingCritical
  • Encoded PowerShell Command ExecutionT1059.001 Command and Scripting Interpreter: PowerShellHigh
  • Suspicious Access to Administrative ShareT1570 Lateral Tool TransferMedium

Read the detection logic All rules on GitHub

Techniques and tools

Sigma
The vendor-neutral format the SIEM’s detection rules are written in.
MITRE ATT&CK
Every rule and detector is tagged with the technique it detects, so coverage can be counted technique by technique.
Atomic Red Team
The attack techniques Sentinel BAS runs against the SIEM to check that each detection fires.
Sysmon
Windows telemetry from the Active Directory lab, where each attack path is mapped to what it leaves in the logs.
Attack-chain correlation
The SIEM links related alerts within a 60-minute window into a single chain.