<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MITRE ATT&amp;CK on CybersecurityOS</title><link>http://www.cybersecurityos.net/tags/mitre-attck/</link><description>Recent content in MITRE ATT&amp;CK on CybersecurityOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Oct 2026 18:45:45 -0500</lastBuildDate><atom:link href="http://www.cybersecurityos.net/tags/mitre-attck/index.xml" rel="self" type="application/rss+xml"/><item><title>Detection as Code 101: How It's Done at Datadog</title><link>http://www.cybersecurityos.net/posts/secops/detection-as-code-101-datadog/</link><pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate><guid>http://www.cybersecurityos.net/posts/secops/detection-as-code-101-datadog/</guid><description>&lt;p&gt;It&amp;rsquo;s Friday afternoon. Someone tunes a noisy rule directly in the SIEM console, saves it, and logs off. Monday morning the queue is either flooded with alerts or eerily quiet, and nobody can say what changed, who changed it, or how to put it back.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s the problem in one scene: &lt;strong&gt;click-ops detection doesn&amp;rsquo;t scale.&lt;/strong&gt; Detection as code is how mature teams fix it. This post breaks down one of the clearest public examples, Datadog&amp;rsquo;s Threat Detection team, as described by Christine Le and Christopher Camacho in &lt;a href="https://www.datadoghq.com/blog/datadog-detection-as-code/"&gt;How we use Datadog for detection as code&lt;/a&gt; (Datadog, October 11, 2024). The tooling is Datadog&amp;rsquo;s. The ideas carry over to any SIEM, and I&amp;rsquo;ll show how after each section.&lt;/p&gt;</description></item></channel></rss>