# US 2006/0085849 A1 · Firewall with stateful inspection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0085849 A1
- Document ID: US20060085849A1
- Status: Published application
- Kind: A1
- Application number: 10/512,950
- Filed: 2003-05-01
- Published: 2006-04-20
- Earliest claimed: 2002-05-01
- Assignees: Firebridge Systems Pty Ltd.
- Inventors: Patrick Culbert
- Web page: https://patentgrep.com/patent/US20060085849A1

## CPC

- H04L 63/0254: {Stateful filtering}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A network security device for controlling the flow of packets into and out of an internal network 60, includes first and second network cards 80 and 120 and a stateful inspection firewall. The first network card 80 forwards each packet for inspection 90 to determine whether or not the packet is part of an existing session. If the packet is part of an existing session it will be forwarded to the second network card 120 and on to the internal network 60. If the packet is not part of an existing session it will be compared with a set of rules to determine whether the packet is acceptable or not acceptable to the network. If the packet is acceptable, it will be forwarded to the second network card 120 and to the internal network and the session is entered into the stateful inspection table, and if the packet is not acceptable it will be dropped and will disappear. During the outflow of packets an outbound packet passes through the second network card where it is inspected to determine whether or not it is part of an existing session and, if so, it is forwarded to the first network card to exit the device, and, if not, it is compared with the set of rules and if the packet is acceptable it is forwarded to the first network card to exit the device and, if not, it is dropped and disappears.

## Claims

### Claim 1

A stateful inspection bridging network security device for controlling the flow of packets into and out of an internal network, via a data link layer said device including first and second network cards and a stateful inspection firewall and wherein during inflow of packets the first network card forwards each packet to the firewall for inspection to determine whether or not the packet is part of an existing session and wherein:
(i) if the packet is part of an existing session it will be forwarded via the data link layer to the second network card and on to the internal network, and
(ii) if the packet is not part of an existing session it will be compared with a set of rules which determine whether the packet is acceptable or not acceptable to the network and wherein:
(a) if the packet is acceptable it will be forwarded via the data link layer to the second network card and to the internal network, and the session is entered into the stateful inspection table,
(b) if the packet is not acceptable it will be dropped and will disappear,
and wherein during the outflow of packets an outbound packet passes through the second network card where it is inspected to determine whether or not it is part of an existing session and, if so, it is forwarded to the first network card to exit the device, and, if not, it is compared with the set of rules and if the packet is acceptable it is forwarded via the data link layer to the first network card to exit the device and, if not, it is dropped and disappears.

### Claim 2 (depends on 1)

A device according to claim 1 wherein the first and second network cards do not have publicly routed IP addresses.

### Claim 3 (depends on 1)

A device according to claim 1 and further including a third network card which is a management interface having a private, not publicly routed IP address which is used to configure the firewall.

### Claim 4 (depends on 1)

The device of claim 1 wherein the device is adapted to be located between a router and a hub or server machine.

### Claim 5 (depends on 1)

The device of claim 1 wherein the device does not require a separate computer to implement.

### Claim 6 (depends on 1)

The device of claim 1 wherein the device is configurable from an HTML interface.

### Claim 7 (depends on 1)

The device of claim 1 wherein the device is configured with an HTML interface which is supplied with the device.

### Claim 8 (depends on 1)

The device of claim 1 further comprising a LOAD monitor which provides LOAD status, and for providing a graphic notification to a user of what the current load on the CPU is.

### Claim 9 (depends on 1)

The device of claim 1 further comprising a CONFIGURATION status monitor, which provides for a graphic notification to a user of whether or not the changes they have made to the configuration of the firewall have been committed to the firewall.

### Claim 10 (depends on 1)

The device of claim 1 further comprising a monitor and log which provides for a graphic indication of whether or not packets have been allowed or denied.

### Claim 11 (depends on 1)

The device of claim 1 further comprising:
an HTML interface for configuration such that it can be configured from any computer to which it is networked that has an HTML browser without installing any additional software.

### Claim 12 (depends on 1)

The device of claim 1 wherein:
the first and second network cards do not have or require an IP address assigned to them.
