Home >
Enterprise >
Participants >
CrowdStrike >
Application Layer Protocol (T1071)
|
|
Carbanak+FIN7 |
||||
Step | ATT&CK Pattern |
|
||
1.A.10
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||
7.A.3
|
Tactic Command and Control (TA0011) |
|
||
8.A.2
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||
12.A.3
|
Tactic Command and Control (TA0011) |
|
||
14.A.6
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||
16.A.8
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||
17.A.5
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||
20.A.3
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
APT29 |
||||
Step | ATT&CK Pattern |
|
||
3.B.4
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||
11.A.14
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
Procedure
Used HTTPS to transport C2 (192.168.0.5) traffic
Criteria
Evidence that the network data sent over the C2 channel is HTTPS
APT3 |
||||||||||
Step | ATT&CK Pattern |
|
||||||||
1.C.1.2
|
|
|||||||||
6.B.1.2
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||||||||
11.B.1.2
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
||||||||
14.A.1.3
|
Tactic Command and Control (TA0011) Subtechnique Application Layer Protocol: Web Protocols (T1071.001) |
|
Procedure
Cobalt Strike: C2 channel established using DNS traffic to freegoogleadsenseinfo.com
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]


[3]

