Exploitation for Stealth T1211
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
Events covered
6 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| Application-Error | Event ID 1000 | Faulting application name: Faulting_application_name, version: version, time stamp: 0xFaulting_module_name. |
| Defender-DeviceFileEvents | FileRenamed | File renamed |
| Audit-CVE | Event ID 1 | Possible detection of CVE: PossibleDetectionOfCVE. |
| Windows-Error-Reporting | Event ID 1001 | Fault bucket , type. |
Authoring guide
Patterns shared across the 9 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names 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 (8 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.
Top indicator values (42 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. Click a value to expand the rules under this technique that use it.
Exclusions (1 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
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
- Audit CVE Event
- Microsoft Malware Protection Engine Crash
- Microsoft Malware Protection Engine Crash - WER
- Writing Of Malicious Files To The Fonts Folder
Splunk 4 rules
- Conhost.exe Kernel call (Sysmon)
- Conhost.exe Kernel call (Windows Event Log)
- Suspicious Conhost.exe Commands (Sysmon)
- Suspicious Conhost.exe Commands (Windows Event Log)