<?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>Supply-Chain on Dedico</title>
    <link>https://www.dedico.hu/en/tags/supply-chain/</link>
    <description>Recent content in Supply-Chain on Dedico</description>
    <generator>Hugo -- 0.137.1</generator>
    <language>en</language>
    <lastBuildDate>Tue, 31 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.dedico.hu/en/tags/supply-chain/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Axios NPM Compromise Just Hit, Here Is How I Locked Down Our Pipelines in 3 Hours</title>
      <link>https://www.dedico.hu/en/posts/axios-npm-supply-chain-attack-cicd-defense/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.dedico.hu/en/posts/axios-npm-supply-chain-attack-cicd-defense/</guid>
      <description>Axios was compromised on NPM with a RAT dropper. I scrambled to audit our CI/CD pipelines and lock down dependency installation. Here is what I did and what you should do right now.</description>
    </item>
    <item>
      <title>Your GitHub Actions Are a Supply Chain Attack Surface and You Probably Haven&#39;t Noticed</title>
      <link>https://www.dedico.hu/en/posts/github-actions-supply-chain-attacks/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.dedico.hu/en/posts/github-actions-supply-chain-attacks/</guid>
      <description>How SHA pinning alone won&amp;#39;t save your CI/CD pipelines from supply chain attacks, and what I changed after the Trivy incident.</description>
    </item>
    <item>
      <title>I Started Verifying Every Container Image in My Clusters and Here Is What Broke</title>
      <link>https://www.dedico.hu/en/posts/cosign-slsa-image-verification-kubernetes/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://www.dedico.hu/en/posts/cosign-slsa-image-verification-kubernetes/</guid>
      <description>How I set up cosign signature verification and SLSA provenance checks in production Kubernetes, the gotchas I hit, and why it was worth the pain.</description>
    </item>
  </channel>
</rss>
