Tag Archive: Attack Disruption

DisruptionAndResponseEvents Table Preview

What can be more exciting than new Advance Hunting tables. Since it’s Preview it could change

The DisruptionAndResponseEvents table in Microsoft Defender XDR is your visibility layer into automatic attack disruption – Microsoft’s built-in capability to actively stop attacks in progress.

It records what Defender did, not just what the attacker did.

Telemetry

Most telemetry tells you what happened while this table tells you how an attack was disrupted in real time and it helps you understand attack scope, attack impact and Defender’s automated response decisions.

What kind of events you’ll see?

The table focuses on defensive actions

  • Containment actions
  • Examples:
  • User logon blocked
  • SMB access blocked
  • RPC access denied
  • RDP sessions disconnected

Hardening & protection policies

  • Safe Boot blocked
  • Safe Boot Guard applied
  • Group Policy hardening applied
  • SYSVOL access blocked

These indicate environment hardening triggered automatically

Session / activity termination

  • SMB session killed
  • Remote session logged off

These show active attacker sessions being cut off

Important nuance (most people miss this) the table does NOT log the action itself (like “Contain User”) instead, it logs the resulting effects, such as:

  • Blocked logons
  • Denied access
  • Policy enforcement

Data sources & dependencies

Populated from multiple Defender services (Endpoint, Identity, etc.) which requires proper onboarding – otherwise you’ll see little or no data

No onboarding = no visibility.

This table shines when you want to answer:

  • What did Defender automatically stop?
  • Why did this attack fail?
  • Which users/devices were actively contained?
  • What hardening actions were triggered during an incident?

If you want to have the table extended with the description you can use the following User-defined function (which runs in query time in Defender)

For further information about Attack Disruption, please visit: Automatic attack disruption in Microsoft Defender – Microsoft Defender XDR | Microsoft Learn

#Happy Hunting

Another reason to make sure Defender is configured correctly

Attack Disruption

  • It uses Defender XDR’s ability to correlate signals from many different sources into a single, high-confidence incident through insights from endpoints, identities, email and collaboration tools, and SaaS apps.
  • It identifies assets controlled by the attacker and used to spread the attack.
  • It automatically takes response actions across relevant Microsoft Defender products to contain the attack in real-time by containing and disabling affected assets.

Previous blog post on Attack Disruption Automatic Attack Disruption Explained – SEC-LABS R&D

With all the capabilities provided within Attack Disruption, it’s important that Defender XDR is configured correctly. For instance, if you have configured a gMSA account for the MDI actions, and it does not work properly, it will affect disruption negatively.

MDE Prereqs

  • Minimum Sense version for contain user:v10.8470
  • Auto IR:  Full – remediate threats automatically (recommended for full coverage, no automated response turns off automatic disruption for device group)
  • Endpoint discovery set to Standard (not basic)

In MDE the most common configuration improvements seen are:

  • Sample submission is not configured to send files automatically
  • Cloud block out level is not set to high
  • Cloud block timeout period is not set to 50s

more on MDE in this previous post 3 common Defender for Endpoint configuration errors

MDI Prereqs

  • Validate DC auditing
  • Validate permissions for Action Account or use LocalSystem
  • Validate no other systems interfere with attack disruption, such as systems for auto activating users

MDO Prereqs

  • Mailboxes are required to be hosted in Exchange Online.
  • The following mailbox events need to be audited by minimum:
    • MailItemsAccessed
    • UpdateInboxRules
    • MoveToDeletedItems
    • SoftDelete
    • HardDelete
    • Safelinks policy needs to be present.

MDA Prereqs

  • Microsoft Defender for Cloud Apps must be connected to Microsoft Office 365 through the connector
  • App Governance must be turned on

Happy Hunting!