312-50 ยท Evading IDS, firewalls and honeypots
Evading an IDS
Fragmentation, obfuscation and encoding, session splicing, encryption/tunnelling, polymorphic shellcode, false positive flooding.
Key points
- Goal: traffic looks different to the sensor than to the target.
- Fragmentation: splits a pattern across pieces.
- Session splicing: payload over many tiny TCP segments.
- Obfuscation, encoding: Unicode, URL encoding.
- Tunnelling or encryption the sensor cannot read; polymorphic shellcode.
- Flooding: noise buries real alerts.
- Defenders: reassembly, normalisation, decryption points, tuning.
Practice questions
Why does splitting an attack string across several small IP fragments sometimes help evade a weak IDS?
- The signature is split so no single piece matches
- Fragments are encrypted automatically
- Fragments change the target's IP address
- Fragments disable the sensor's logging
Show answer
Answer: A. The signature is split so no single piece matches
If the sensor inspects fragments individually and does not reassemble them, the signature never appears whole. The fragments are still reassembled by the target.
Which of these are IDS evasion techniques?
- Session splicing
- Polymorphic shellcode
- Fragment reassembly on the sensor
- Patching the target
- Payload obfuscation and encoding
Show answer
Answer: A. Session splicing, B. Polymorphic shellcode, E. Payload obfuscation and encoding
Session splicing, polymorphic shellcode and fragmentation all alter what the sensor sees. Patching the target and enabling reassembly are defences.
Flooding an IDS with harmless-looking noisy traffic can hide a real attack among the resulting false-positive alerts.
Show answer
Answer: True
True. The goal is to overwhelm analysts and the sensor so that the real event is missed.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
