<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Credentials on Brian Faust</title><link>https://wimdy.works/tags/credentials/</link><description>Recent content in Credentials on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://wimdy.works/tags/credentials/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Short-Lived Token Can Still Have a Large Blast Radius</title><link>https://wimdy.works/thoughts/a-short-lived-token-can-still-have-a-large-blast-radius/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate><guid>https://wimdy.works/thoughts/a-short-lived-token-can-still-have-a-large-blast-radius/</guid><description>&lt;p&gt;The release job has no stored cloud key. It asks GitHub for an identity token,
exchanges that token for a five-minute production credential, deploys, and lets
the credential expire.&lt;/p&gt;
&lt;p&gt;A compromised dependency runs in the same job. It can use the same identity
request interface and deploy while the credential is live. Five minutes sounds
short on a policy diagram. For hostile code already executing inside the job,
it is plenty.&lt;/p&gt;</description></item></channel></rss>