<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Github-Actions on microsegment.io</title>
    <link>https://microsegment.io/tags/github-actions/</link>
    <description>Recent content in Github-Actions on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/github-actions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your CI/CD Runner Is A Privileged Workload. Contain It.</title>
      <link>https://microsegment.io/post/2026-08-18-cicd-runners-need-containment/</link>
      <pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-08-18-cicd-runners-need-containment/</guid>
      <description>&lt;p&gt;A CI/CD runner is not just a machine that builds software.&lt;/p&gt;&#xA;&lt;p&gt;It is a workload that routinely sits between untrusted input and high-trust systems: source repositories, package registries, artifact stores, cloud APIs, deployment platforms, ticketing systems, and production environments.&lt;/p&gt;&#xA;&lt;p&gt;That makes it privileged infrastructure, even when the workflow looks administrative rather than security-critical.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.wiz.io/blog/red-agent-snowflake-copilot-cicd-bug&#34;&gt;Wiz&amp;rsquo;s disclosure about a GitHub Actions vulnerability in a public Snowflake repository&lt;/a&gt; is a clean example. An unauthenticated user could place crafted content in a GitHub issue title. A workflow inserted that title directly into a shell script. Wiz&amp;rsquo;s autonomous Red Agent used the resulting script injection to execute commands on the runner, extract a Jira credential, and validate read access to internal Snowflake Jira projects.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
