T1205 Traffic Signaling Mappings

Adversaries may use traffic signaling to hide open ports or other malicious functionality used for persistence or command and control. Traffic signaling involves the use of a magic value or sequence that must be sent to a system to trigger a special response, such as opening a closed port or executing a malicious task. This may take the form of sending a series of packets with certain characteristics before a port will be opened that the adversary can use for command and control. Usually this series of packets consists of attempted connections to a predefined sequence of closed ports (i.e. Port Knocking), but can involve unusual flags, specific strings, or other unique characteristics. After the sequence is completed, opening a port may be accomplished by the host-based firewall, but could also be implemented by custom software.

Adversaries may also communicate with an already open port, but the service listening on that port will only respond to commands or trigger other malicious functionality if passed the appropriate magic value(s).

The observation of the signal packets to trigger the communication can be conducted through different methods. One means, originally implemented by Cd00r (Citation: Hartrell cd00r 2002), is to use the libpcap libraries to sniff for the packets in question. Another method leverages raw sockets, which enables the malware to use ports that are already open for use by other programs.

On network devices, adversaries may use crafted packets to enable Network Device Authentication for standard services offered by the device such as telnet. Such signaling may also be used to open a closed service port such as telnet, or to trigger module modification of malware implants on the device, adding, removing, or changing malicious capabilities.(Citation: Cisco Synful Knock Evolution) (Citation: FireEye - Synful Knock) (Citation: Cisco Blog Legacy Device Attacks) To enable this traffic signaling on embedded devices, adversaries must first achieve and leverage Patch System Image due to the monolithic nature of the architecture.



Capability ID Capability Description Mapping Type ATT&CK ID ATT&CK Name
AC-3 Access Enforcement Protects T1205 Traffic Signaling
AC-4 Information Flow Enforcement Protects T1205 Traffic Signaling
CA-7 Continuous Monitoring Protects T1205 Traffic Signaling
CM-6 Configuration Settings Protects T1205 Traffic Signaling
CM-7 Least Functionality Protects T1205 Traffic Signaling
SC-7 Boundary Protection Protects T1205 Traffic Signaling
SI-15 Information Output Filtering Protects T1205 Traffic Signaling
SI-4 System Monitoring Protects T1205 Traffic Signaling
network_security_groups Network Security Groups technique_scores T1205 Traffic Signaling
azure_firewall Azure Firewall technique_scores T1205 Traffic Signaling

ATT&CK Subtechniques

Technique ID Technique Name Number of Mappings
T1205.001 Port Knocking 10