Tech

Explainer

Updated

What is a firewall?

Key facts

NIST's firewall guidance describes types including packet filters, stateful inspection, application firewalls, application-proxy gateways and host-based firewalls.

A firewall is a gateway that limits access between networks in accordance with local security policy, according to the NIST glossary. It sits at the junction between two networks, usually a private network and a public network such as the Internet, and it limits how far damage can spread from one part of a network to another.

Firewall types that NIST describes

The NIST guidance on firewalls, Special Publication 800-41 Revision 1 describes each type below in its own section. The table covers five of them. The same publication also covers virtual private networking, network access control, unified threat management, web application firewalls and personal firewall appliances.

TypeWhat it checksSection of SP 800-41 Rev. 1
Packet filteringEach packet against a ruleset, using its source and destination addresses, its protocol and its ports2.1.1
Stateful inspectionEach packet against a state table that records each connection2.1.2
Application firewallsHow an application's protocol is running, through stateful protocol analysis2.1.3
Application-proxy gatewaysA proxy agent that sits between two hosts and never allows a direct connection between them2.1.4
Host-based and personal firewallsThe traffic to and from one host, in software on that host2.2.1

Packet filtering is the base layer. The publication says these devices "do not keep track of the state of each flow of traffic that passes though the firewall," so they cannot tie several requests in one session to each other. Stateful inspection adds that tracking. It checks each packet against the state of its connection and blocks packets that deviate from the expected state.

What changed and when

The NIST publication page for SP 800-41 Rev. 1 lists the revision as published in September 2009, as the replacement for the earlier SP 800-41 dated 01/01/2002, and as Final. The executive summary of the publication describes the earlier pattern. It says that "At one time, most firewalls were deployed at network perimeters," which gave some protection to internal hosts, but the perimeter placement "could not recognize all instances and forms of attack."

What a reader meets next: host and network firewalls

The network firewall at the edge of a network is one kind. The publication says network firewalls "are not able to recognize all instances and forms of attack," and that attacks sent from one internal host to another may not pass through a network firewall at all. Host-based firewalls for servers and personal firewalls for desktop and laptop computers "provide an additional layer of security against network-based attacks," in software on each host they protect.

What a firewall cannot read

The publication states that "firewalls can only work effectively on traffic that they can inspect." Traffic that is encrypted is one case. Firewalls "also cannot read application data that is encrypted, such as email that is encrypted using the S/MIME or OpenPGP protocols, or files that are manually encrypted." For the basics of encryption, see what encryption is.

Have another question?