<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Password-Spray on CuraSec</title><link>https://curasec.metacog.co.kr/tags/password-spray/</link><description>Recent content in Password-Spray on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 21 Aug 2026 11:38:25 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/password-spray/index.xml" rel="self" type="application/rss+xml"/><item><title>PowerShell guide for auditing Entra ID login logs and detecting password sprays</title><link>https://curasec.metacog.co.kr/insights/2026-08-21-even-moar-powershell-looking-at-entra-logins-the-good-the-ba/</link><pubDate>Fri, 21 Aug 2026 11:38:25 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-21-even-moar-powershell-looking-at-entra-logins-the-good-the-ba/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Practical reminder that cloud identity login logs (Entra ID sign-in logs) deserve the same daily scrutiny as on-prem logs; useful if you haven&amp;rsquo;t wired these into a monitoring workflow yet, but no patch or config change required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Adopt or adapt the PowerShell queries shown to pull Entra successful/failed login data for routine password-spray hunting; worth scheduling as a log-source coverage improvement if Entra sign-in logs aren&amp;rsquo;t already feeding your SIEM.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>