Un pare-feu est un appareil de sécurité réseau qui surveille et filtre le trafic réseau entrant et sortant sur la base des politiques de sécurité préalablement établies par une organisation. Dans sa forme la plus élémentaire, un pare-feu est essentiellement la barrière qui se trouve entre un réseau interne privé et l'internet public. L'objectif principal d'un pare-feu est d'autoriser le trafic non dangereux à entrer et d'empêcher le trafic dangereux de sortir.
Les pare-feu existent depuis la fin des années 1980 et ont commencé par être des filtres de paquets, qui étaient des réseaux mis en place pour examiner les paquets, ou les octets, transférés entre les ordinateurs. Bien que les pare-feu à filtrage de paquets soient encore utilisés aujourd'hui, les pare-feu ont parcouru un long chemin au fur et à mesure que la technologie s'est développée au fil des décennies.
En 1993, Gil Shwed, PDG de Check Point, a présenté le premier pare-feu à inspection dynamique, FireWall-1. Vingt-sept ans plus tard, le pare-feu reste la première ligne de défense d'une organisation contre les attaques cybernétiques. Les pare-feu actuels, y compris les pare-feu de nouvelle génération et les pare-feu de réseau, prennent en charge un large éventail de fonctions et de capacités grâce à des caractéristiques intégrées, notamment
Just like the networks they protect, firewalls have undergone a significant amount of change over the last decade. Even the earliest firewall tooling was essential to network security, as their 1980s counterparts first came into existence as packet filtering tools.
The first generation of firewalls, introduced in the late 1980s, employed simple packet filtering. These tools examined data packets at the network layer (OSI Layer 3), and filtered the packets that a network responds to through parameters such as IP addresses, ports, and protocols. However, their lack of contextual awareness and overwhelming focus on individual packets made them vulnerable to complex attacks like IP fragmentation.
The 1990s saw the advent of stateful inspection firewalls, pioneered by Check Point. These second-generation firewalls continuously monitored the state of connections, ensuring that packets were part of an established session. This enhancement significantly bolstered security.
Application layer firewalls and proxy firewalls emerged around the same time. The former operated at Layer 7, able to analyze and apply application-specific data and rulesets. They were also highly secure – boasting the ability to completely separate traffic requests from the underlying network architecture – but early models suffered from limited processing power and bad latency.
The 2010s saw the advent of UTM systems, which sought to combine a firewall’s reactivity with the extra data points from antivirus, intrusion detection, and other enterprise security systems. NGFWs were able to push these integration capabilities by adding deep packet inspection, advanced threat protection, and application-level filtering.
Today, firewalls have adapted to cloud environments and containerized applications, giving rise to Firewall-as-a-Service (FWaaS). Building upon the foundation of cross-environment data, AI and machine learning are increasingly being deployed for their superior anomaly detection, predictive threat analysis, and adaptive policy enforcement.
From static filters to intelligent, context-aware systems, firewalls have continuously evolved to meet the demands of an ever-changing threat landscape. Let’s delve into all the features that make today’s firewalls so critical.
Packet filtering is a network security technique used in firewalls to control data flow between networks. It evaluates the headers of incoming and outgoing traffic against a set of predefined rules, and then decides whether to allow or block them.
Firewall rules are precise directives that form a critical part of firewall configurations. They define the conditions under which traffic is permitted or blocked based on parameters such as source and destination IP addresses, ports, and communication protocols. In enterprise environments, these individual rules are nested together to form Access Control Lists (ACLs). When processing traffic, the firewall evaluates each packet against the ACL rules in sequential order. Once a packet matches a rule, the firewall enforces the corresponding action—such as allowing, denying, or rejecting the traffic—without further evaluation of subsequent rules. This structured and methodical approach ensures that network access is tightly controlled and consistent.
Since firewalls are happy to sit at the edge of a network, a proxy firewall is naturally well-suited to acting as a single point of entry: in doing so, they’re able to assess the validity of each connection. Proxy-service firewalls completely separate the internal and external, by terminating the client connection at the firewall, analyzing the request, and then establishing a new connection with the internal server.
Stateful packet inspection analyzes the contents of a data packet and compares them to information about packets that have already traversed the firewall.
Stateless inspection analyzes each packet in isolation: stateful inspection, on the other hand, pulls in previous device and connection data to further understand network traffic requests. This is more akin to viewing network data as a continuous stream. By maintaining a list of active connections, and evaluating each from a more macroscopic perspective, stateful firewalls are able to assign network behavior to long-term user and device profiles.
A Web Application Firewall (WAF) wraps around a specific application and examines the HTTP requests being sent to it. Similar to other types of firewall, it then applies predefined rules to detect and block malicious traffic. The components being scrutinized include headers, query strings, and the body of HTTP requests – all of which contribute to signs of malicious activity. When a threat is identified, the WAF blocks the suspicious request and notifies the security team.
Firewalls are essentially powerful analytical engines: they’re perfectly suited for the implementation of machine learning algorithms. Because ML algorithms are able to ingest and analyze far greater amounts of data far faster than their manual counterparts, AI-powered firewalls have consistently been able to outperform their older counterparts when handling novel (zero day) threats.
One of the more common implementations of AI within firewalls, for instance, is User and Endpoint Behavioural Analysis (UEBA). This ingests the historical data from entire networks, and establishes how every user and endpoint typically interacts with it – what resources they use, when they access them, etc.
A high availability (HA) firewall is designed to maintain network protection even in the event of firewall failure. This is achieved via redundancy, in the form of HA clustering: multiple firewall peers working together to deliver uninterrupted protection. In the event of device failure, the system automatically transitions to a peer device, therefore maintaining seamless network security. Above and beyond traditional ‘high availability’ designs, many organizations now need hyper scalable and telco-class resilient firewall systems to assure 99.99999%+ uptime and up to 1,000 Gbps of network throughput with full threat prevention. An intelligent load-sharing firewall design distributes network traffic across a firewall cluster. It can also automatically reallocate additional firewall resources to critical applications during unexpected peak traffic conditions or other predefined triggers, and then reassign those firewall resources back to their original group after conditions are back to normal. This optimizes performance and prevents any single device from becoming overwhelmed, and assures maximum network performance under all conditions.
Firewalls were traditionally hardware-exclusive, as they needed the heavy CPU power to manually flick through every rule in the ACL. Now, however, that processing power can essentially be outsourced thanks to firewall virtualization. Virtual systems support internal segmentation: where one tool can be used to set up and monitor multiple segmented firewalls, allowing sub-firewalls to have their own security policies and configurations.
Virtual firewalls offer many advantages: multi-tenancy environments, for instance, benefit from this segmentation. It also allows for larger organizations to implement network segmentation in a more streamlined way, through one central tool. Other than that, virtual firewalls can offer all the same capabilities as their hardware-based counterparts.
It’s common to see people conflate virtualized firewalls with cloud firewalls, but there is a distinction: whereas virtual describes the underlying architecture, cloud firewalls refer to the enterprise assets they are protecting. Cloud firewalls are those used to protect organizations’ public and private cloud-based networks.
Since cloud virtualization now allows for processing power to be purchased and used remotely, virtual firewalls are now possible. This opens up new possibilities for firewall architecture – one of which is Firewall as a Service (FWaaS).
FWaaS, like any SaaS, is a pre-built firewall solution that is deployed through the cloud. Instead of all enterprise traffic being routed and analyzed via an in-house server room, FWaaS’ unique offering is often its global Points of Presence, which allows for more local (and latency-free) firewall deployment.
Finally, it’s all well and good having a firewall – but as we’ll cover shortly, this tool needs continuous refinement and tweaking. Some enterprises find that the human demands of this can quickly overwhelm a lean cybersecurity team. So, many choose to route their traffic via a managed firewall – which is continuously monitored for threats, anomalies, or unusual traffic patterns. These outsourced firewalls can also benefit from the provider’s advanced tooling and threat intelligence.
Even basic firewalls are able to dig into the source, destination, and protocols that every packet is conforming to. But visibility alone doesn’t prevent attacks; firewall rules govern how the firewall tool reacts to each packet – ultimately either allowing it through to the enterprise network, or denying it.
These rules are fundamental to maintaining network security by controlling access to and from systems, ensuring that only authorized traffic passes through while malicious or unwanted data is blocked. To save time, most off-the-shelf firewalls offer preconfigured rulesets. After all, many threats are universal, regardless of the specifics of your industry or employees – especially when attackers are able to scan any public-facing networks for common vulnerabilities. By shipping with preconfigured rulesets, modern firewalls allow for an immediate reduction in potential threats that could hit your enterprise; a boon to deployment, allowing administrators to cut a lot of manual setup that a new tool typically demands. This reduces errors and ensures adherence to industry best practices.
Firewalls, especially Next Generation Firewalls, focus on blocking malware and application-layer attacks. Along with an integrated intrusion prevention system (IPS), these Next Generation Firewalls are able to react quickly and seamlessly to detect and combat attacks across the whole network. Firewalls can act on previously set policies to better protect your network and can carry out quick assessments to detect invasive or suspicious activity, such as malware, and shut it down. By leveraging a firewall for your security infrastructure, you’re setting up your network with specific policies to allow or block incoming and outgoing traffic.
Firewalls aren’t a set-it-and-forget-it solution. The attacks facing your organization are in constant flux, and firewalls that rely solely on manual rule updates demand just as much time and attention.
Foundational to effective firewall rule management is the principle of least privilege. It functionally means only traffic that serves a specific, necessary business function is allowed. By adhering to this principle, it’s all but guaranteed that future rule changes minimize risk, maintain greater control over network traffic, and limit unnecessary cross-network communication. Applying this to rules demands that details such as source and destination IP addresses (or ranges) and destination ports are always defined. This is why overly permissive rules like “Any/Any,” need to be replaced with an explicit deny/allow strategy for all inbound and outbound activity.
As pre-configured rules are changed and updated, clear and comprehensive documentation is essential. Anyone on the network security team should easily understand the purpose of each rule from the documentation. At a minimum, you should record details such as the purpose of the rule, the services it affects, the users and devices involved, the date it was implemented, the rule’s expiration date if temporary, and the name of the analyst who created it.
The firewall isn’t just a critical piece of enterprise safety: it’s the most public-facing piece of any network infrastructure, making unmanaged firewalls themselves a threat. To secure the firewall, a few key best practices are mandatory: insecure protocols like telnet and SNMP should be disabled entirely; configurations and log databases should be backed up; and a stealth rule should be implemented to protect the firewall from network scans. Finally, keep a regular eye on the updates available for the firewall solution.
Segmenting enterprise networks into corresponding security levels is another foundational best practice for network security, and firewall rules are perfectly well-suited for enforcing these segments. To streamline management, organize rules into categories or sections based on their function or related characteristics. This approach allows you to structure the rules in the most effective order and ensures better oversight.
AI-powered firewalls are increasingly able to automate the rules and documentation they’re based on: these massive strides in efficiency are the main reason why NGFWs are replacing their older models.
La couche réseau ou les filtres de paquets inspectent les paquets à un niveau relativement bas de la pile de protocoles TCP/IP, ne permettant pas aux paquets de passer à travers le pare-feu à moins qu'ils ne correspondent à l'ensemble de règles établi où la source et la destination de l'ensemble de règles sont basées sur les adresses et les ports du protocole Internet (IP). Les pare-feu qui effectuent une inspection de la couche réseau sont plus performants que les appareils similaires qui effectuent une inspection de la couche application. L'inconvénient est que application ou logiciel malveillant non désiré peut passer par des ports autorisés, par exemple. le trafic Internet sortant via les protocoles web HTTP et HTTPS, respectivement sur les ports 80 et 443.
Les pare-feu remplissent également des fonctions de base au niveau du réseau, telles que la traduction d'adresses de réseau (NAT) et le réseau privé virtuel (RVP). La traduction d'adresses de réseau masque ou traduit en adresses IP publiques les adresses IP internes des clients ou des serveurs qui peuvent se trouver dans une "plage d'adresses privées", telle que définie dans la RFC 1918. Le masquage des adresses de l'appareil protégé préserve le nombre limité d'adresses IPv4 et constitue une défense contre la reconnaissance du réseau puisque l'adresse IP est cachée de l'internet.
De même, un réseau privé virtuel (RVP) étend un réseau privé sur un réseau public à l'intérieur d'un tunnel souvent crypté où le contenu des paquets est protégé lorsqu'ils traversent l'internet. Cela permet aux utilisateurs d'envoyer et de recevoir des données en toute sécurité sur un réseau partagé ou public.
Les Pare-feu de nouvelle génération inspectent les paquets au niveau de l'application de la pile TCP/IP et sont capables d'identifier des applications telles que Skype ou Facebook et d'appliquer une politique de sécurité basée sur le type d'application.
Aujourd'hui, les appareils UTM (Unified Threat Management) et Pare-feu de nouvelle génération intègrent également des technologies de prévention des menaces telles que le Système de prévention des intrusions (IPS) ou l'Antivirus pour détecter et prévenir les logiciels malveillants et les menaces. Ces appareils peuvent également inclure des technologies de sandboxing pour détecter les menaces dans les fichiers.
As the cyber security landscape continues to evolve and attacks become more sophisticated, Next Generation Firewalls will continue to be an essential component of any organization’s security solution, whether you’re in the data center, network, or cloud.
Protect your network using Check Point’s Quantum NGFW – the most effective AI-powered firewalls, featuring the highest rated threat prevention, seamless scalability, and unified policy management.
Combining cutting-edge threat prevention, unparalleled performance, and streamlined efficiency, Check Point Quantum’s advanced capabilities include intelligent traffic inspection, seamless integration with cloud services, and in-depth incident automation. See for yourself how Quantum boasts effortless scalability and centralized policy management with a demo.
To learn more about the essential capabilities your Next Generation Firewall needs to have, download the Next Generation Firewall (NGFW) Buyer’s Guide today.