System Network Configuration Discovery T1016
Adversaries may look for details about the network configuration and settings, such as IP and/or MAC addresses, of systems they access or through information discovery of remote systems. Several operating system administration utilities exist that can be used to gather this information. Examples include Arp, ipconfig/ifconfig, nbtstat, and route.
Events covered
9 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Sysmon | Event ID 3 | Network connection |
| Sysmon | Event ID 22 | DNSEvent (DNS query) |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| Defender-DeviceProcessEvents | any | Process activity (any) |
| DNS-Server-Service | Event ID 6004 | The DNS server received a zone transfer request from param1 for a non-existent or non-authoritative zone param2. |
| PowerShell | Event ID 4103 | Payload Context: ContextInfo User Data: UserData. |
| PowerShell | Event ID 4104 | Creating Scriptblock text (MessageNumber of MessageTotal). |
| PowerShell | Event ID 800 | Event ID 800 |
Authoring guide
Patterns shared across the 43 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 (34 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 (399 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 (76 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 12 rules
- Failed DNS server zone transfer for enumeration purposes
- Firewall Configuration Discovery Via Netsh.EXE
- Firewall configuration enumerated (command)
- Firewall configuration enumerated (PowerShell)
- Local Firewall Rules Enumeration Via NetFirewallRule Cmdlet
- Nltest.EXE Execution
- Potential Pikabot Discovery Activity
- Potential Recon Activity Via Nltest.EXE
- Scheduled task enumerated
- Suspicious Network Command
- Suspicious Network Connection to IP Lookup Service APIs
- Winlogon process contact to C2 - Blacklotus (Sysmon)
Elastic 10 rules
- Active Directory Discovery using AdExplorer
- AdFind Command Activity
- Enumeration Command Spawned via WMIPrvSE
- External IP Lookup from Non-Browser Process
- Remote System Discovery Commands
- Suspicious JetBrains TeamCity Child Process
- Suspicious MS Office Child Process
- Suspicious PDF Reader Child Process
- System Public IP Discovery via DNS Query
- Wireless Credential Dumping using Netsh Command
Splunk 18 rules
- Adfind Commands (PowerShell)
- Adfind Commands (Sysmon)
- Adfind Commands (Windows Event Log)
- Adfind Execution (EDR)
- Adfind Execution (PowerShell)
- Adfind Execution (Sysmon)
- Adfind Execution (Windows Event Log)
- Domain Controller Enumeration via nltest (PowerShell)
- Domain Controller Enumeration via nltest (Sysmon)
- Domain Controller Enumeration via nltest (Windows Event Log)
- Multiple nslookup commands (Sysmon)
- Multiple nslookup commands (Windows Event Log)
- Network Discovery Using Route Windows App
- Nslookup Execution (Windows Event Log)
- Potential System Network Configuration Discovery Activity
- Windows PowerShell Invoke-RestMethod IP Information Collection
- Windows System Network Config Discovery Display DNS
- Windows WinPEAS PowerShell Script Execution