Gather Victim Network Information T1590
Tactic: Reconnaissance
Adversaries may gather information about the victim's networks that can be used during targeting. Information about networks may include a variety of details, including administrative data (ex: IP ranges, domain names, etc.) as well as specifics regarding its topology and operations.
Events covered
13 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 17 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 (25 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 (222 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.
Exclusions (39 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.
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 4 rules
- Failed DNS Zone Transfer
- PUA - Advanced IP/Port Scanner Update Check
- PUA - Crassus Execution
- Suspicious DNS Query for IP Lookup Service APIs
Elastic 1 rule
Splunk 8 rules
- Cisco ASA - Reconnaissance Command Activity
- Cisco IOS XE Reconnaissance Command Activity
- Cisco NVM - Suspicious Network Connection to IP Lookup Service API
- Local LLM Framework DNS Query
- Wermgr Process Connecting To IP Check Web Services
- Windows DNS Gather Network Info
- Windows Gather Victim Network Info Through Ip Check Web Services
- Windows WinPEAS PowerShell Script Execution
Kusto 4 rules
- AWSCloudTrail - Suspicious AWS CLI Command Execution
- Network Port Sweep from External Network (ASIM Network Session schema)
- Rare client observed with high reverse DNS lookup count - Anomaly based (ASIM DNS Solution)
- Rare client observed with high reverse DNS lookup count - Static threshold based (ASIM DNS Solution)