ATT&CK coverage › Technique

Software Discovery: Security Software Discovery T1518.001

Adversaries may attempt to get a listing of security software, configurations, defensive tools, and sensors that are installed on a system or in a cloud environment. This may include things such as cloud monitoring agents and anti-virus. Adversaries may use the information from Security Software Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing4688A new process has been created.
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).

Authoring guide

Patterns shared across the 4 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 (4 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
Image2ends_with 2\findstr.exe, \find.exe
OriginalFileName2eq 2FINDSTR.EXE, FIND.EXE
CommandLine2ends_with 1, match 1 avira", defender", kaspersky", 385201
ScriptBlockText1match 1\*symantec\*, Path -like, gps | where

Top indicator values (45 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
Imageends_with\find.exe28
OriginalFileNameeqFINDSTR.EXE210
Imageends_with\findstr.exe211
OriginalFileNameeqFIND.EXE26
ScriptBlockTextmatch\*malware\*1
ScriptBlockTextmatchName -like1
ScriptBlockTextmatch\*sentinel\*1
ScriptBlockTextmatchget-process | \?1
ScriptBlockTextmatchProduct -like1
ScriptBlockTextmatchDescription -like1
ScriptBlockTextmatch\*virus\*1
ScriptBlockTextmatchPath -like1
ScriptBlockTextmatch\*defender\*1
ScriptBlockTextmatchgps | \?1
ScriptBlockTextmatchget-process | where1
ScriptBlockTextmatch\*cylance\*1
ScriptBlockTextmatch\*kaspersky\*1
ScriptBlockTextmatch\*avira\*1
ScriptBlockTextmatchCompany -like1
ScriptBlockTextmatch\*symantec\*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.

Sigma 3 rules

Kusto Query Language 1 rule