- How do SOC analysts detect Remote System Discovery?
- Detection centers on SIEM, Firewall telemetry for the discovery phase of the attack. Hunt on the full command line. Event 4688 carries Process Command Line only after the "Include command line in process creation events" policy is enabled, and it is off by default; Sysmon Event ID 1 logs the full command line plus a ProcessGUID for correlation. Flag net view /domain, net group "Domain computers", nltest /dclist: or /dsgetdc and Get-ADComputer -Filter * when two or more come from the same parent within minutes. FIN8, HAFNIUM and Wizard Spider all ran nltest /dclist, and APT29 used AdFind in the SolarWinds intrusion. A cmdlet runs inside the PowerShell process, so Get-ADComputer typed in an open session leaves no 4688 or Sysmon 1 of its own. Turn on script block logging and search event 4104 in the Microsoft-Windows-PowerShell/Operational log for Get-ADComputer -Filter * or an LDAPFilter that returns every computer object, especially from an account outside IT.
- What does a Remote System Discovery alert look like?
- A representative SIEM detection is "Ping Sweep Executed Across Internal Network" (medium severity): ICMP echo request flood detected from workstation WS-ACCT-011: 4,096 ping requests to the 10.10.0.0/20 internal subnet within 90 seconds. The workstation has an accounting function and should not be performing network discovery. The sweep received responses from 847 live hosts, providing the attacker with a comprehensive map of active systems on the internal network as a foundation for targeted lateral movement.
- Which tools detect Remote System Discovery, and how can I practice?
- Remote System Discovery (T1018) is best surfaced with SIEM, Firewall telemetry, which exposes the discovery signals described above. SOCSimulator covers it in Pro simulations on those consoles; the surrounding detection skills are free to practice in SOCSimulator Operations.