Understanding Evasions and Their Significance in the Cloud Network Firewall (CNFW) Test

Attackers are continually devising new techniques to evade detection by security tools such as firewalls. Often, attackers start with an “exploit” to take advantage of a vulnerability within a firewall. But “evasions” are far worse.  An attacker can use an evasion to disguise or manipulate malicious network traffic, enabling threats to slip past firewall defenses unnoticed. Evasions can involve altering packet structures, fragmenting data in unusual ways, or using encoding methods that standard firewall inspection processes cannot reliably detect.

In our recent Cloud Network Firewall (CNFW) test, we evaluated firewall effectiveness by assessing how well they recognize and counteract 2,500 attacks spanning 27 evasion techniques across multiple network layers. This provides a crucial measure of firewall robustness and overall security effectiveness.

For the CNFW test, CyberRatings integrates evasion scoring into a comprehensive security effectiveness metric through a detailed multiplier approach.

Security Effectiveness = Routing & Access Control × TLS/SSL Functionality × Exploits × Evasions × Stability & Reliability

Each component is scored on a scale from 0% to 100%. A low score, especially for evasions, significantly reduces the overall security effectiveness of the test.

How Firewall Evasion Impacts Your Security Posture in the CNFW Test

Our CNFW scoring starts at 100% and deducts points based on the firewall’s ability to detect evasions. Failing to detect lower-layer evasions, which are fundamental within the CNFW testing scenario, has the most significant impact.

OSI Layers and CNFW Test Impact

The OSI (Open Systems Interconnection) model provides a standardized framework for understanding data flow in network systems. Our CNFW test specifically evaluates evasion techniques across Layers 3, 4, and 7:

Layer 3 (Network Layer)

High Impact (50% per category, up to 100% total impact)

Layer 3 evasions, such as IP fragmentation and header manipulation, present the most significant risk in the CNFW test because they take place at the fundamental levels of network traffic inspection.

Common Layer 3 evasions:

  • IP fragmentation: Data packets split to evade inspection.
  • Header manipulation: Packet headers modified to bypass security.

Layer 4 (Transport Layer)

Moderate Impact (20% per category, up to 60% total impact)

In Layer 4, the CNFW test assesses evasions that manipulate packet sequencing or segmentation, challenging firewall connection monitoring.

Typical Layer 4 evasions:

  • TCP segmentation: Packet fragmentation to disrupt monitoring.
  • Sequence number manipulation: Confusing stateful inspection.

Layer 7 (Application Layer)

Lower Impact (1% per category, up to 10% total impact)

Layer 7 evasions within CNFW tests embed threats in typical web traffic, testing firewalls’ deep inspection abilities.

Examples of Layer 7 evasions:

  • Manipulated HTTP headers: Concealed malicious requests.
  • Chunked encoding: Traffic in misleading fragments.

CNFW Test Evasion Technique Scoring Breakdown

Linking CNFW Evasion Scores to Severity

The severity of evasion detection is particularly crucial in the context of our CNFW testing. An undetected evasion can create significant vulnerabilities, potentially allowing attackers unrestricted access. Therefore, firewalls that score poorly in evasion detection should be promptly reviewed, reconfigured, or replaced to maintain an optimal security posture against cyber threats.

Stateful vs. Stateless Inspection: Use Cases and Limitations

This post focuses on Stateful and Stateless Packet Inspection – their definitions, use cases, and the contexts where they may not be as effective. This insight is crucial for IT professionals, network administrators, and cybersecurity enthusiasts who want to optimize their network security strategies.

What are Stateful and Stateless Packet Inspections?

Stateless Packet Inspection

Definition: Stateless inspection, also known as static packet filtering, examines packets in isolation, without considering the state of a connection or packets that have previously passed through the firewall.

Function: It typically checks packet headers for source and destination IP addresses, port numbers, and other surface-level information, allowing or blocking them based on pre-defined rules.

Stateful Packet Inspection

Definition: Stateful inspection, in contrast, tracks the state of active connections and makes decisions based on the context of the packet within a conversation.

Function: It examines not just the packet headers but also the state of the connection, including sequence numbers and flags in TCP headers, offering a more nuanced approach to filtering.

Use Cases for Stateless Inspection

  • Basic Network Perimeter Defense: Stateless inspection is suitable for simple network environments where basic access control and packet filtering are sufficient.
  • Low-resource Environments: In scenarios where computing resources are limited, stateless inspection provides a less resource-intensive solution.
  • High-speed Networks: For networks where speed is a priority, stateless inspection offers less latency compared to stateful inspection.

Use Cases for Stateful Inspection

  • Complex Network Environments: Stateful inspection is ideal for complex environments requiring dynamic access control and in-depth traffic analysis.
  • Enhanced Security Posture: It’s beneficial for networks needing a higher level of security, capable of understanding and tracking the state of network connections.
  • Regulatory Compliance: In industries where compliance mandates sophisticated network security measures, stateful inspection is often a requirement.

Limitations and Ineffectiveness

Stateless Inspection Limitations

  • Surface-Level Filtering: Lacks the depth to understand the context or the state of connections, potentially allowing more sophisticated threats to pass through.
  • Vulnerability to Spoofing and Evasion Techniques: Due to its superficial inspection, it’s more susceptible to IP spoofing and other evasion methods.
  • Inadequate for Complex Protocols: Not suitable for protocols that require the tracking of connection states or dynamic port numbers.

Stateful Inspection Limitations

  • Resource Intensity: Can be resource-intensive, potentially slowing down network performance.
  • Complexity in Large-scale Networks: Managing and configuring stateful inspection rules in large-scale or highly dynamic environments can be challenging.
  • Struggles with Asymmetric Routing: Can face difficulties in environments where packet flows are asymmetric and not all packets of a connection pass through the same path.

Scenarios Where Stateful/Stateless May Be Overkill or Ineffective

  • Highly Encrypted Traffic: Both stateful and stateless inspections have limited visibility into encrypted traffic, reducing their effectiveness.
  • Ultra-High-Speed Networks: In environments where processing speed is critical, the added latency from stateful inspection might be a concern.
  • Static Environments with Minimal Threat Exposure: In networks with minimal exposure to external threats and low variability in traffic, advanced stateful inspection might be more than what is required.

Conclusion

Both stateful and stateless packet inspections have their place in network security, with their effectiveness depending on the specific requirements and characteristics of the network environment. Understanding these methods’ capabilities and limitations allows network security professionals to make informed decisions and optimize their security posture.

Further Reading

For a deeper dive into stateful and stateless packet inspections, consider these resources:

  • “Network Security Essentials” by William Stallings – Offers a comprehensive overview of different network security measures, including packet inspection techniques.
  • “Computer and Network Security Essentials” by Kevin Daimi and Mourad Debbabi – Provides insights into various network security technologies and methodologies.
  • “Firewalls and Internet Security: Repelling the Wily Hacker” by William R. Cheswick, Steven M. Bellovin, and Aviel D. Rubin – Includes detailed discussions on firewall technologies, including packet inspections.