<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Token-Security on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/token-security/</link><description>Recent content in Token-Security on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 19 Sep 2026 14:03:42 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/token-security/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub adds stage-only scope for npm granular access tokens</title><link>https://curadevops.metacog.co.kr/insights/2026-09-19-stage-only-npm-tokens-for-safer-automation/</link><pubDate>Sat, 19 Sep 2026 14:03:42 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-19-stage-only-npm-tokens-for-safer-automation/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Adopt the new &amp;lsquo;stage only&amp;rsquo; permission when minting npm automation tokens to enforce least-privilege publishing; schedule a rotation of existing CI npm tokens to apply the tighter scope and reduce blast radius from a leaked credential.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>