Home  >  APT29  >  Results  >  Elastic  >  Remote System Discovery

Technique Results: Remote System Discovery (T1018) Technique Page Information

The ATT&CK technique page displays all procedures used to test the technique, and their respective detections. The Procedure column contains a description of how the technique was tested . The Step column is where the procedure occurred in the operational flow. Click the Step Number to view it in the Operational Flow panel. Detections are classified by one or more Detection Types, summarized by the Detection Notes, and may be supported by screenshots.

MITRE does not assign scores, rankings, or ratings. The evaluation results are available to the public, so other organizations may provide their own analysis and interpretation - these are not endorsed or validated by MITRE.

Vendor Configuration     All Results JSON Legend
Legend
Main Detection Categories: Detection Modifiers:

None

Telemetry

Indicator of
Compromise

General
Behavior

MSSP

General

Tactic

Specific
Behavior

Technique

Enrichment

Tainted

Alert

Correlated

Delayed

Host
Interrogation

Residual
Artifact

Configuration
Change

Innovative
Procedures Criteria Step
Detection Type Detection Notes
Enumerated remote systems using LDAP queries
powershell.exe making LDAP queries over port 389 to the Domain Controller (10.0.0.4)
8.A.1
Telemetry (Correlated)
Telemetry showed powershell.exe establishing a connection to NewYork (10.0.0.4) over TCP port 389. The detection was correlated to a parent alert for malicious file execution. [1]
Enumerated the domain controller host NewYork (10.0.0.4) using LDAP queries
powershell.exe making LDAP queries over port 389 via functions from System.DirectoryServices.dll
16.A.1
Telemetry (Correlated)
Telemetry showed PowerShell executing the Get-NetDomainController cmdlet then subsequently making a network connection to the domain controller NewYork (10.0.0.4) over TCP port 389. The detection was correlated to a parent alert for a suspicious Windows script. [1] [2] [3]