Network Fingerprinting: Analyzing Default ICMP Structures and Payload Mimicry
Research Context
"In advanced network observability, understanding the default behavior of various operating systems is vital for traffic profiling. This article explores the structural differences in ICMP Echo Requests across different OS environments and analyzes how 'Traffic Mimicry' can be used to evaluate the accuracy of Network Intrusion Detection Systems (NIDS)."
"In advanced network observability, understanding the default behavior of various operating systems is vital for traffic profiling. This article explores the structural differences in ICMP Echo Requests across different OS environments and analyzes how 'Traffic Mimicry' can be used to evaluate the accuracy of Network Intrusion Detection Systems (NIDS)."
1. The Anatomy of an ICMP Signature
A standard ICMP Echo Request is not just a simple signal; it carries a specific "fingerprint" based on the operating system that generated it. These fingerprints consist of:
Total Packet Size
TTL (Time to Live) values
Default Payload Content
2. Cross-Platform Discrepancies (Linux vs. Windows)
When a system sends a "ping," the default data size ($D$) and the total packet length ($L$) vary significantly between architectures.
| Feature | Linux (Typical) | Windows (Typical) |
|---|---|---|
| Data Size ($D$) | 56 Bytes | 32 Bytes |
| ICMP Header ($H$) | 8 Bytes | 8 Bytes |
| Total ICMP Length ($L$) | 64 Bytes | 40 Bytes |
| Default Payload | Timestamp + Data | abcdefg... |