This detection identifies adversaries executing Mimikatz to extract credentials and secrets directly from system memory, a technique frequently used during post-compromise lateral movement. SOC teams should proactively hunt for this activity in Azure Sentinel because memory dumping is often a precursor to credential theft that can lead to domain-wide compromise if not immediately contained.
rule Mimikatz_Memory_Rule_2 : APT {
meta:
description = "Mimikatz Rule generated from a memory dump"
author = "Florian Roth - Florian Roth"
type = "memory"
score = 80
strings:
$s0 = "sekurlsa::" ascii
$x1 = "cryptprimitives.pdb" ascii
$x2 = "Now is t1O" ascii fullword
$x4 = "ALICE123" ascii
$x5 = "BOBBY456" ascii
condition:
$s0 and 1 of ($x*)
}
This YARA rule can be deployed in the following contexts:
This rule contains 5 string patterns in its detection logic.
Here are 5 specific false positive scenarios for the Mimikatz Rule generated from a memory dump, including targeted filters and exclusions:
Scheduled Credential Harvesting by Backup Agents
mimikatz.exe (or a similar binary) as part of their credential extraction routine, triggering the rule even though no human interaction occurred.Veeam.Backup.Service.exe or commvault.cmd and the executable path matches the known backup agent installation directory (e.g., C:\Program Files\Veeam\Backup and Replication\...).Automated Onboarding Scripts via PowerShell
mimikatz.exe with specific command-line arguments in a non-interactive session.SYSTEM or a dedicated service account (e.g., svc-onboarding) and the command line contains specific flags like /quiet, /script, or references to internal script paths (e.g., C:\Scripts\Onboard\Mimikatz.ps1).Endpoint Detection and Response (EDR) Health Checks