Blog Post

Microsoft Defender XDR Blog
2 MIN READ

Automatically disrupt adversary-in-the-middle (AiTM) attacks with XDR

eyalh's avatar
eyalh
Icon for Microsoft rankMicrosoft
May 17, 2023

UPDATE: As of July 4th, 2023, the expansion of the automatic attack disruption capability in Microsoft 365 Defender to include adversary-in-the-middle (AiTM) attacks is now generally available (GA).

 

Microsoft has been on a journey to harness the power of artificial intelligence to help security teams scale more effectively. Microsoft 365 Defender correlates millions of signals across endpoints, identities, emails, collaboration tools, and SaaS apps to identify active attacks and compromised assets in an organization’s environment. Last year, we introduced automatic attack disruption, which uses these correlated insights and powerful AI models to stop some of the most sophisticated attack techniques while in progress to limit lateral movement and damage.  

 

Today, we are excited to announce the expansion of automatic attack disruption to include adversary-in-the-middle attacks (AiTM) attacks, in an addition to the previously announced public preview for business email compromise (BEC) and human-operated ransomware attacks.

 

AiTM attacks are a widespread and can pose a major risk to organizations. We are observing a rising trend in the availability of adversary-in-the-middle (AiTM) phishing kits for purchase or rent.

 

During AiTM attacks (Figure 1), a phished user interacts with an impersonated site created by the attacker. This allows the attacker to intercept credentials and session cookies and bypass multifactor authentication (MFA), which can then be used to initiate other attacks such as BEC and credential harvesting. 

 

Automatic attack disruption does not require any pre-configuration by the SOC team. Instead, it’s built in as a capability in Microsoft’s XDR.

Figure 1. Example of an AiTM phishing campaign that led to a BEC attack

 

How Microsoft’s XDR automatically contains AiTM attacks

Similarly to attack disruption of BEC and human-operated ransomware attacks, the goal is to contain the attack as early as possible while it is active in an organization’s environment and reduce its potential damage to the organization. AiTM attack disruption works as follows:

 

  1. High-confidence identification of an AiTM attack based on multiple, correlated Microsoft 365 Defender signals.
  2. Automatic response is triggered that disables the compromised user account in Active Directory and Azure Active Directory.
  3. The stolen session cookie will be automatically revoked, preventing the attacker from using it for additional malicious activity.

Figure 2. An example of a contained AiTM incident, with attack disruption tag

 

To ensure SOC teams have full control, they can configure automatic attack disruption and easily revert any action from the Microsoft 365 Defender portal. See our documentation for more details.

 

Get started

  1. Make sure your organization fulfills the Microsoft 365 Defender pre-requisites
  2. Connect Microsoft Defender for Cloud Apps to Microsoft 365.
  3. Deploy Defender for Endpoint. A free trial is available here.
  4. Deploy Microsoft Defender for Identity. You can start a free trial here.

Learn more

Updated Oct 29, 2024
Version 5.0

8 Comments

  • Kostas1978's avatar
    Kostas1978
    Copper Contributor

    yycc1  the first url that started the incident was fourthmanservice.com which indeed is marked as malicious from many engines.

    Then another site was added.  http://www.e-tsekouras.gr which has an issue with http link which misses a certificate and doesn’t auto redirect in https which is working.

    another website added in the incident was koufomata.gr which I haven’t investigated yet but it’s a legit site. 
    then a fourth site was added http://www.athanassopoulos.gr. All these don’t connect with each other. All were accessed from different users. 

    More sites are added daily

  • yycc1's avatar
    yycc1
    Copper Contributor

    Kostas1978  you have any http site you can share? I have not seen a single incident triggered that way and we have enough sporadic http only sites that users access.

  • Kostas1978's avatar
    Kostas1978
    Copper Contributor

    In our case we have events from users accessing sites that were either malicious or for example had a missing certificate in HTTP. If we dont close the incident for 2-3 days then more events add up that are from different users and for completely different websites. 

     

    At this point this rule seems like it bring a lot of false positive. Is it the same for you?

  • ZeeHulk66's avatar
    ZeeHulk66
    Copper Contributor

    Hello, is there any way to simulate this attack to test ? 

  • Hi yycc1, thank you for the questions. Please see our direct response to your case, which was reported via the Microsoft 365 Defender portal.

  • yycc1's avatar
    yycc1
    Copper Contributor

    How can we validate the 'stolen' cookie has been revoked?  

     

    Account disablement, this does not seem to be happening.  Can it happen in a hybrid situation???

     

    Also, it seems like your products do not talk to each other.  Azure risky users lowered the user from a HIGH to a medium after a AITM event.

     

  • DanChemistruck's avatar
    DanChemistruck
    Copper Contributor

    viktorhammel you listed the location for the endpoint portion of Automatic Disruption. For Identities, there is an exclusion list you can manage:

    https://security.microsoft.com/settings/identities?tabid=automaticExclusions

     

    I believe you just need to have Identity Protection enabled for this feature to work:
    https://portal.azure.com/?feature.msticonnector=true#view/Microsoft_AAD_IAM/IdentityProtectionMenuBlade/~/Overview

  • viktorhammel's avatar
    viktorhammel
    Copper Contributor

    Hi,

    I wanted to check if the automatic response is enabled in our tenant. According to documentation, Automatic attack disruption in Microsoft 365 Defender is configured in Settings > Endpoints > Device groups under Permissions.

    But the Remidiation levels are all based on folders. How does this apply to identities? Thanks for a short clarification.