<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure on CuraSec</title><link>https://curasec.metacog.co.kr/tags/azure/</link><description>Recent content in Azure on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 18 Aug 2026 11:37:25 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>Hacker claims 3.6M Azure account records sold from Fortune 500 firms</title><link>https://curasec.metacog.co.kr/insights/2026-08-18-hacker-claims-3-6-million-azure-account-records-stolen-from/</link><pubDate>Tue, 18 Aug 2026 11:37:25 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-18-hacker-claims-3-6-million-azure-account-records-stolen-from/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> The alleged vector is compromised credentials, not a platform vulnerability — audit Azure Entra ID sign-in logs for anomalous authentication, verify MFA is enforced on all accounts, and review conditional access policies for gaps.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> No IOCs or confirmed TTPs are available yet, but if your estate includes Azure, queue a hunt for unusual authentication patterns in Entra ID logs (off-hours logins, new service principals, bulk data exports) and monitor breach-data feeds for your org&amp;rsquo;s domains.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> If Azure is in your estate, contact your Microsoft account team this week to ask whether your tenant appears in this claimed dataset, and prepare a brief for leadership in case the story gains traction or your company is named.&lt;/li>
&lt;/ul></description></item></channel></rss>