Home  >  APT29  >  Results  >  F-Secure  >  Bypass User Account Control

Technique Results: Bypass User Account Control (T1088) 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
Executed elevated PowerShell payload
High integrity powershell.exe spawning from control.exe​​ (spawned from sdclt.exe)
3.B.2
General (Alert)
A General alert detection (high severity) was generated due to powershell.exe running with parameters associated with post exploitation payloads. [1]
MSSP (Delayed (Manual))
An MSSP detection occurred for User DMEVALS\pam launching a command prompt from which the sdclt.exe program was used. [1]
Telemetry
Telemetry showed control.exe creating a high integrity powershell.exe. [1]
Executed elevated PowerShell payload
High integrity powrshell.exe spawning from control.exe​​ (spawned from sdclt.exe)
14.A.2
General (Alert)
A General alert detection (high severity) was generated due to powershell.exe running with parameters associated with post exploitation payloads. [1]
MSSP (Delayed (Manual))
An MSSP detection occurred containing evidence of executed function "bypass." [1] [2]
Telemetry
Telemetry showed a new High Integrity PowerShell callback spawned from control.exe (indicated by the true "elev" flag). [1]