<?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>OPA Gatekeeper on Yogesh Thanvi</title>
    <link>https://yogeshthanvi.com/tags/opa-gatekeeper/</link>
    <description>Recent content in OPA Gatekeeper on Yogesh Thanvi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yogeshthanvi.com/tags/opa-gatekeeper/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Enforcing Pod Security on AKS with Azure Policy and OPA Gatekeeper</title>
      <link>https://yogeshthanvi.com/posts/enforcing-pod-security-aks-azure-policy/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://yogeshthanvi.com/posts/enforcing-pod-security-aks-azure-policy/</guid>
      <description>Detecting insecure pods on Azure Kubernetes Service is not the same as preventing them. Here is how Azure Policy and OPA Gatekeeper move enforcement to admission time, so a misconfigured workload never reaches the cluster.</description>
    </item>
    <item>
      <title>From Detection to Enforcement: Making CSPM Actually Stop Misconfigurations</title>
      <link>https://yogeshthanvi.com/posts/from-detection-to-enforcement/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://yogeshthanvi.com/posts/from-detection-to-enforcement/</guid>
      <description>Most Cloud Security Posture Management tools detect misconfigurations and stop there. Detection without enforcement leaves the exposure in place. Here is what changes when policy-as-code blocks and remediates at admission time.</description>
    </item>
  </channel>
</rss>
