<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Account-Security on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/account-security/</link><description>Recent content in Account-Security on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Sep 2026 14:43:59 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/account-security/index.xml" rel="self" type="application/rss+xml"/><item><title>npm extends 72-hour security hold to all accounts after recovery-code sign-in</title><link>https://curadevops.metacog.co.kr/insights/2026-09-11-npm-extends-recovery-code-security-holds-to-all-accounts/</link><pubDate>Fri, 11 Sep 2026 14:43:59 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-09-11-npm-extends-recovery-code-security-holds-to-all-accounts/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>CI/CD — Learn:&lt;/strong> npm now applies a 72-hour security hold to any account following a recovery-code sign-in, broadening a protection previously limited to high-impact accounts; no pipeline changes are needed since CI automation should use tokens, not recovery codes, but this informs npm supply-chain security posture.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>