ISOC Is Microsoft's Answer to Agent-Speed Attacks. The Loop Still Needs Human Judgment
TL;DR On September 23, 2026, Microsoft announced the integrated security operations center (ISOC) in Microsoft Defender, bringing SIEM and threat protection together on one foundation. The argument is architectural: security cannot operate at AI speed when protection and operations are separate systems; every handoff and integration boundary slows defenders down, and agents inherit that…
On September 23, 2026, Microsoft unveiled the integrated security operations center (ISOC) within Microsoft Defender, unifying Security Information and Event Management (SIEM) and threat protection into a single foundation. The reasoning behind this move is straightforward: security cannot operate at AI speed when protection and operations are separate systems; each handoff and integration boundary slows down defenders at every turn, and agents acquire this complexity as well.
Microsoft's announcement follows two days after the publication of Storm-3168, an agentic-driven cloud attack where compromised service principals executed 150+ destructive or credential-collection operations within a 35-minute timeframe. Among these, there were 100+ storage-account deletion attempts within a 7-minute span. The attack exemplified automation, not manual intervention, as the operations followed the identity's existing Azure role assignments.
The Storm-3168 attack succeeded precisely because a compromised identity carried extensive Contributor roles.
Microsoft's statement of "Strategy stays human. Scale becomes autonomous" underscores the importance of human oversight even as technology takes over more responsibilities. The convergence that makes agentic defense possible is emphasized in Microsoft's announcement; however, the convergence should be accompanied by a strong authentication and least privilege model. Storm-3168 demonstrates that detection alone is not enough, as the integrated loop can only respond to what identity policy allows.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.