<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Credential-Stuffing — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/credential-stuffing/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 02 Jan 2024 15:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/credential-stuffing/feed.xml" rel="self" type="application/rss+xml"/><item><title>Azure AD Failed Authentication Increase</title><link>https://feed.craftedsignal.io/briefs/2024-01-02-azure-ad-failed-auth-increase/</link><pubDate>Tue, 02 Jan 2024 15:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-02-azure-ad-failed-auth-increase/</guid><description>Detects a significant increase (10% or greater) in failed Azure AD sign-in attempts, potentially indicating brute-force attacks, credential stuffing, or other unauthorized access attempts.</description><content:encoded><![CDATA[<p>This brief focuses on detecting abnormal increases in failed authentication attempts within Azure Active Directory (Azure AD). An adversary attempting to gain unauthorized access to user accounts or systems often performs brute-force or credential stuffing attacks. These attacks result in a higher-than-normal number of failed sign-in attempts. Monitoring and detecting such increases can provide early warning of potential breaches or compromised accounts. Defenders should investigate any significant spikes in failed authentications as they might indicate malicious activity targeting user accounts or application access. The detection is based on analysis of Azure AD sign-in logs to identify when the number of failed sign-ins increases by 10% or greater, warranting further investigation.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li><strong>Initial Access:</strong> The attacker attempts to gain initial access through various methods, such as phishing, compromised credentials, or exploiting vulnerabilities.</li>
<li><strong>Credential Stuffing/Brute-Force:</strong> The attacker uses lists of known usernames and passwords (credential stuffing) or systematically tries different password combinations (brute-force) against Azure AD accounts.</li>
<li><strong>Authentication Attempts:</strong> Each failed authentication attempt is logged within Azure AD sign-in logs, recording details such as username, IP address, and failure reason.</li>
<li><strong>Threshold Exceeded:</strong> The number of failed sign-in attempts reaches a threshold, triggering the detection rule based on a 10% or greater increase.</li>
<li><strong>Account Lockout (Potential):</strong> Multiple failed authentication attempts may lead to account lockouts, disrupting legitimate user access.</li>
<li><strong>Successful Authentication (Potential):</strong> If the attacker guesses the correct credentials, they gain unauthorized access to the target account.</li>
<li><strong>Privilege Escalation/Lateral Movement:</strong> After gaining access, the attacker attempts to escalate privileges or move laterally within the network to access sensitive data or systems.</li>
<li><strong>Data Exfiltration/Impact:</strong> The attacker exfiltrates sensitive data or causes disruption to services depending on their objectives.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful brute-force or credential stuffing attack can lead to unauthorized access to user accounts, data breaches, and service disruptions. Depending on the compromised account&rsquo;s privileges, the attacker may gain access to sensitive information, escalate privileges, or move laterally within the organization&rsquo;s network. The impact could range from minor data leaks to significant financial losses and reputational damage. Early detection and mitigation are crucial to minimize the impact of such attacks.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to your SIEM to detect increases in failed Azure AD sign-in attempts and tune the threshold (10%) based on your environment (<code>Count: &quot;&lt;10%&quot;</code>).</li>
<li>Investigate alerts generated by the Sigma rule to determine the source and scope of the increased failed authentications.</li>
<li>Enforce multi-factor authentication (MFA) for all users to mitigate the risk of credential-based attacks.</li>
<li>Implement account lockout policies to prevent attackers from repeatedly attempting to guess passwords.</li>
<li>Monitor sign-in logs for unusual patterns, such as sign-ins from unfamiliar locations or devices, to identify potential compromised accounts.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>azuread</category><category>brute-force</category><category>credential-stuffing</category><category>authentication</category></item></channel></rss>