<?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>Illicit-Consent - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/illicit-consent/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 03 Jan 2024 18:23:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/illicit-consent/feed.xml" rel="self" type="application/rss+xml"/><item><title>Entra ID Illicit Consent Grant via Registered Application</title><link>https://feed.craftedsignal.io/briefs/2024-01-03-entra-id-illicit-consent/</link><pubDate>Wed, 03 Jan 2024 18:23:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-03-entra-id-illicit-consent/</guid><description>Attackers register malicious applications within Entra ID and deceive users into granting extensive permissions through OAuth consent, enabling unauthorized access to sensitive data like emails and files.</description><content:encoded><![CDATA[<p>Attackers are increasingly leveraging illicit consent grants within Microsoft Entra ID to gain unauthorized access to sensitive data. This involves registering a malicious application within an organization's Entra ID environment and tricking users into granting it excessive permissions via OAuth consent. The attack commonly uses spearphishing to distribute links that lead users to grant permissions to seemingly legitimate applications. Once consent is granted, the attacker-controlled application can access resources like mail, profiles, and files on behalf of the compromised user. Detection focuses on identifying unusual consent activity within Azure audit logs, particularly new application consent grants and instances where Microsoft flags an application as risky. This activity is flagged using ES|QL aggregation logic over a 7-day window looking for new or risky user-application consent pairs.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker registers a malicious application within Microsoft Entra ID.</li>
<li>The attacker crafts a spearphishing email containing a malicious link.</li>
<li>The victim receives the spearphishing email and clicks the malicious link.</li>
<li>The link redirects the victim to a consent page for the attacker's application.</li>
<li>The consent page requests permissions to access resources such as mail, profiles, and files.</li>
<li>The victim, believing the application is legitimate, grants consent.</li>
<li>The attacker's application receives an OAuth access token.</li>
<li>The attacker's application uses the access token to access resources on behalf of the compromised user, enabling data exfiltration or other malicious activities.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful illicit consent grant attack can lead to unauthorized access to sensitive data, including emails, files, and user profiles. The impact includes data breaches, financial loss, and reputational damage. While the exact number of victims is unknown, this technique targets any organization using Microsoft Entra ID and relying on user consent for application access.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>Detect Entra ID Illicit Consent Grant</code> to your SIEM and tune for your environment to detect suspicious consent grants.</li>
<li>Review Azure audit logs for consent events where the <code>azure.auditlogs.properties.target_resources.0.modified_properties.5.new_value</code> field contains &quot;<em>Risky application detected</em>&quot;.</li>
<li>Enable the Admin Consent Workflow in Azure AD to prevent unsanctioned user approvals.</li>
<li>Revoke the OAuth grant for any identified malicious application using Graph API or PowerShell.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>azure</category><category>entra-id</category><category>oauth</category><category>illicit-consent</category></item><item><title>Entra ID Sharepoint or OneDrive Accessed by Unusual Client</title><link>https://feed.craftedsignal.io/briefs/2024-01-entra-id-sharepoint-unusual-access/</link><pubDate>Wed, 03 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-entra-id-sharepoint-unusual-access/</guid><description>An application accessing SharePoint Online or OneDrive for Business for the first time in a tenant could indicate OAuth phishing, illicit consent grants, or compromised third-party apps accessing file storage.</description><content:encoded><![CDATA[<p>This detection identifies when an application accesses SharePoint Online or OneDrive for Business for the first time within a tenant. This is a critical signal for detecting successful OAuth phishing campaigns, where users are tricked into granting consent to malicious applications. Once consent is granted, the malicious app can persistently access file storage without further user interaction. This also catches illicit consent grants, compromised third-party applications, or custom malicious apps registered by adversaries. The rule uses data from Entra ID sign-in logs to identify new application IDs accessing SharePoint or OneDrive resources. The rule looks back 9 months to establish a baseline of known applications.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker sends a phishing email with a link to a malicious OAuth application.</li>
<li>The victim clicks the link and is redirected to a legitimate-looking consent page.</li>
<li>The victim grants consent to the malicious application, unknowingly providing access to their data.</li>
<li>The malicious application authenticates to Entra ID using the granted consent.</li>
<li>The application accesses SharePoint Online or OneDrive for Business using the victim's permissions.</li>
<li>The application exfiltrates sensitive data from SharePoint or OneDrive.</li>
<li>The attacker uses the exfiltrated data for their objectives, such as financial gain or espionage.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>A successful OAuth phishing campaign or illicit consent grant can lead to significant data breaches. An attacker gaining access to SharePoint Online or OneDrive for Business can steal sensitive documents, intellectual property, and other confidential information. This can result in financial losses, reputational damage, and legal liabilities. There is no specific number of victims or sectors targeted detailed in the provided source material.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule &quot;Entra ID Sharepoint or OneDrive Accessed by Unusual Client&quot; to your SIEM and tune for your environment to detect initial access of unusual applications.</li>
<li>Review <code>azure.signinlogs.properties.app_id</code> and <code>azure.signinlogs.properties.app_display_name</code> to identify the application and cross-reference with known legitimate applications, as described in the rule's Triage and Analysis section.</li>
<li>Monitor <code>azure.auditlogs</code> for recent <code>Consent to application</code> events matching suspicious app IDs to identify how consent was granted, as documented in the rule's analysis section.</li>
<li>Implement Conditional Access policies to require admin consent for high-risk permissions and block unverified publishers, as recommended in the Response and Remediation section.</li>
<li>Ensure that Microsoft Entra ID Sign-In Logs are being collected and streamed into the Elastic Stack via the Azure integration, as required by the rule setup.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>azure</category><category>sharepoint</category><category>onedrive</category><category>oauth</category><category>phishing</category><category>illicit-consent</category></item></channel></rss>