Ping can be used to identify remote systems within a network.2
Discovery39 detection rules
Standing S0097
Reach is how much of ATT&CK this tool touches. Coverage is how well defended each thing it does is, as a median per technique rather than a total — a total would just restate the reach. Each figure is ranked against all 825 ATT&CK software entries only where that population actually spreads. Where most of the population shares one value, a percentile would rank the tie instead of the entity, so the raw value is shown and no rank is claimed.
Reach
Technique1Bottom 5%
5th percentile · 95% of 825 ATT&CK software entries have more Enterprise techniques.
Tactic1Bottom 6%
6th percentile · 94% of 825 ATT&CK software entries have more tactics spanned.
Threat groups1561% tie · 22 values
61% of the population shares a single value across only 22 distinct values, so a percentile here would rank the tie, not the entity.
Campaigns485% tie · 8 values
85% of the population shares a single value across only 8 distinct values, so a percentile here would rank the tie, not the entity.
Coverage
Rules / technique39medTop 14%
86th percentile · 86% of 825 ATT&CK software entries have this many detection rules per technique or fewer.
Tests / technique23med
Ping detections S0097
39 distinct rules cover the 1 technique recorded for this tool. 22 Splunk · 17 Sigma.
1 covered by at least one rule39 distinct rules in total
Showing 1-39 of 39 rules
Drag headers to reorder | Drag edges to resize
Select
Title
Description
Category
Status
Event
OS
Product
MITRE ATT&CK
CVEs
Severity
Author
Created
Updated
ID
Refs
Detects usage of the "Get-AdComputer" to enumerate Computers or properties within Active Directory.
The following analytic detects the execution of `nltest.exe` with command-line arguments `/dclist:` or `/dsgetdc:` to discover domain controllers. (...)
The following analytic identifies the execution of `wmic.exe` with command-line arguments used to discover domain controllers in a Windows domain. (...)
The following analytic detects the execution of `powershell.exe` with the `Get-AdComputer` commandlet, which is used to discover remote systems within a domain. (...)
The following analytic detects the execution of the `Get-AdComputer` PowerShell commandlet using PowerShell Script Block Logging (EventCode=4104). (...)
The following analytic detects the execution of `powershell.exe` with command-line arguments that utilize `Get-DomainComputer` to discover remote systems. (...)
The following analytic detects the execution of `powershell.exe` with the `Get-DomainController` command, which is used to discover remote systems within a Windows domain. (...)
The following analytic detects the execution of `powershell.exe` with command-line arguments that utilize the `Get-WmiObject` cmdlet to discover remote systems, specifically targeting the `DS_Computer` parameter. (...)
The following analytic detects the execution of the `Get-WmiObject` cmdlet with the `DS_Computer` class parameter via PowerShell Script Block Logging (EventCode=4104). (...)
The following analytic detects the use of the `[Adsisearcher]` type accelerator in PowerShell scripts to query Active Directory for domain computers. (...)
The following analytic detects the execution of `dsquery.exe` with the `computer` argument, which is used to discover remote systems within a domain. (...)
The following analytic identifies the execution of `adfind.exe` standalone or with specific command-line arguments related to Active Directory queries. (...)
Jose Hernandez, Bhavin Patel, Nasreddine Bencherchali, Splunk
2020-12-17
2026-10-02
bd3b0187-189b-46c0-be45-f52da2bae67f
Splunk
The following analytic detects the use of the Get-ADComputer cmdlet with parameters indicating a search for Windows endpoints with Kerberos Unconstrained Delegation. (...)