<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on CuraSec</title><link>https://curasec.metacog.co.kr/tags/aws/</link><description>Recent content in Aws on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 11:32:44 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>9,300+ Leaked AWS Keys Still Active, Grant Full Account Control</title><link>https://curasec.metacog.co.kr/insights/2026-08-22-hundreds-of-leaked-aws-keys-give-full-control-over-corporate/</link><pubDate>Sat, 22 Aug 2026 11:32:44 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-22-hundreds-of-leaked-aws-keys-give-full-control-over-corporate/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Still-valid exposed AWS keys require no exploitation sophistication — the credential is the exploit. Audit all active IAM access keys in your AWS accounts, cross-reference against the leaked dataset, rotate any keys created or last-used anomalously, and enforce least-privilege policies with automatic key rotation going forward.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Active leaked credentials mean unauthorized access may already be occurring. Hunt CloudTrail logs since August 2022 for API calls from unexpected source IPs, new IAM user/role creation, or unusual resource provisioning that could indicate keys were already abused by third parties.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Hundreds of corporate AWS keys with full-account-control scope being publicly available for up to four years is a material risk requiring same-week action — confirm whether your organization&amp;rsquo;s keys appear in the exposed set and direct engineering to complete a credential audit and rotation before end of week.&lt;/li>
&lt;/ul></description></item></channel></rss>