By identifying similar patterns of behavior within different variants, we've come up with some proactive rules for our Endpoint products: Endpoint Security (ENS) and Trellix Endpoint (formerly MVISION Endpoint). These rules intend to effectively prevent the installation or the payload of historical, current, and evolving new variants of these threats.
From internal Support testing, we've found the following ENS countermeasures effective against several types of ransomware attacks:
ENS Adaptive Threat Protection JTI Rules (ATP):
Enable or disable the settings for the rules below within the ePolicy Orchestrator (ePO) Server Settings under Adaptive Threat Protection. There're three different configurations: Productivity, Balanced, and Security. The changes made within Server Settings apply to rule group assignments in the ATP Options policy.
Rule ID 4: Use GTI file reputation to identify trusted or malicious files
Rule ID 5: Use GTI URL reputation to identify trusted or malicious processes
Rule ID 239: Identify suspicious command parameter execution
Rule ID 240: Identify suspicious files with characteristics that have been predominantly seen in ransomware
Rule ID 255: Detect potentially obfuscated command-line parameters
Rule ID 263: Detect processes accessing suspicious URLs
Rule ID 300: Prevent office applications from starting child processes that can execute script commands
Rule ID 309: Block processes attempting to launch from Office applications.
Rule ID 312: Prevent email applications, such as Outlook, from spawning script editors and dual use tool
Rule ID 313: Prevent text editors like Notepad and WordPad from spawning processes that can execute script commands in all rule group assignments
Rule ID 316: Prevent PDF readers from starting processes that can execute scripts in all rule group assignments
Rule ID 318: Prevent PDF readers from starting cmd.exe
Rule ID 319: Prevent cmd.exe from starting other script interpreters such as cscript or PowerShell in all rule group assignments
Rule ID 323: Prevent mshta from being launched as a child process.
Rule ID 332: Prevent certutil.exe from downloading or decoding files with suspect extensions
Rule ID 341: Identify and block patterns being used in Ransomware attacks in security rule group assignments.
Rule ID 342: Identify and block patterns being used in Ransomware attacks
Rule ID 502: Detect new service creation
Rule ID 513: Detect commands used for copying files from a remote system
Rule ID 517: Prevent actor process with unknown reputations from launching processes in common system folders
ENS Dynamic Application Containment (DAC):
DAC is triggered only if the reputation for the process meets the reputation criteria defined in the ATP Options policy. When a process is contained by DAC, it's subject to post execution monitoring and any rules enabled within the DAC policy.
Rule: Deleting files commonly targeted by ransomware-class malware
Rule: Disabling critical operating system executables
Rule: Modifying appinit DLL registry entries
Rule: Modifying Image File Execution Options registry entries
Rule: Modifying screen saver settings
Rule: Modifying startup registry locations
Rule: Reading files commonly targeted by ransomware-class malware
Rule: Suspending a process
Rule: Terminating another process
Rule: Reading from another process' memory
Rule: Writing to files commonly targeted by ransomware-class malware
NOTE: For best practices, see
KB87843 - Dynamic Application Containment rules and best practices. Similar to Access Protection rules, test all DAC rules to prevent interruptions in your environment.
ENS Threat Prevention Anti-Malware Scan Interface (AMSI):
Enable integration with AMSI. AMSI provides enhanced script scanning. AMSI is a generic interface standard that allows applications and services to integrate with Threat Prevention, providing better protection against malware. Microsoft provides AMSI. AMSI is supported on Windows 10 and Windows Server 2016 (and later) systems. Use AMSI to enhance scanning for threats in non-browser-based scripts, such as
PowerShell, WScript, and
CScript.
ENS Exploit Prevention:
Signature 344: New StartUp Creation
Signature 413: Suspicious Double File Extension Execution
Signature 428: Generic Buffer Overflow
Signature 6107: MS Word trying to execute unwanted programs
Signature 6108: Suspicious download string script execution
Signature 6113: Fileless Threat: Reflective Self Injection
Signature 6114: Fileless Threat: Reflective EXE Self Injection
Signature 6115: Fileless Threat: Reflective DLL Remote Injection
Signature 6116: Mimikatz LSASS Suspicious Memory Read
Signature 6117: Mimikatz LSASS Suspicious Memory DMP Read
Signature 6120: Fileless Threat: Process Hollowing
Signature 6121: Fileless Threat: Process Hollowing
Signature 6127: Suspicious LSASS Access from PowerShell
Signature 6131: Weaponized OLE object infection via WMI
Signature 6148: Malware Behavior: Windows EFS abuse
Signature 6153: Malware Behavior: Ryuk Ransomware activity detected
Signature 6155: Malicious Behavior: Directory Junction attempt detected
ENS Exploit Prevention Expert Rules:
The Trellix Advanced Research Center
GitHub repository contains a set of Expert Rule samples that can be directly used with ENS in the Exploit Prevention policy. The Expert Rules below are specific to targeting ransomware attacks:
Detect_Deletion_Of_Shadow_Copies_Using_WMIC.EXE.md.txt
Detect_Suspicious_Usage_Of_VSSADMIN.EXE.md.txt
File_Block_Rclone (Two scenarios provided for this rule.)
ENS Access Protection Default Rules:
Browsers launching programs from downloaded programs file folders
Creating new executable file in the programs files folder
Creating new executable file in the windows folder
Disabling registry editor and task manager
Doppelganger attack on processes
Executing mimikatz malware
Executing scripts by windows script host
Remotely creating or modifying files or folders
Remotely creating or modifying PE,.INI and core system locations