--- title: "Microsoft warns patch window is collapsing, urges shift to network-level containment" url: https://daily.dev/posts/microsoft-warns-patch-window-is-collapsing-urges-shift-to-network-level-containment-rbtcbzvie source_url: https://www.csoonline.com/article/4214135/microsoft-warns-patch-window-is-collapsing-urges-shift-to-network-level-containment.html type: article source: "CSO Online" published: 2026-08-26T11:10:30.609Z updated: 2026-08-26T11:10:55.913Z tags: ["security", "azure"] reading_time: 5 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Microsoft warns patch window is collapsing, urges shift to network-level containment **[CSO Online](https://daily.dev/sources/csoonline)** · 5 min read · 0 upvotes · 0 comments ## Summary Microsoft's Azure Networking VP Igor Sakhnov argues that the gap between vulnerability disclosure and exploitation has shrunk so much that traditional patch-and-deploy cycles can no longer keep enterprises safe, urging a shift toward network-level compensating controls like segmentation, WAF/IPS policies, and temporary isolation to reduce exposure while patches are still pending. Gartner analyst Shriya Mehrotra agrees the compression is real for high-risk, internet-facing systems but calls the proposed approach more an evolution of existing Zero Trust and segmentation practices than a wholesale shift. Both she and Kanerika's Bhupendra Chopra caution that most enterprises lack the asset visibility needed to implement real-time containment reliably, and that temporary workarounds risk becoming permanent, unpatched liabilities. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does Microsoft say patching alone is no longer enough to manage vulnerabilities? Attack timelines have compressed so much that exploitation now often happens within hours of disclosure, while enterprises still typically need weeks to test and deploy patches across complex hybrid and multicloud environments. Microsoft's Azure Networking VP Igor Sakhnov calls this the 'window between awareness and remediation' and recommends network-level compensating controls, such as segmentation and WAF/IPS policies, to reduce exposure while patches are still pending. _Track evolving vendor guidance on vulnerability response and compensating controls on daily.dev._ ### What are the risks of relying on network-level containment instead of patching vulnerabilities? Containment can miss unmanaged, encrypted, identity-based, or alternative attack paths, and overly broad network rules can disrupt legitimate business services. There is also a practical risk that temporary fixes become permanent: a network rule blocks a risky path, nobody circles back to patch the underlying system, and months later that workaround becomes an unmanaged liability. Analysts stress containment should buy time, not replace patching. _Security teams weighing containment versus patching tradeoffs can follow this debate on daily.dev._ ## Similar posts on daily.dev - [Flaw surge fuels need for CISOs to rethink vulnerability management](https://daily.dev/posts/flaw-surge-fuels-need-for-cisos-to-rethink-vulnerability-management-otbfbwnn6) · CSO Online · 0 upvotes · 0 comments - [Microsoft’s 3-day patching directive comes with added operational risk](https://daily.dev/posts/microsoft-s-3-day-patching-directive-comes-with-added-operational-risk-hbmjvytiq) · CSO Online · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#azure](https://daily.dev/tags/azure) [View this post on daily.dev](https://daily.dev/posts/microsoft-warns-patch-window-is-collapsing-urges-shift-to-network-level-containment-rbtcbzvie)