<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Image-Signing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/image-signing/</link>
    <description>Recent content in Image-Signing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/image-signing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Container Image Signing Policy Enforcement: Kyverno vs Connaisseur vs Portieris vs Ratify Compared</title>
      <link>https://www.pistack.xyz/posts/2026-06-18-self-hosted-container-image-signing-policy-enforcement-kyverno-connaisseur-portieris-ratify/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-18-self-hosted-container-image-signing-policy-enforcement-kyverno-connaisseur-portieris-ratify/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Software supply chain attacks targeting container images have become one of the most critical security threats in cloud-native environments. When an attacker compromises a container image in your registry, every pod running that image inherits the compromise. The solution is cryptographic image signing — but signing alone is not enough. You need enforcement: a mechanism that blocks unsigned or tampered images from ever running in your cluster.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
