<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security Leadership on CybersecurityOS</title><link>https://www.cybersecurityos.net/categories/security-leadership/</link><description>Recent content in Security Leadership on CybersecurityOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 17:39:02 +0000</lastBuildDate><atom:link href="https://www.cybersecurityos.net/categories/security-leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>The SOC Gets a New Org Chart: Five Security Operations Predictions for 2027</title><link>https://www.cybersecurityos.net/posts/secops/security-operations-2027-predictions/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.cybersecurityos.net/posts/secops/security-operations-2027-predictions/</guid><description>&lt;p&gt;Last week I argued that the bottleneck in detection engineering moved from writing rules to investigating alerts. If you missed it, start with &lt;a href="https://www.cybersecurityos.net/posts/secops/detection-engineering-2027-bottleneck-moved/"&gt;The Bottleneck Moved: Detection Engineering Heading Into 2027&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This post zooms out to the whole SOC. Detection is one function. Security operations is the system around it: who triages, who acts, what telemetry matters, what the SOC owns, and whose clock it runs on.&lt;/p&gt;
&lt;p&gt;All five of those are changing at once. By the end of 2027, a lot of SOCs will have a different org chart than the one on the wall today.&lt;/p&gt;</description></item><item><title>The Bottleneck Moved: Detection Engineering Heading Into 2027</title><link>https://www.cybersecurityos.net/posts/secops/detection-engineering-2027-bottleneck-moved/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.cybersecurityos.net/posts/secops/detection-engineering-2027-bottleneck-moved/</guid><description>&lt;p&gt;Twenty-two seconds. That&amp;rsquo;s the median time, per Mandiant&amp;rsquo;s M-Trends 2026, for initial access to be handed off from one threat actor to the next. One crew gets in. Another takes over.&lt;/p&gt;
&lt;p&gt;Now look at your queue. An alert fires. It waits. Someone picks it up, pivots across four consoles, decides it&amp;rsquo;s probably the backup job again, and closes it. The rule worked. The detection still failed.&lt;/p&gt;
&lt;p&gt;That gap is the story of detection engineering heading into 2027. For a decade the constraint was signal creation. Could we write enough good rules, fast enough, across enough telemetry? That problem hasn&amp;rsquo;t gone away. But it&amp;rsquo;s no longer the binding constraint. The bottleneck moved to signal consumption: who or what investigates the alert, and how fast.&lt;/p&gt;</description></item></channel></rss>