<?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>Exchange — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/exchange/</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>Wed, 03 Jan 2024 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/exchange/feed.xml" rel="self" type="application/rss+xml"/><item><title>New ActiveSync Allowed Device Added via PowerShell</title><link>https://feed.craftedsignal.io/briefs/2024-01-activesync-device-added/</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-activesync-device-added/</guid><description>The rule detects the use of the Exchange PowerShell cmdlet, Set-CASMailbox, to add a new ActiveSync allowed device, potentially allowing attackers to gain persistent access to sensitive email data by adding unauthorized devices.</description><content:encoded><![CDATA[<p>This detection identifies the use of the Exchange PowerShell cmdlet, <code>Set-CASMailbox</code>, to add a new ActiveSync allowed device. Attackers may target user email to collect sensitive information by adding unauthorized devices to a user&rsquo;s allowed ActiveSync devices. The rule focuses on detecting suspicious PowerShell activity by monitoring for specific command patterns indicative of unauthorized device additions. This activity can lead to persistent access to sensitive email data, bypassing normal authentication controls. The original Elastic detection rule was created on 2020/12/15 and updated on 2026/05/04. This matters for defenders because it highlights a persistence mechanism that can be difficult to detect through traditional means.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a privileged account with Exchange management permissions.</li>
<li>The attacker uses PowerShell to execute the <code>Set-CASMailbox</code> cmdlet.</li>
<li>The attacker modifies the <code>ActiveSyncAllowedDeviceIDs</code> attribute for a target user&rsquo;s mailbox.</li>
<li>The attacker adds a rogue device ID to the list of allowed devices.</li>
<li>The attacker configures a mobile device with the rogue device ID to synchronize with the target mailbox.</li>
<li>The attacker gains persistent access to the target user&rsquo;s email, calendar, and contacts.</li>
<li>The attacker exfiltrates sensitive data from the mailbox.</li>
<li>The attacker maintains persistence even after password changes by continuing to synchronize via the added device.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation could lead to unauthorized access to sensitive email data, including confidential communications, financial information, and personal data. This can result in data breaches, compliance violations, and reputational damage. The scope of the impact depends on the privileges of the compromised account and the sensitivity of the data contained in the targeted mailboxes.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>ActiveSyncAllowedDeviceID Added via PowerShell</code> to your SIEM and tune for your environment to detect suspicious activity.</li>
<li>Enable Sysmon process-creation logging to capture PowerShell commands for the rule above.</li>
<li>Review Exchange audit logs for instances of <code>Set-CASMailbox</code> being used to modify <code>ActiveSyncAllowedDeviceIDs</code>.</li>
<li>Implement multi-factor authentication (MFA) for all accounts, especially those with Exchange management privileges.</li>
<li>Regularly audit ActiveSync device configurations to identify unauthorized devices.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>exchange</category><category>activesync</category><category>powershell</category><category>persistence</category></item><item><title>Exchange Mailbox Export via PowerShell</title><link>https://feed.craftedsignal.io/briefs/2024-01-exchange-mailbox-export/</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-exchange-mailbox-export/</guid><description>Adversaries may use the New-MailboxExportRequest PowerShell cmdlet to export mailboxes in Exchange, potentially leading to sensitive information theft.</description><content:encoded><![CDATA[<p>Attackers may target user email to collect sensitive information. The <code>New-MailBoxExportRequest</code> cmdlet is used to export the contents of a primary mailbox or archive to a .pst file. Note that this is done on a per-mailbox basis and this cmdlet is available only in on-premises Exchange. Attackers can abuse this functionality in preparation for exfiltrating contents, which is likely to contain sensitive and strategic data. This activity is typically performed using PowerShell or similar scripting tools and can be difficult to detect without specific monitoring in place. The activity may be part of a larger attack campaign targeting sensitive information.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains initial access to a compromised system with sufficient privileges to access Exchange PowerShell.</li>
<li>The attacker authenticates to the Exchange server using PowerShell.</li>
<li>The attacker uses the <code>New-MailboxExportRequest</code> cmdlet to initiate the export of a target mailbox to a .pst file. The command may include parameters to filter specific content.</li>
<li>The Exchange server processes the export request, creating a .pst file containing the mailbox data.</li>
<li>The attacker retrieves the exported .pst file from the designated file path.</li>
<li>The attacker may compress and archive the .pst file to reduce its size for exfiltration.</li>
<li>The attacker exfiltrates the .pst file to an external location controlled by the attacker.</li>
<li>The attacker analyzes the .pst file to extract sensitive information such as credentials, financial data, or intellectual property.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows the attacker to gain access to sensitive information contained within the exported mailboxes. This could lead to financial loss, reputational damage, or compromise of intellectual property. Depending on the scope of the export requests, multiple mailboxes may be compromised, impacting a large number of users. The impact is significant because email often contains highly sensitive business communications and data.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Enable Sysmon process creation logging to monitor PowerShell execution with command-line arguments (Data Source: Sysmon).</li>
<li>Implement the provided Sigma rule to detect the use of <code>New-MailboxExportRequest</code> cmdlet in PowerShell commands.</li>
<li>Review the privileges of users with the &ldquo;Mailbox Import Export&rdquo; privilege to ensure that the least privilege principle is being followed.</li>
<li>Monitor Windows Security Event Logs for PowerShell activity related to mailbox export requests (Data Source: Windows Security Event Logs).</li>
<li>Investigate any alerts generated by the Sigma rules to identify potential malicious activity.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>collection</category><category>execution</category><category>powershell</category><category>exchange</category><category>mailbox</category></item></channel></rss>