When traffic passes through a firewall:
A filter defines some specific pattern for which a firewall seeks a match. An exclusionary filter is one that results in traffic being blocked if a match occurs; an inclusionary filter is one that results in traffic being allowed if a match occurs.
Largely, filters and rules are two different ways of stating the same kind of information. A filter might take this form:
Block port 80
In English, this filter will block all packets destined for port 80 (the port requests for Web pages almost always comes through). If this filter were set up on your firewall, the firewall would reject any requests from users outside your system for Web pages inside your system. An equivalent rule to block port 80 might be stated as:
If port=80 then deny
The difference is a filters specifies an action for some specific value (like all traffic coming in on port 80), while rules usually apply a conditional statement that takes the form "if pattern match x, then take action y."
For many firewalls, filters or rules are set up to work together to define a general rule that established a basic filtering level, then setting exceptions to that rule to handle special cases. In this example, the first filter explicitly blocks all incoming traffic port addresses by default, then goes on only to allow use of well-known ports for FTP, SMTP, and Web services, plus the range of addresses reserved for temporary port use:
Block port all Allow port 21, 22, 25, 80, 49,152-65,535
By contrast, this filter configuration allows all traffic through by default, and blocks only Telnet and NetBIOS-related services:
Allow port all Deny port 23, 135-139
In reality, this second set of filters not a very effective security barrier since many other kinds of well-known attacks might be allowed through.
Rules and filters don't just apply to ports as in the previous examples, but can apply to a variety of different criteria that a firewall can learn about incoming traffic based on the packets of information that pass through it. For example, you could create a set of filters that allow employees to access local or Internet Web servers but that prevent users from outside the company from accessing a Web server on the company's side of the firewall.
Regardless of the size of your organization or the level of security you want to impose on your systems, firewalls are designed specifically to help you put your security policy into action. Home and small business firewalls usually have interfaces that make it very easy to configure your firewall rules and filters without much knowledge of ports, services, protocols, and the like. However, it's best if you have an IT professional configure an enterprise-level firewall, as firewalls at this level have more options and require more networking knowledge to secure your network properly.
When you start with a solid security policy that carefully balances employee needs for Internet connectivity with your organization's need for network security, you can easily find the right combination of hardware, software, and IT resources to implement that policy. Always remember that firewall configurations stem directly from business rules.
|