Impair Defenses: Disable or Modify Tools T1562.001

Tactic: Stealth

Adversaries may modify and/or disable security tools to avoid possible detection of their malware/tools and activities. This may take many forms, such as killing security software processes or services, modifying / deleting Registry keys or configuration files so that tools do not operate properly, or other methods to interfere with security tools scanning or reporting information. Adversaries may also disable updates to prevent the latest security patches from reaching tools on victim systems.

Events covered

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

Authoring guide

Patterns shared across the 158 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 (107 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
EventType55eq 29, in 24, ne 2exec, ProcessRollup2, exec_event, CHANGE_APPLICATION_SETTING, A process changed a file creation time
event.type40eq 34, in 5, ne 1start, change, process_started, deletion, creation
data_stream.dataset37eq 37aws.cloudtrail, o365.audit, azure.activitylogs, github.audit, google_workspace.admin
event.outcome30eq 26, in 4success, Success
process_name26eq 20, in 6, starts_with 2, is_not_null 1, wildcard 1chkconfig, kill, service, bash, defaults
Provider_Name25eq 24, in 1Exchange, bedrock.amazonaws.com, cloudtrail.amazonaws.com, config.amazonaws.com, guardduty.amazonaws.com
host.os.type25eq 24, in 1
EventID22eq 21, in 1, regex_match 14688, 1, 4104, 4656, 13
process.args22eq 14, in 7, wildcard 4, contains 2, starts_with 2-c, disable, *.EndpointSecurity, -*a*, --clear
event.category18eq 15, in 3web, process, iam, configuration, dns
CommandLine11contains 10, regex_match 1 -enc, (?i)(stop.*(ShellHWDetection|AVPSUS|McAfeeDLPAgentService..., -e , -en , /etc/sysctl.conf
action11in 9, eq 2CreateIgnoreRule, CreateMalwareExclusion, DeleteAutomationRule, DeleteCICDScanPolicy, DeleteConnector
Details10eq 8, is_not_null 2, contains 1, in 10, 0x00000000, 0x00000001, 0x00000004, 0x00000003
registry_value_name7eq 7AmsiEnable, ConsentPromptBehaviorAdmin, DisableAntiSpyware, DisableBehaviorMonitoring, DisableBlockAtFirstSeen
status7eq 7SUCCESS

Top indicator values (1117 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.

FieldKindValueRules (here)Corpus reach
event.outcomeeq
success
26251
event.typeeq
start
21606
event.typeeq
change
1277
data_stream.dataseteq
aws.cloudtrail
14141
data_stream.dataseteq
o365.audit
1145
data_stream.dataseteq
azure.activitylogs
534
EventTypein
exec
13171
EventTypein
ProcessRollup2
12117
EventTypein
exec_event
12139
EventTypein
start
12134
EventTypein
executed
788
EventTypein
process_started
774
Provider_Nameeq
Exchange
1019
event.categoryeq
web
920
event.categoryeq
process
5128
statuseq
SUCCESS
716
EventDatacontains
set-mppreference
55
EventDatacontains
add-mppreference
44
EventIDeq
4688
5313
process.argseq
off
56
process.argseq
stop
57
Detailseq
0
412
Detailseq
0x00000000
443
event.outcomein
Success
437
event.outcomein
success
438
event.typein
process_started
440
event.typein
start
442
process.argsin
stop
44
process_nameeq
chkconfig
44
process_nameeq
service
44

Exclusions (132 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.

FieldKindValueRules excluding
aws::userAgenteq
AWS Internal
3
user.ideq
S-1-5-18
3
CommandLinecontains
drop_caches
1
CurrentDirectorywildcard
/tmp/makeself*NVIDIA-Linux*
1
CurrentDirectorywildcard
/tmp/self*NVIDIA-Linux*
1
Detailseq
0x00000001
1
Detailseq
0x00000002
1
Detailseq
1
1
Detailseq
2
1
Imageeq
?:\program files (x86)\trend micro\security agent\ntrmv.exe
1
Imageeq
?:\windows\system32\securityhealthservice.exe
1
Imageeq
?:\windows\system32\services.exe
1
Imageeq
?:\windows\system32\svchost.exe
1
Imagewildcard
/applications/.com.bomgar.scc.*/remote support customer...
1
Imagewildcard
/applications/cewe fotoschau.app/contents/macos/fotoplus
1

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.

Platform (all)
Domain (all)

Sigma 14 rules

Elastic 82 rules

Splunk 15 rules

Kusto 12 rules

YARA-L 10 rules

Panther 25 rules