Home  >  APT29  >  Results  >  F-Secure  >  Service Execution

Technique Results: Service Execution (T1035) 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 python.exe using PSExec
python.exe spawned by PSEXESVC.exe
8.C.3
Technique (Alert, Correlated)
A Technique alert detection (low severity) for "Service Execution" was generated due to PsExec running a process remotely. The event was correlated to parent alert for Abnormal File Modification. [1]
MSSP (Delayed (Manual))
An MSSP detection occurred containing evidence of PSEXESVC.exe executing python.exe. [1] [2]
Telemetry
Telemetry showed python.exe spawned by PSEXESVC.exe. [1]
Executed persistent service (javamtsup) on system startup
javamtsup.exe spawning from services.exe
10.A.1
None
No detection capability demonstrated for this procedure.