Home >
Enterprise >
Participants >
SentinelOne >
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) |
|
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 modified to use HTTP traffic to freegoogleadsenseinfo.com
Footnotes
- Telemetry showed a connection to port 80 (no detection showed HTTP specifically).
Procedure
Empire: C2 channel established using HTTPS traffic to freegoogleadsenseinfo.com
Footnotes
- Vendor stated log files indicate the powershell process was using the SSL cache folder.
- Telemetry showed an outbound network connection to 192.168.0.5 (C2 server) over TCP port 443 (no protocol was identified for this traffic).

