ATT&CK coverage › Technique
Indicator Removal T1070
Adversaries may delete or modify artifacts generated within systems to remove evidence of their presence or hinder defenses. Various artifacts may be created by an adversary or something that can be attributed to an adversary’s actions. Typically these artifacts are used as defensive indicators related to monitored events, such as strings from downloaded files, logs that are generated from user actions, and other data analyzed by defenders. Location, format, and type of artifact (such as command or login history) are often specific to each platform.
Events covered
12 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 24 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 (21 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 (136 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.
Common exclusions (13 distinct)
Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). 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.
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 16 rules
- Clearing Windows Console History
- Disable of ETW Trace - Powershell
- DLL Load By System Process From Suspicious Locations
- ETW Trace Evasion Activity
- EventLog EVTX File Deleted
- Exchange PowerShell Cmdlet History Deleted
- Filter Driver Unloaded Via Fltmc.EXE
- Fsutil Suspicious Invocation
- IIS WebServer Access Logs Deleted
- IIS WebServer Log Deletion via CommandLine Utilities
- Potential Ransomware or Unauthorized MBR Tampering Via Bcdedit.EXE
- PowerShell Console History Logs Deleted
- Shadow Copies Deletion Using Operating Systems Utilities
- Sysmon Driver Unloaded Via Fltmc.EXE
- Terminal Server Client Connection History Cleared - Registry
- Tomcat WebServer Logs Deleted
Elastic 3 rules
- Potential Timestomp in Executable Files
- Sensitive Audit Policy Sub-Category Disabled
- Windows Event Logs Cleared