Skip to content

Latest commit

 

History

History
258 lines (199 loc) · 13.4 KB

playbook-responding-ransomware-m365-defender.md

File metadata and controls

258 lines (199 loc) · 13.4 KB
Raw
title description search.appverid author ms.author manager audience ms.topic ms.date ms.service ms.subservice ms.collection f1.keywords
Responding to ransomware attacks
This article provides a generalized playbook for responding to ransomware attacks.
MET150
nic-name
noriordan
dolmont
ITPro
article
10/16/2024
microsoft-365-security
m365d
msftsolution-secops
tier1
NOCSH

Responding to ransomware attacks

[!INCLUDE Microsoft Defender XDR rebranding]

When you suspect you were or are currently under a ransomware attack, establish secure communications with your incident response team immediately. They can perform the following response phases to disrupt the attack and mitigate the damage:

  • Investigation and containment
  • Eradication and recovery

This article provides a generalized playbook for responding to ransomware attacks. Consider adapting the described steps and tasks in this article to your own security operations playbook. NOTE: For information about preventing ransomware attacks, see Quickly deploy ransomware preventions.

Containment

Containment and investigation should occur as simultaneously as possible; however, you should focus on quickly achieving containment, so you have more time to investigate. These steps help you determine the scope of the attack and to isolate it to only affected entities, such as user accounts and devices.

Step 1: Assess the scope of the incident

Run through this list of questions and tasks to discover the extent of the attack. Microsoft Defender XDR can provide a consolidated view of all impacted or at-risk assets to aid in your incident response assessment. See Incident response with Microsoft Defender XDR. You can use the alerts and the evidence list in the incident to determine:

  • Which user accounts might be compromised?
    • Which accounts were used to deliver the payload?
  • Which onboarded and discovered devices are affected and how?
    • Originating devices
    • Impacted devices
    • Suspicious devices
  • Identify any network communication that is associated with the incident.
  • Which applications are affected?
  • What payloads were spread?
  • How is the attacker communicating with the compromised devices? (Network protection must be enabled):
    • Go to the indicators page to add a block for the IP and URL (if you have that information).
  • What was the payload delivery medium?

Step 2: Preserve existing systems

Run through this list of tasks and questions to protect existing systems from attack:

  • If you have online backups, consider disconnecting the backup system from the network until you're confident that the attack is contained, see Backup and restore plan to protect against ransomware | Microsoft Docs.
  • If you're experiencing or expect an imminent and active ransomware deployment:
    • Suspend privileged and local accounts that you suspect are part of the attack. You can do this from the Users tab in the properties of the incident in the Microsoft Defender portal.
    • Stop all remote logon sessions.
    • Reset the compromised user account passwords and require the users of compromised user accounts to sign in again.
    • Do the same for user accounts that might be compromised.
    • If shared local accounts are compromised, have your IT admin help you to enforce a password change across all exposed devices. Example Kusto query:
DeviceLogonEvents | where DeviceName  contains (AccountDomain) | take 10
  • For the devices that aren't yet isolated and aren't part of the critical infrastructure:
    • Isolate compromised devices from the network but don't shut them off.
    • If you identify the originating or spreader devices, isolate those first.
  • Preserve compromised systems for analysis.

Step 3: Prevent the spread

Use this list to keep the attack from spreading to additional entities.

DeviceLogonEvents
| where IsLocalAdmin == true and AccountDomain == DeviceName
| extend IsLocalLogon = tobool(todynamic(AdditionalFields).IsLocalLogon)
| where IsLocalLogon==false
  • Kusto query for non-RDP logons (more realistic for most networks):
DeviceLogonEvents
| where IsLocalAdmin == true and AccountDomain == DeviceName and LogonType != 'RemoteInteractive'
| extend IsLocalLogon = tobool(todynamic(AdditionalFields).IsLocalLogon)
| where IsLocalLogon==false

Investigation

Use this section to investigate the attack and plan your response.

Assess your current situation

  • What initially made you aware of the ransomware attack?
    • If IT staff identified the initial threat—such as noticing backups being deleted, antivirus alerts, endpoint detection and response (EDR) alerts, or suspicious system changes—it's often possible to take quick decisive measures to thwart the attack, typically by the containment actions described in this article.
  • What date and time did you first learn of the incident?
    • What system and security updates weren't installed on devices on that date? This is important to understand what vulnerabilities might have been leveraged so they can be addressed on other devices.
    • What user accounts were used on that date?
    • What new user accounts were created since that date?
    • What programs were added to automatically start around the time that the incident occurred?
  • Is there any indication that the attacker is currently accessing systems?
    • Are there any suspected compromised systems that are experiencing unusual activity?
    • Are there any suspected compromised accounts that appear to be actively used by the adversary?
    • Is there any evidence of active command-and-control (C2) servers in EDR, firewall, VPN, web proxy, and other logs?

Identify the ransomware process

  • Using advanced hunting, search for the identified process in the process creation events on other devices.

Look for exposed credentials in the infected devices

  • For user accounts whose credentials were potentially compromised, reset the account passwords, and require the users to sign in again.
  • The following IOAs might indicate lateral movement:
Click to expand
  • SuspiciousExploratoryCommands
  • MLFileBasedAlert
  • IfeoDebuggerPersistence
  • SuspiciousRemoteFileDropAndExecution
  • ExploratoryWindowsCommands
  • IoaStickyKeys
  • Mimikatz Defender Amplifier
  • Network scanning tool used by PARINACOTA
  • DefenderServerAlertMSSQLServer
  • SuspiciousLowReputationFileDrop
  • SuspiciousServiceExecution
  • AdminUserAddition
  • MimikatzArtifactsDetector
  • Scuba-WdigestEnabledToAccessCredentials
  • DefenderMalware
  • MLSuspCmdBehavior
  • MLSuspiciousRemoteInvocation
  • SuspiciousRemoteComponentInvocation
  • SuspiciousWmiProcessCreation
  • MLCmdBasedWithRemoting
  • Process Accesses Lsass
  • Suspicious Rundll32 Process Execution
  • BitsAdmin
  • DefenderCobaltStrikeDetection
  • DefenderHacktool
  • IoaSuspPSCommandline
  • Metasploit
  • MLSuspToolBehavior
  • RegistryQueryForPasswords
  • SuspiciousWdavExclusion
  • ASEPRegKey
  • CobaltStrikeExecutionDetection
  • DefenderBackdoor
  • DefenderBehaviorSuspiciousActivity
  • DefenderMalwareExecuted
  • DefenderServerAlertDomainController
  • DupTokenPrivilegeEscalationDetector
  • FakeWindowsBinary
  • IoaMaliciousCmdlets
  • LivingOffTheLandBinary
  • MicrosoftSignedBinaryAbuse
  • MicrosoftSignedBinaryScriptletAbuse
  • MLFileBasedWithRemoting
  • MLSuspSvchostBehavior
  • ReadSensitiveMemory
  • RemoteCodeInjection-IREnabled
  • Scuba-EchoSeenOverPipeOnLocalhost
  • Scuba-SuspiciousWebScriptFileDrop
  • Suspicious DLL registration by odbcconf
  • Suspicious DPAPI Activity
  • Suspicious Exchange Process Execution
  • Suspicious scheduled task launch
  • SuspiciousLdapQueryDetector
  • SuspiciousScheduledTaskRegistration
  • Untrusted application opens a RDP connection

Identify the line of business (LOB) apps that are unavailable due to the incident

  • Does the app require an identity?
    • How is authentication performed?
    • How are credentials such as certificates or secrets stored and managed?
  • Are evaluated backups of the application, its configuration, and its data available?
  • Determine your compromise recovery process.

Eradication and recovery

Use these steps to eradicate the threat and recover damaged resources.

Step 1: Verify your backups

If you have offline backups, you can probably restore the data that has been encrypted after you've removed the ransomware payload (malware) from your environment and after you've verified that there's no unauthorized access in your Microsoft 365 tenant.

Step 2: Add indicators

Add any known attacker communication channels as indicators, blocked in firewalls, in your proxy servers, and on endpoints.

Step 3: Reset compromised users

Reset the passwords of any known compromised user accounts and require a new sign-in.

  • Consider resetting the passwords for any privileged account with broad administrative authority, such as the members of the Domain Admins group.
  • If a user account might have been created by an attacker, disable the account. Don't delete the account unless there are no plans to perform security forensics for the incident.

Step 4: Isolate attacker control points

Isolate any known attacker control points inside the enterprise from the Internet.

Step 5: Remove malware

Remove the malware from the affected devices.

  • Run a full, current antivirus scan on all suspected computers and devices to detect and remove the payload that is associated with the ransomware.
  • Don't forget to scan devices that synchronize data or the targets of mapped network drives.

Step 6: Recover files on a cleaned device

Recover files on a cleaned device.

  • You can use File History in Windows 11, Windows 10, Windows 8.1, and System Protection in Windows 7 to attempt to recover your local files and folders.

Step 7: Recover files in OneDrive for Business

Recover files in OneDrive for Business.

  • Files Restore in OneDrive for Business allows you to restore an entire OneDrive to a previous point in time within the last 30 days. For more information, see Restore your OneDrive.

Step 8: Recover deleted email

Recover deleted email.

Step 9: Re-enable Exchange ActiveSync and OneDrive sync

  • After you've cleaned your computers and devices and recovered the data, you can re-enable Exchange ActiveSync and OneDrive sync that you previously disabled in step 3 of containment. [!INCLUDE Microsoft Defender XDR rebranding]