MITRE D3FENDdefensive technique
D3-NTSA Network Traffic Signature Analysis
- Tactic
- Detect
Definition
Analyzing network traffic and compares it to known signatures
How it works
How it works
Network signature analysis relies on predefined patterns, or signatures, to identify malicious network activity. These signatures typically match against specific byte sequences, packet header information, or protocol anomalies indicative of known threats.
The process works as follows:
• Packet Capture: Network traffic is captured on an interface or port, resulting in a stream of raw packets.
• Preprocessing: The captured packets are preprocessed, cleaning and normalizing the data for efficient analysis.
• Signature Matching: Each packet is compared against a database of signatures using dedicated engines.
Considerations
False Negatives
Network signature analysis is susceptible to generating false negatives. These occur when malicious activity evades detection due to limitations in the signature-based approach. Here are some common causes:
• Evolving threats: Attackers frequently modify their tactics, rendering existing signatures ineffective against new variants.
• Obfuscation: Attackers may disguise malicious content using encryption, encoding, or other techniques to bypass signature detection.
• Limited visibility: Signatures rely on specific patterns. If crucial information is encrypted or hidden, the signature might miss the threat.
• Zero-day attacks: By definition, new and unknown attacks lack corresponding signatures, allowing them to pass undetected.
False Positives
Network signature analysis is susceptible to generating false positives. These occur when the signature analysis triggers an alert for benign traffic. Common causes include:
• Overly broad signatures: Rules designed to be too general might match harmless activities, generating false alarms.
• Network misconfigurations: Improperly configured devices or legitimate network activity can mimic malicious patterns, triggering false positives.
• Data errors: Corrupted or incomplete network data can lead to misinterpretations and false alerts.
Related
Counters · MITRE ATT&CK (104)
- T0895 Autorun Image technique
- T0894 System Binary Proxy Execution technique
- T1557.003 DHCP Spoofing sub-technique
- T0888 Remote System Information Discovery technique
- T0886 Remote Services technique
- T1542.005 TFTP Boot sub-technique
- T1205.001 Port Knocking sub-technique
- T0814 Denial of Service technique
- T0817 Drive-by Compromise technique
- T0819 Exploit Public-Facing Application technique
- T0822 External Remote Services technique
- T0830 Adversary-in-the-Middle technique
- T0840 Network Connection Enumeration technique
- T0842 Network Sniffing technique
- T0846 Remote System Discovery technique
- T0848 Rogue Master technique
- T0865 Spearphishing Attachment technique
- T0866 Exploitation of Remote Services technique
- T0869 Standard Application Layer Protocol technique
- T0884 Connection Proxy technique
- T0885 Commonly Used Port technique
- T1573 Encrypted Channel technique
- T1573.001 Symmetric Cryptography sub-technique
- T1573.002 Asymmetric Cryptography sub-technique
- T1048.001 Exfiltration Over Symmetric Encrypted Non-C2 Protocol sub-technique
- T1048.002 Exfiltration Over Asymmetric Encrypted Non-C2 Protocol sub-technique
- T1048.003 Exfiltration Over Unencrypted Non-C2 Protocol sub-technique
- T1071.001 Web Protocols sub-technique
- T1071.002 File Transfer Protocols sub-technique
- T1071.003 Mail Protocols sub-technique
Child of · MITRE D3FEND (1)
- D3-NTA Network Traffic Analysis defensive technique
References
- https://patentimages.storage.googleapis.com/d9/02/31/3a28fefc73661d/US20230362189A1.pdf System and method for strategic anti-malware monitoring