<?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>Activesync — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/activesync/</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/activesync/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></channel></rss>