ATT&CK coverage › Technique

Exploitation for Defense Evasion T1211

Adversaries may exploit a system or application vulnerability to bypass security features. Exploitation of a vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Vulnerabilities may exist in defensive security software that can be used to disable or circumvent them.

Events covered

6 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing4688A new process has been created.
Application-Error1000Faulting application name: Faulting_application_name, version: version, time stamp: 0xFaulting_module_name.
Defender-DeviceFileEvents9002004File renamed
Audit-CVE1Possible detection of CVE: PossibleDetectionOfCVE.
Windows-Error-Reporting1001Fault bucket , type.

Authoring guide

Patterns shared across the 5 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (5 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
Provider_Name3eq 3Audit-CVE, Microsoft-Windows-Audit-CVE, Application Error, Windows Error Reporting
Data2match 2MsMpEng.exe, mpengine.dll
ActionType1eq 1FileRenamed
InitiatingProcessFileName1in 1powerpnt.exe, winword.exe, outlook.exe
CommandLine1match 1C:\Windows\Fonts\, .vbs, .bin

Top indicator values (36 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
Datamatchmpengine.dll22
DatamatchMsMpEng.exe22
InitiatingProcessFileNameinoutlook.exe1
ActionTypeeqFileRenamed1
InitiatingProcessFileNameinwinword.exe1
InitiatingProcessFileNameinpowerpnt.exe1
InitiatingProcessFileNameinexcel.exe1
Provider_NameeqAudit-CVE1
Provider_NameeqMicrosoft-Windows-Audit-CVE1
Provider_NameeqApplication Error12
Provider_NameeqWindows Error Reporting1
CommandLinematch.vbs15
CommandLinematch.inf13
CommandLinematch.vb13
CommandLinematchtype12
CommandLinematch.scr15
CommandLinematchecho13
CommandLinematch.pl12
CommandLinematch.sh12
CommandLinematch.cmd15

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 4 rules

Kusto Query Language 1 rule