ATT&CK coverage › Technique
Impair Defenses T1562
Adversaries may maliciously modify components of a victim environment in order to hinder or disable defensive mechanisms. This not only involves impairing preventative defenses, such as firewalls and anti-virus, but also detection capabilities that defenders can use to audit activity and identify malicious behavior. This may also span both native defenses as well as supplemental capabilities installed by users and administrators.
Events covered
19 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 35 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 (28 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 (439 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 (1 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 20 rules
- ETW Logging Disabled For rpcrt4.dll
- ETW Logging Disabled For SCM
- ETW Logging Disabled In .NET Processes - Registry
- ETW Logging Disabled In .NET Processes - Sysmon Registry
- ETW Logging Tamper In .NET Processes Via CommandLine
- Filter Driver Unloaded Via Fltmc.EXE
- HackTool - EDRSilencer Execution
- HackTool - EDRSilencer Execution - Filter Added
- Hide Schedule Task Via Index Value Tamper
- Potential Suspicious Activity Using SeCEdit
- Potential Windows Defender Tampering Via Wmic.EXE
- Removal Of Index Value to Hide Schedule Task - Registry
- Removal Of SD Value to Hide Schedule Task - Registry
- Sysmon Application Crashed
- Sysmon Driver Unloaded Via Fltmc.EXE
- WFP Filter Added via Registry
- Windows Defender Exclusions Added - PowerShell
- Windows Filtering Platform Blocked Connection From EDR Agent Binary
- Windows Firewall Disabled via PowerShell
- Write Protect For Storage Disabled
Elastic 3 rules
- Kerberos Pre-authentication Disabled for User
- Potential Evasion via Windows Filtering Platform
- Sensitive Audit Policy Sub-Category Disabled
Splunk 5 rules
- Unloading AMSI via Reflection
- Windows Increase in Group or Object Modification Activity
- Windows Increase in User Modification Activity
- Windows Outlook Dialogs Disabled from Unusual Process
- Windows Registry Delete Task SD