<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Iam on CuraSec</title><link>https://curasec.metacog.co.kr/tags/aws-iam/</link><description>Recent content in Aws-Iam on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 21 Sep 2026 17:01:38 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/aws-iam/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS IAM credential exposure response: GitHub scanning &amp; CloudTrail tactics</title><link>https://curasec.metacog.co.kr/insights/2026-09-21-from-exposure-to-lockdown-how-aws-neutralizes-compromised-ia/</link><pubDate>Mon, 21 Sep 2026 17:01:38 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-21-from-exposure-to-lockdown-how-aws-neutralizes-compromised-ia/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Covers AWS&amp;rsquo;s automated response to leaked IAM credentials via managed policy quarantine and CloudTrail monitoring — useful design context for incident runbooks and understanding AWS-side controls, but no patch or immediate action required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Details on CloudTrail signals and GitHub secret scanning patterns for detecting exposed IAM credentials are worth incorporating into hunting playbooks, though no active exploitation or IOCs are present here.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>