Network Firewalls

A firewall is a piece of hardware or software which functions in a networked environment to prevent some communications forbidden by the network policy, analagous to the function of firewalls in building construction. It has the basic task of controlling traffic between different zones of trust. Typical zones of trust include the Internet ( a zone with no trust ) and an internal network ( a zone with high trust ). The ultimate goal is to prevent intrusion from a connected network device into other networked devices.

Network security analysts distinguish between:

• a personal firewall, a software application which normally filters traffic entering or leaving a single computer; and:
• a traditional firewall, normally running on a dedicated network device or computer positioned on the boundary of two or more networks or DMZs (demilitarized zones). Such a firewall filters all traffic entering or leaving the connected networks.

The latter definition corresponds to the conventional meaning of "firewall" in networking, and the remainder of this article addresses this type of firewall. Two main categories of such firewalls exist:

• network layer firewalls
• application layer firewalls.

These two types of firewall may overlap; indeed, single systems have implemented both together.

Contents [showhide]

1 Types of firewalls   1.1 Network layer firewalls 1.2 Application-layer firewalls   2 See also   3 External links

Types of firewalls

Network layer firewalls

Network layer firewalls operate at a (relatively low) level of the TCP/IP protocol stack as IP-packet filters, not allowing packets to pass through the firewall unless they match the rules. The firewall administrator may define the rules; or default built-in rules may apply (as in some inflexible firewall systems). A more permissive setup could allow any packet to pass the filter as long as it does not match one or more "negative-rules", or "deny rules". Today network firewalls are built into most computer operating system and network appliances.

Application-layer firewalls

Application-layer firewalls work on the application level of the TCP/IP stack (i.e., all browser traffic, or all telnet or ftp traffic), and may intercept all packets traveling to or from an application. They block other packets (usually dropping them without acknowledgement to the sender). In principle, application firewalls can prevent all unwanted outside traffic from reaching protected machines. By inspecting all packets for improper content, firewalls can even prevent the spread of the likes of viruses. In practice, however, this becomes so complex and so difficult to attempt (given the variety of applications and the diversity of content each may allow in its packet traffic) that comprehensive firewall design does not generally attempt this approach. The XML Firewall exemplifies a more recent kind of application-layer firewall.

A proxy device (running either on dedicated hardware or as software on a general-purpose machine) may act as a firewall by responding to input packets (connection requests, for example) in the manner of an application, whilst blocking other packets.

Proxies make tampering with an internal system from the external network more difficult, and misuse of one internal system would not necessarily cause a security breach exploitable from outside the firewall (as long as the application proxy remains intact and properly configured). Conversely, intruders may hijack a publicly-reachable system and use it as a proxy for their own purposes; the proxy then masquerades as that system to other internal machines. While use of internal address spaces enhances security, crackers may still employ methods such as IP spoofing to attempt to pass packets to a target network.

Firewalls often have network address translation (NAT) functionality, and the hosts protected behind a firewall commonly use so-called "private address space", as defined in RFC 1918. Administrators often set up such scenarios in an effort (of debatable effectiveness) to disguise the internal address or network.

Proper configuration of firewalls demands skill. It requires considerable understanding of network protocols and of computer security. Small mistakes can render a firewall worthless as a security tool.

See also

• Stateful firewall
• Stateless firewall
• End-to-end connectivity
• Netfilter
• Bastion Host
• Application level Gateway
• DMZ

External links

• Matt Curtin and Marcus J. Ranum Internet Firewalls: Frequently Asked Questions (http://www.faqs.org/faqs/firewalls-faq/)
• Home PC Firewall Guide - includes info on free firewalls (http://www.firewallguide.com/)
• ShieldsUp (https://www.grc.com/x/ne.dll?bh0bkyd2) - a web service which can evaluate some aspects of firewall effectiveness
• What is a Firewall (http://www.pcreview.co.uk/article-7388.php) - a guide to computing firewalls, with links to current downloads.
• Choosing a Firewall (http://www.windowsnetworking.com/articles_tutorials/Choosing_a_Firewall.html) - Take a look at some of the factors you should consider when buying a firewall.
• Personal Firewall (http://www.windowsnetworking.com/articles_tutorials/firewall.html) - How to set up your own personal firewall.
• Firewall White papers (http://www.xtradyne.com/products/resources.htm) - White papers on Web Services XML/SOAP and CORBA IIOP firewall security.