<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security Posture on Erwin Staal</title>
    <link>https://staal-it.nl/tags/security-posture/</link>
    <description>Recent content in Security Posture on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/security-posture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforcing Microsoft Defender for Cloud Across 30&#43; Subscriptions With Bicep</title>
      <link>https://staal-it.nl/posts/azure-defender-for-cloud-settings/</link>
      <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/azure-defender-for-cloud-settings/</guid>
      <description>&lt;p&gt;Security posture management is one of those things that starts manually and stays manual for too long. Someone enables Defender for Cloud on a subscription in the portal, picks a few plans, saves. Six months later a new subscription appears, nobody remembers exactly which plans were enabled on the others, and the configuration drifts. An audit comes along and suddenly you&amp;rsquo;re comparing screenshots.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
