Home  >  APT29  >  Results  >  Elastic  >  System Owner/User Discovery

Technique Results: System Owner/User Discovery (T1033) 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 the current username using PowerShell
powershell.exe executing $env:USERNAME
4.C.2
Telemetry (Correlated)
Telemetry showed powershell.exe executing $env:USERNAME. The event was correlated to a parent General detection for malicious file execution. [1]
Checked that the username is not related to admin or a generic value (ex: user) using PowerShell
powershell.exe executing a Get-WmiObject query for Win32_ComputerSystem
11.A.6
Tactic (Alert)
A Tactic alert detection (medium severity) called "Reconnaissance of Multiple WMI Classes" was generated for powershell.exe enumerating WMI classes associated with System Information Discovery. [1]
Telemetry
Telemetry showed the PowerShell gwmi query for Win32_ComputerSystem. [1]
Enumerated the current username using the GetUserNameEx API
powershell.exe executing the GetUserNameEx API
13.C.1
Telemetry (Correlated)
Telemetry showed PowerShell executing the GetUserNameEx API. The event was correlated to a parent General detection for a suspicious Windows script. [1]
Enumerated logged on users using PowerShell
powershell.exe executing $env:UserName
15.A.1
Telemetry (Correlated)
Telemetry showed PowerShell script block executing $env:UserName. The event was correlated to a parent General detection for a suspicious Windows script. [1]
Enumerated the domain SID (from current user SID) using the ConvertSidToStringSid API
powershell.exe executing the ConvertSidToStringSid API
16.B.1
Telemetry (Correlated)
Telemetry showed PowerShell executing the ConvertSidToStringSid API function. The detection was correlated to a parent alert for a suspicious Windows script. [1]