profile

CybersecurityOS 🛡️

Your SIEM rules have no git log


It's Friday afternoon. Someone tunes a noisy rule in the SIEM console and logs off. Monday, the queue is either flooded or silent, and nobody knows what changed.

That's click-ops detection, and it's why mature teams are moving to detection as code: version control, peer review, testing, and CI/CD applied to detection rules.

This week I broke down one of the clearest public examples, Datadog's Threat Detection team, based on the write-up by Christine Le and Christopher Camacho. Inside:

  • How they write every rule as a Terraform file, grouped by data source
  • The repo layout that separates what a rule is from where it runs
  • Hourly attack simulation that proves rules still fire
  • A six-stage pipeline, and why each stage matters
  • The one Terraform mistake that froze all their changes, and the fix

Every section ends with an "On any SIEM" note, so it applies whether you run Splunk, Sentinel, Elastic, or Chronicle. There's also a section on why DaC turns audit prep in regulated environments from a scramble into a query, and a week-by-week 30-day plan to get started.

Read the full breakdown →

Then hit reply: do your rules live in Git, in the console, or somewhere in between?

Michael

CybersecurityOS 🛡️

Engineering security from first principles. I'm d0uble 3L, I write CybersecurityOS, where I break down secure-by-design architecture, DevSecOps, cloud security, and emerging-tech risk into practical frameworks for engineers, leaders, and teams. Weekly perspectives, clarity over complexity.

Share this page