ATT&CK coverage › Technique

Active Scanning: Vulnerability Scanning T1595.002

Adversaries may scan victims for vulnerabilities that can be used during targeting. Vulnerability scans typically check if the configuration of a target host/application (ex: software and version) potentially aligns with the target of a specific exploit the adversary may seek to use.

Events covered

1 catalog event are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon3Network connection

Authoring guide

Patterns shared across the 1 rule 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 (5 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
All_Traffic.app1eq 1"*\\*"
dest_count1gt 110
sourcetype1eq 1XmlWinEventLog
port_count1gt 110
DestinationPort1lt 132000

Top indicator values (5 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
All_Traffic.appeq"*\\*"1
port_countgt101
sourcetypeeqXmlWinEventLog1
DestinationPortlt320001
dest_countgt101

Common exclusions (10 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.

FieldKindValueRules excluding
DestinationPortin251
DestinationPortin801
DestinationPortin84431
DestinationPortin32681
DestinationPortin3891
DestinationPortin53531
DestinationPortin531
DestinationPortin80801
DestinationPortin881
DestinationPortin4431

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.

Splunk 1 rule