<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service-Accounts on CuraSec</title><link>https://curasec.metacog.co.kr/tags/service-accounts/</link><description>Recent content in Service-Accounts on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 17:09:30 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/service-accounts/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP2Shell used to argue blast radius beats CVSS as patching metric</title><link>https://curasec.metacog.co.kr/insights/2026-10-28-even-after-php2shell-blast-radius-matters-more-than-a-cvss-s/</link><pubDate>Wed, 28 Oct 2026 17:09:30 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-28-even-after-php2shell-blast-radius-matters-more-than-a-cvss-s/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The blast-radius framing — scope service accounts, API keys, and AI agent credentials to minimum necessary access so a successful exploit can&amp;rsquo;t pivot far — is a useful mental model, though not a new principle. No specific patch or configuration action is indicated by this item.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Vendor thought-leadership piece using PHP2Shell as a hook to argue that access-scoping for service accounts and AI agents limits breach impact beyond what patching speed alone can achieve — useful framing for a future risk posture discussion, but no new evidence or compliance deadline is introduced.&lt;/li>
&lt;/ul></description></item></channel></rss>