// Defense

Explore Detection Engineering

Write detections that survive contact with production noise, not just the demo.

Anyone can block a hash. The question this topic keeps asking is what happens ten minutes later, after the attacker recompiles and the same technique walks straight past your rule. Nugget starts you where the field actually starts: what evidence does this behavior leave, not what indicator can I paste into a blocklist.

You'll map adversary techniques to ATT&CK not as vocabulary to memorize but as a coverage map — the thing that tells you where you're blind. Then you write the logic itself in Sigma: the detection block, the filters that keep it from paging on-call at 3am, the metadata that lets another analyst read your intent without running the rule first.

None of it counts until you've proven it fires. Nugget pushes you toward the loop practitioners actually run — write the rule, fire the real technique, watch what happens — because a detection nobody's tested against reality is a hypothesis wearing a badge.

// What a session feels like

You bring the questions. Nugget asks the next one.

  • Nugget sketches a process tree on the whiteboard — Word spawning encoded PowerShell — and asks you what a hash-based rule would catch here versus what a behavioral one would. You work out why the hash dies in a recompile and the behavior doesn't.
  • In the terminal, you draft a Sigma rule's detection and filter blocks against a sample of noisy production-like logs Nugget lays out, and get asked what happens to your false-positive rate if you drop the parent-process condition.
  • You run an Atomic Red Team test against a Docker lab Nugget's set up, then get walked through the alert queue it actually produced — or didn't — and asked to explain the gap between what you wrote and what fired.

Start exploring Detection Engineering tonight — a 30-day trial, cancel anytime.

Start your 30-day trial