Home >
Enterprise >
Participants >
CrowdStrike >
Process Discovery (T1057)
|
|
Carbanak+FIN7 |
||||||||
Step | ATT&CK Pattern |
|
||||||
2.A.4
|
Tactic Discovery (TA0007) |
|
||||||
5.B.3
![]() |
Tactic Discovery (TA0007) |
|
||||||
13.A.1
|
Tactic Discovery (TA0007) |
|
||||||
15.A.1
|
Tactic Discovery (TA0007) |
|
||||||
20.B.2
|
Tactic Discovery (TA0007) |
|
APT29 |
||||
Step | ATT&CK Pattern |
|
||
4.B.1
|
Tactic Discovery (TA0007) |
|
||
4.C.5
|
Tactic Discovery (TA0007) |
|
||
8.A.3
|
Tactic Discovery (TA0007) |
|
||
11.A.8
|
Tactic Discovery (TA0007) |
|
||
13.D.1
|
Tactic Discovery (TA0007) |
|
||
14.B.2
|
Tactic Discovery (TA0007) |
|
Procedure
Checked that processes such as procexp.exe, taskmgr.exe, or wireshark.exe are not running using PowerShell
Criteria
powershell.exe executing a Get-WmiObject query for Win32_Process
Footnotes
- PowerShell script block content for this step was collected on sensor, but at execution time did not meet confidence threshold to be sent to cloud for further analysis.
APT3 |
||||||||
Step | ATT&CK Pattern |
|
||||||
2.C.1
|
Tactic Discovery (TA0007) |
|
||||||
2.C.2
|
Tactic Discovery (TA0007) |
|
||||||
3.B.1
|
Tactic Discovery (TA0007) |
|
||||||
8.B.1
|
Tactic Discovery (TA0007) |
|
||||||
12.C.1
|
Tactic Discovery (TA0007) |
|
Procedure
Empire: 'qprocess *' via PowerShell
Footnotes
- For any alert in the user interface, the telemetry behind it is separately available in the capability. This is counted as a separate detection because the functionality was shown to MITRE throughout the evaluation, though a screenshot was not taken in this instance.


[2]

