<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Akamai on CuraSec</title><link>https://curasec.metacog.co.kr/tags/akamai/</link><description>Recent content in Akamai on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 31 Oct 2026 16:03:46 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/akamai/index.xml" rel="self" type="application/rss+xml"/><item><title>Linode Security Incident Disclosed via Status Page</title><link>https://curasec.metacog.co.kr/insights/2026-10-31-linode-security-incident/</link><pubDate>Sat, 31 Oct 2026 16:03:46 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-31-linode-security-incident/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If workloads run on Linode (now Akamai Cloud), review the incident disclosure at the status page to determine whether credentials, SSH keys, or customer data were exposed and rotate accordingly.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> Confirm whether Linode/Akamai Cloud appears in the vendor inventory; if so, request a formal incident scope statement and assess whether any customer or regulated data was co-hosted there.&lt;/li>
&lt;/ul></description></item></channel></rss>