<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cloud Security on Wolkwacht</title>
    <link>https://wolkwacht.nl/topics/cloud-security/</link>
    <description>Recent content in Cloud Security on Wolkwacht</description>
    <image>
      <title>Wolkwacht</title>
      <url>https://wolkwacht.nl/images/branding/feature-image.png</url>
      <link>https://wolkwacht.nl/images/branding/feature-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/topics/cloud-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secrets Management Showdown: Azure Key Vault CSI Driver vs. External Secrets Operator</title>
      <link>https://wolkwacht.nl/posts/2026-09-05_secrets-management-showdown--azure-key-vault-csi-driver-vs-external-secrets-operator/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/2026-09-05_secrets-management-showdown--azure-key-vault-csi-driver-vs-external-secrets-operator/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;Two secrets-management paths lead from a secure vault into Kubernetes workloads&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/feature.svg&#34;&gt;&lt;/p&gt;
&lt;p&gt;The real question is not whether to use the Azure Key Vault provider for the Secrets Store CSI Driver or the External Secrets Operator (ESO). Instead, it&amp;rsquo;s whether your workload should access secret data as &lt;strong&gt;mounted files&lt;/strong&gt; or via &lt;strong&gt;native Kubernetes Secret objects&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;That choice influences application design, rotation, incident handling, RBAC, observability, Helm compatibility, and GitOps. In short: &lt;strong&gt;CSI offers a more secure default for applications that consume files; ESO provides a more practical platform default when Kubernetes-native compatibility is a priority.&lt;/strong&gt; This decision involves both GitOps and security considerations.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KubeBuddy: An Agentless Second Opinion for Kubernetes</title>
      <link>https://wolkwacht.nl/posts/2026-08-25_kubebuddy--an-agentless-second-opinion-for-kubernetes/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0200</pubDate>
      <guid>https://wolkwacht.nl/posts/2026-08-25_kubebuddy--an-agentless-second-opinion-for-kubernetes/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;An external diagnostic drone scans a Kubernetes cluster without entering its boundary&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/kubebuddy-feature.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Kubernetes is very good at reporting desired state. A Deployment can be available while its pods restart every few hours. A cluster can show green nodes while workloads have no disruption budgets, probes, resource limits, or network isolation. Dashboards show signals; they do not necessarily connect them into an operational judgment.&lt;/p&gt;
&lt;p&gt;That is the gap &lt;a href=&#34;https://kubebuddy.io/&#34;&gt;KubeBuddy&lt;/a&gt; tries to fill. The open-source KubeDeck project is a Go-based command-line scanner that connects through an existing Kubernetes context and evaluates cluster health, workloads, security, RBAC, networking, storage, and configuration. It can add provider-specific checks for AKS and GKE and emit terminal, HTML, JSON, and CSV output. There is no controller, Helm release, or long-running agent to install in the cluster.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Secure Azure Kubernetes Service (AKS)</title>
      <link>https://wolkwacht.nl/posts/secure-azure-kubernetes-service-aks/</link>
      <pubDate>Thu, 13 Aug 2026 11:01:01 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/secure-azure-kubernetes-service-aks/</guid>
      <description>Azure Kubernetes Service (AKS) removes most of the undifferentiated heavy lifting of running Kubernetes, but it does not remove your responsibility for securing what runs on top of it.</description>
    </item>
    <item>
      <title>Azure Kubernetes Application Network, Part 2: Zero-Trust and Multi-Cluster Patterns</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-2-zero-trust-and-multi-cluster-patterns/</link>
      <pubDate>Sun, 07 Jun 2026 15:18:29 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-application-network-part-2-zero-trust-and-multi-cluster-patterns/</guid>
      <description>In Part 1, we discussed the AppNet architecture, setup process, and waypoint model. This second part shifts focus from mechanics to…</description>
    </item>
    <item>
      <title>When Kubernetes Lies:</title>
      <link>https://wolkwacht.nl/posts/when-kubernetes-lies/</link>
      <pubDate>Thu, 19 Feb 2026 07:29:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/when-kubernetes-lies/</guid>
      <description>Truth inside AKS with Inspektor Gadget</description>
    </item>
    <item>
      <title>Cloud Security Is a System, Not a Stack</title>
      <link>https://wolkwacht.nl/posts/cloud-security-is-a-system-not-a-stack/</link>
      <pubDate>Wed, 28 Jan 2026 08:50:22 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/cloud-security-is-a-system-not-a-stack/</guid>
      <description>Part 6 of the Cloud Security series</description>
    </item>
    <item>
      <title>Security Fails Quietly When Nobody Owns It</title>
      <link>https://wolkwacht.nl/posts/security-fails-quietly-when-nobody-owns-it/</link>
      <pubDate>Tue, 20 Jan 2026 10:40:04 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/security-fails-quietly-when-nobody-owns-it/</guid>
      <description>Part 5 of the Cloud Security series</description>
    </item>
    <item>
      <title>Architecture Decides the Blast Radius</title>
      <link>https://wolkwacht.nl/posts/architecture-decides-the-blast-radius/</link>
      <pubDate>Tue, 13 Jan 2026 08:42:36 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/architecture-decides-the-blast-radius/</guid>
      <description>Part 4 of the Cloud Security series</description>
    </item>
    <item>
      <title>You Are Logging Everything — And Seeing Almost Nothing</title>
      <link>https://wolkwacht.nl/posts/you-are-logging-everything-and-seeing-almost-nothing/</link>
      <pubDate>Tue, 06 Jan 2026 13:41:29 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/you-are-logging-everything-and-seeing-almost-nothing/</guid>
      <description>Part 3 of the Cloud Security series</description>
    </item>
    <item>
      <title>Identity Is the Perimeter You Forgot to Guard</title>
      <link>https://wolkwacht.nl/posts/identity-is-the-perimeter-you-forgot-to-guard/</link>
      <pubDate>Mon, 29 Dec 2025 10:05:37 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/identity-is-the-perimeter-you-forgot-to-guard/</guid>
      <description>Part 2 of the Cloud Security series</description>
    </item>
    <item>
      <title>The First Security Conversation You Have Too Late: Hardening an Existing Azure Environment</title>
      <link>https://wolkwacht.nl/posts/the-first-security-conversation-you-have-too-late-hardening-an-existing-azure-environment/</link>
      <pubDate>Tue, 23 Dec 2025 15:45:32 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/the-first-security-conversation-you-have-too-late-hardening-an-existing-azure-environment/</guid>
      <description>Most cloud security stories begin in the wrong place.</description>
    </item>
    <item>
      <title>Azure Kubernetes Security Demystified: From Nodes to Pods</title>
      <link>https://wolkwacht.nl/posts/azure-kubernetes-security-demystified-from-nodes-to-pods/</link>
      <pubDate>Mon, 06 Oct 2025 09:21:22 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/azure-kubernetes-security-demystified-from-nodes-to-pods/</guid>
      <description>&lt;h2 id=&#34;azure-kubernetes-security-demystified-from-nodes-topods&#34;&gt;Azure Kubernetes Security Demystified: From Nodes to Pods&lt;/h2&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://cdn-images-1.medium.com/max/800/1*TaWt7QA5dk2vpOJm78Oi9w.png&#34;&gt;&lt;/p&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Kubernetes has become the standard for hosting containerized applications, with Azure Kubernetes Service (AKS) being one of the most popular managed options. AKS simplifies management by handling the control plane, but securing the environment remains the customer’s responsibility. The shared responsibility model requires you to focus on strengthening worker nodes, controlling cluster access, and ensuring that workloads and pods operate with the least privileges.&lt;br&gt;
Security in Kubernetes involves multiple layers. The base layer is the host security of the virtual machines in the node pools. Next is the cluster layer, where identity, networking, and governance must be carefully established and maintained. At the top, securing pods and containers that run your business logic is crucial to prevent privilege escalation or unauthorized communication. This approach, known as “defense in depth,” emphasizes addressing security across various boundaries instead of relying on a single tool or configuration for full protection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zero Trust in the Cloud</title>
      <link>https://wolkwacht.nl/posts/zero-trust-in-the-cloud/</link>
      <pubDate>Fri, 06 Dec 2024 08:29:37 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/zero-trust-in-the-cloud/</guid>
      <description>A Simple Path to Securing Cloud Infrastructure</description>
    </item>
    <item>
      <title>Confidential Computing</title>
      <link>https://wolkwacht.nl/posts/confidentialcompute/</link>
      <pubDate>Mon, 20 Nov 2023 15:43:00 +0100</pubDate>
      <guid>https://wolkwacht.nl/posts/confidentialcompute/</guid>
      <description>The implementation of confidential compute on Azure</description>
    </item>
  </channel>
</rss>
