Method and apparatus for optimizing firewall processing

[00002] 1. Field of the Invention

[00003] This invention pertains generally to firewall systems. More particularly, the invention is a firewall system and method which optimizes the performance of the firewall process by reducing overhead associated with ACL verification and firewall application-level authorization.

[00004] 2. The Prior Art

[00005] Firewalls are known in the art. In general, a firewall is a combination of hardware and software which limits the exposure of a computer or group of computers to an attack from outside. The most common use of a firewall is on a local area network (LAN) connected to the global information network, known as the Internet. Without a firewall, anyone on the Internet could theoretically connect to the corporate LAN and retrieve and/or transmit information to computers on the LAN. A firewall provides services which enforce a boundary between two or more networks. In the above example, a firewall would enforce a boundary between the LAN and the Internet.

[00006] A traditional firewall is implemented through a combination of hosts and routers. A router can control traffic at the packet level, allowing or denying packets based on the source/destination address or the source/destination port number. A host (or application gateway), on the other hand, can control traffic at the application level, allowing control based on a more detailed and protocol-dependent examination of the traffic. Often, a router can be configured to provide firewall capability.

[00007] FIG. 1 depicts a block diagram of a firewall (or router with firewall capbilities) device 10 according to the prior art. Firewall 10 is shown having interface 1 (designated as 12a) and interface 2 (designated as 12b), interface 1 (12a) connected to a network 1 (14a) and interface 2 (12b) connected to network 2 (14b). As a data packet is communicated from network 1 (14a) to network 2 (14b) or from network 2 (14b) to network 1 (14a), the data is intercepted and is authorized or denied data communication based on a plurality of configuration settings as is well known in the art.

[00008] The firewall device 10 includes a plurality of services to carry out the operation of authorizing data traffic through the device 10. More particularly, the firewall device 10 includes a switching process component (or router) 16, a packet filtering component 18, and a firewall services component 20. Switching process 16 handles traffic connections associated with interfaces 12a, 12b, and routes data according to designated addresses.

[00009] The packet filtering component 18 filters data packets based on a set of rules defined in an associated Access Control List, designated ACL 22. The ACL 22 contains static as well as dynamic settings. Static settings are normally provided by a user in a configuration file. For example, the ACL 22 may define a set of IP (Internet Protocol) addresses that are permitted to communicate through firewall device 10. Dynamic settings are normally provided by the firewall services to enable certain communications, including return acknowledgement signals, for example.

[00010] The firewall services 20 provide authentication on an application level, providing among other things, protocol dependent inspection and authentication. As noted above, the firewall service 20 also configures the ACL 22 to allow certain communications to pass through the device 10.

[00011] The following example illustrates the operation of a prior art firewall device. FIG. 2 shows the structure of a typical data packet 28 transmitted through the firewall device. As is known, the data packet 28 will include a header portion 30, and a data payload component 32. The header portion 30 includes among other things, address information (such as the destination address, for example).

[00012] The data payload component 32 includes additional information such as User ID and protocol information, among other things.

[00013] When a data packet is communicated from network 14a to network 14b, for example, the data packet enters interface 12a from network 14a. The packet filtering component 18 intercepts the data packet at point 24 and determines whether the data packet is authorized to enter the router 10 via the interface 12a based on the set of rules defined in the ACL 22. Typically, the header is inspected to determine source and/or destination address information. If so authorized, the data packet is communicated back to point 24 and to the switching process 16 for routing to the appropriate interface.

[00014] The switching process 16 receives the data packet and “diverts” the data packet to the firewall services 20 for inspection and authorization. As noted above, the firewall services component 20 authenticates the data packet based on a set of protocol-dependent rules. In this way, the payload component 32 of the data packet is typically inspected to see if communication is authorized. If so authorized by the firewall services 20, the data packet is sent back to the switching process 16, which then communicates the data packet to the interface 12b via point 26. As noted above, the firewall services component 20 may also configure one or more settings within the ACL 22 to allow certain communications (return acknowledgments, for example) to pass through the router 10.

[00015] At point 26, the data packet communicated by the switching process 16 is again intercepted by the packet filtering component 18 to determine whether the data packet is authorized to exit interface 12b based of the set of rules defined in the ACL 22. If so authorized, the switching process 16 transmits the data packet to the interface 12b, via point 26, which then communicates the data packet to network 14b where the packet is further processed.

[00016] As described above, the prior art method of firewall processing involves a plurality of security authorization steps. For each data packet that is communicated through the firewall device, the authorization steps described above are carried out. In the above example firewall 10 having 2 ports 14a, 14b, two ACL authentication processes are carried out by the packet filtering component 18, one for each port. Additionally, the switching process 16 diverts the packet to the firewall services 20 for application-level authentication.

[00017] While providing security, there are performance penalties associated with the above described authorization processes for a firewall. For example, because the switching process 16 operates in a different address space from the firewall services component 20, the router device 10 suffers the overhead associated with “context switching” when a data packet is “diverted” from the switching process 16 to the firewall services 20 for inspection and authorization.

[00018] Prior art firewalls “divert” each data packet handled by switching process 16. However, since data communication transactions often involve the transfer of a plurality of data packets (rather than a single packet), the need for authorizing (and therefore diverting) each and every packet may be unnecessary, once the first in a series of associated data packets has been authorized. This is particularly evident in a data transfer, as opposed to a control transfer.

[00019] For example, an FTP transfer of a file may involve the transfer or a plurality of packets. If the first packet is authorized between a source and a destination, then the remaining associated packets would also be authorized. However, under present firewall solutions, each of the remaining packets would be diverted and authorized, and thus the overhead associated with context-switching is realized for each of the associated packets for the duration of the file transfer.

[00020] Also as noted above, the packet filtering component 18 carries out authorization based on the rules provided in the corresponding ACL 22. This authorization is carried out for each packet processed by the packet filtering component 18. As noted above, the packet is checked upon entering a port and upon exiting a port, thus incurring additional performance penalties.

[00021] Accordingly, there is a need for a method and apparatus which provides firewall security processing which minimizes the overhead with context switching and optimizes overall firewall performance. The present invention satisfies these needs, as well as others, and generally overcomes the deficiencies found in the background art.

[00022] The present invention is a system and method for optimizing firewall performance, which reduces the overhead associated with firewall protocol inspection and packet filtering authorization. The invention further relates to machine readable media on which are stored embodiments of the present invention. It is contemplated that any media suitable for retrieving instructions is within the scope of the present invention. By way of example, such media may take the form of magnetic, optical, or semiconductor media. The invention also relates to data structures that contain embodiments of the present invention, and to the transmission of data structures containing embodiments of the present invention.

[00023] The present system operates in a conventional firewall (or router having firewall capabilities) device having conventional hardware components, such as a central processor unit (CPU), memory, and input/output devices. The firewall device will typically further include a plurality of communication interfaces (interfaces), such as Ethernet ports and/or serial ports, for example. As such, the firewall device inspects and authenticates communication carried out between the various ports of the firewall device.

[00024] According to one embodiment of the present invention, the firewall system operates in a firewall device having a plurality of communication interfaces, a packet filtering component coupled to each of the interfaces, a switching component coupled to each of the interfaces, and a firewall services component coupled to the switching process. The firewall system comprises a session manager operating in the firewall services component. The session manager is structured and configured to instantiate a plurality of sessions in the firewall services component and a plurality of mini-sessions in the switching process component. Each of the sessions has context information captured from the header and payload information of packets of the session. Each of the mini-sessions corresponds to a session and includes header information related the corresponding data transfer within the firewall device. The mini-sessions are managed by a firewall module (or mini-session manager) residing and operating in the switching process/component. This firewall module is initiated by the session manager component and is configured to maintain data in the mini-sessions. The firewall module further determines whether to send packets from the switching process to the firewall process based on the data in the mini-sessions.

[00025] According to another embodiment of the present invention, the method for optimizing firewall processing comprises providing a session manager in the firewall services component, providing a firewall module in the switching process/component, instantiating a session, by the session manager, for data transfers within the firewall device, the sessions having header and payload information related to data transfers within the firewall device, and instantiating a mini-session, by the session manager, corresponding to the instantiated session, the mini-session having header information related to data transfers within the firewall device.

[00026] An object of the invention is to provide a firewall system and method for optimizing firewall processing that overcomes the deficiencies in the prior art.

[00027] Another object of the invention is to provide a firewall system and method for optimizing firewall processing that reduces the overhead associated with context-switching in firewall authentication.

[00028] Yet another object of the invention is to provide a firewall system and method for optimizing firewall processing that reduces the overhead associated with access control list authentication.

[00029] Further objects and advantages of the invention will be brought out in the following portions of the specification, wherein the detailed description is for the purpose of fully disclosing the preferred embodiment of the invention without placing limitations thereon.

[00038] Persons of ordinary skill in the art will realize that the following description of the present invention is illustrative only and not in any way limiting. Other embodiments of the invention will readily suggest themselves to such skilled persons having the benefit of this disclosure.

[00039] Referring more specifically to the drawings, for illustrative purposes the present invention is embodied in the apparatus shown FIG. 3 and FIG. 4 and the method outlined in FIG. 5a through FIG. 7. It will be appreciated that the apparatus may vary as to configuration and as to details of the parts, and that the method may vary as to details and the order of the acts, without departing from the basic concepts as disclosed herein. The invention is disclosed generally in terms of a firewall system and method, although numerous other uses for the invention will suggest themselves to persons of ordinary skill in the art.

[00040] Referring now to FIG. 3, there is generally shown a block diagram depicting a firewall system in accordance with the present invention. The present system operates in a conventional firewall or router device 40 having conventional hardware components (not shown), such as a central processor unit (CPU), memory, and input/output devices. The firewall device will typically further include a plurality of communication interfaces (interfaces) 42a, 42b, which may be Ethernet ports and/or serial ports, for example. Interface 42a is operatively coupled for communication with a first network designated 44a, and interface 42b is operatively coupled for communication with a second network designated 44b. Network 44a, 44b comprise convention networks, such a local area network (LAN), wide area network (WAN), and/or the Internet, for example. Under this arrangement, the firewall device carries out the operation of inspecting and authenticating communication carried out between the various ports 42a, 42b of the firewall device.

[00041] The firewall system of the present invention is generally embodied in software executing and operating in the firewall 40 and carries out the operation described herein. The firewall system generally includes a packet filtering component 46, a switching process component 48, and a firewall services component 50.

[00042] The packet filtering component 46 is a software module coupled for communication to the interfaces 42a, 42b of the firewall device 40. The packet filtering component 46 inspects packets entering and exiting the communication interfaces 42a, 42b to determine whether transfer is authorized according to certain port and address settings maintained in an “Access Control List” (ACL 52). The packet filtering component 46 of the present invention, however, does not perform ACL verification for each packet processed through a port as is carried out in prior art firewall system. Rather, the packet filtering component 46 first checks the data packet for a “pass” flag which may be set by the firewall system. If the “pass” flag is set, the packet filtering component 46 bypasses ACL verification. If the “pass” flag is not set, ACL verification is carried out conventionally. This process is described more fully below in conjunction with FIG. 5a and FIG. 5b.

[00043] The switching process component 48 is a software module coupled for communication to the interfaces 42a, 42b of the firewall device. The switching process component routes packets between the interfaces 42a, 42b of the firewall device, according to address and port information, as is known in the art.

[00044] The switching process further comprises a “firewall module” (or mini-session manager), designated FWM 57. The FWM 57 is a software module operating in the same memory space as switching process 48 which performs session tracking operations, including “non-application-level” inspection of data packets, and “diverting” data packets to the firewall services 50 for inspection and authorization thereof when appropriate as described in further detail in conjunction with FIG. 7 below. The FWM 57 is initiated during the startup of the device 40 by the firewall services 50.

[00045] The FWM 57 is coupled to one or more “mini-sessions” (generally designated as 58) which are described in more detail below in conjunction with FIG. 5a through FIG. 7. The “mini-sessions” are instantiated software modules residing in the same address space as the switching process component 48 which contain session information data used by the FWM 57 for processing data packets.

[00046] The firewall services component 50 is a software module coupled for communication to the switching process component 48 which inspects and authorizes packets according to information in the payload component of the packet, the process of which is known in the art.

[00047] According to the present invention, once a data packet from a first address is authorized for transfer to a second address, the firewall system authorizes “future” data transfers between the first and second addresses to complete the data transfer so authorized. In this way, the system provides a means for authorizing such “future” data transfers without ACL authorization and firewall “application-level” authorization in order to complete the data transfer transaction. To this end, the firewall system of the present invention provides a session manager 54 operating within the firewall services component 50. The session manager 54 is configured to create, manage and delete a plurality of sessions 56 in the firewall services and a plurality of “mini-sessions” 58 in the switching process component 48.

[00048] In general, when the firewall services 50 encounters a data packet (an FTP data transfer, for example), as opposed to a control packet (a login command, for UL example), for transfer within the firewall 40, the session manager 54 instantiates a corresponding session 56, for storing among other things, header data (addresses and port information, for example) as well as payload data (user id and communication protocol, for example) to track the data transfer. This instantiated session 56 is maintained in the firewall services 50 by the session manager 54 until the data transfer is either completed or exceeds a predetermined timeout (a period of time during which no corresponding data transfer is carried out). The session manager 54 further instantiates a corresponding “mini-session” 58 in the switching process 48 which contains, among other things, corresponding header data used by the FWM 57. In this manner, for each session 56 maintained by the session manager 54, there is a corresponding mini-session 58 in the switching process 48.

[00049] The processes of the FWM 57 in conjunction with the mini-sessions 58 are described further below in conjunction with FIG. 6. In general, the FWM 57 is configured to intercept data packets entering the interfaces 42a, 42b of the firewall 40, preferably before the packet filtering component 46 intercepts the packet for ACL verification. The FWM 57 then compares the data in the header component of the intercepted packet to corresponding data in each mini-session 58 to determine whether the packet is authorized to pass without authorization. A packet is authorized when a source and destination address and port number specified in the header matches corresponding source and destination address port number in one of the mini-sessions. If so, the FWM 57 sets a “pass” flag in the packet to communicate that ACL verification is to be bypassed and a “do not divert” flag to communicate that firewall “application” level authorization is to be bypassed.

[00050] The FWM 57 is also configured to update the connection state “in-place” (i.e., without sending the packets to the firewall process). This ability is particularly important to reduce the overhead involving context switching between different processes, i.e., the switching process and the firewall services component process. Without this “in-place” inspection, all packets would have to be sent to an external process (e.g., the firewall services 50), causing additional overhead and latency. The scope of this invention does not limit the capability of the mini-session manager just to a subset of the connections or sessions. While the illustrative FWM 57 in FIG. 3 performs non-application-level inspection, it is possible to create a firewall module that has the ability to perform application-level inspection and therefore eliminate the need to transfer packets to an external process once the inspection of a new connection begins. However, to provide speed at the switching process 48 level, the FWM 57 described in FIG. 3 is configured to carry out non-application-level inspection.

[00051] FIG. 4 depicts an example data structure for a data packet 64 where flag bits may be set in slot 66 by the FWM 57 to define the “pass” state and the “do not divert” state as described above. For example, slot 66 may comprise two bits, the first bit (“pass” bit) for defining “pass” state and the second bit (“do not divert” bit) for defining the “do not divert” state. While depicted as the first slot of the data structure 64, the communication of a “pass” flag and “do not pass” flag may be carried out using various other slot arrangements as is known in the art.

[00052] Once a data transfer is completed, the associated session 56 and mini-session 58 is deleted. In general, the FWM 57 monitors communications between the interfaces 42a, 42b for signals indicating a completed transfer as is known in the art. Once this signal is so detected, a “delete” request is sent to the session manager 54 by the FWM 57. In response, to the “delete” request, the session manager 54 deletes corresponding session 56 and mini-session 58. Sessions 56 and corresponding mini-sessions 58 are also deleted if the data transfer associated therewith is idle (not communicating) for a predetermined period of time (“timeout” period).

[00053] The method and operation of invention will be more fully understood with reference to the flow charts of FIG. 5a through FIG. 7, as well as FIG. 3 and FIG. 4. The order of actions as shown in FIG. 5a through FIG. 7 and described below is only exemplary, and should not be considered limiting.

[00054] Referring next to FIG. 5a and FIG. 5b, as well as FIG. 2 through FIG. 4, there is generally shown the acts associated with the firewall system processes of the present invention. FIG. 5a and FIG. 5b depict the example situation where a data packet is communicated from Network 1 to Network 2. An analogous series of acts are carried out for data packets communicated from Network 2 to Network 1.

[00055] At box 100, Interface 42a receives a data packet from Network 1 for communication to Network 2. The data packet will typically be structured as packet 28 (FIG. 2) having a header component and a payload component. In general, the header component includes source and destination address information as well as port information. Box 110 is then carried out.

[00056] At box 110, the FWM 57 operating in the switching process 48 ascertains whether there are any active mini-sessions 58 operating therein. As described above, mini-deleted sessions 58 are instantiated and deleted during operation of the firewall device 40. If there are active mini-sessions 58, box 120 is carried out. Otherwise, box 130 is carried out.

[00057] At box 120, the FWM 57 processing sequence is carried out. This sequence is described in more detail in conjunction with FIG. 6 below. After the FWM 57 processing sequence is completed, box 130 is then carried out.

[00058] At box 130, the packet filtering component (PFC) 46 intercepts the packet at point 60 before the switching process 48 carries out routing tasks (described in box 180 below). Box 140 is then carried out.

[00059] At box 140, the PFC 46 inspects the intercepted data packet to determine whether a “pass” flag is set. In this way, the PFC 46 checks a predetermined slot in the data structure. For example, in FIG. 4, flag slot 66 may contain a “1” bit in the appropriate bit location (i.e., the “pass” bit) to indicate a “pass”. Diamond 150 is then carried out.

[00060] At diamond 150, the PFC 46 determines whether the “pass” flag is set in the intercepted data packet. If the “pass” flag is set, box 170 is then carried out to bypass the ACL verification. Otherwise, box 160 is carried out.

[00061] At box 160, the PFC 46 authenticates the packet entering interface 42a according to the settings provided in the ACL 52 as is known in the art. This typically involves comparing the header of the packet to corresponding settings in the ACL 52. Packets which are authorized are further processed, while unauthorized packets are dropped. Box 170 is then carried out.

[00062] At box 170, the PFC 46 returns the packet for processing by the switching component 48. Box 180 is then carried out.

[00063] At box 180, the switching process 48 sequence is carried out. In general, this sequence includes, among other things, routing the packet to the appropriate interface as well as verifying the packet with the firewall services component 50 when appropriate. This sequence is described more fully below in conjunction with FIG. 7. Box 190 is then carried out.

[00064] At box 190, the switching process 48 routes the packet to the appropriate interface, which in the present example is interface 42 (for communication to Network 44b). Box 200 is then carried out.

[00065] At box 200, the packet filtering component (PFC) 46 intercepts the packet at point 62 before the packet is received by interface 42b. Box 210 is then carried out.

[00066] At box 210, the PFC 46 inspects the intercepted data packet to determine whether a “pass” flag is set. As described above in box 140, the PFC 46 check a predetermined slot in the data structure. Diamond 220 is then carried out.

[00067] At diamond 220, the PFC 46 determines whether the “pass” flag is set in the intercepted data packet. If the “pass” flag is set, box 240 is then carried out to bypass ACL verification. Otherwise, box 230 is carried out.

[00068] At box 230, the PFC 46 authenticates the packet exiting via interface 42b according to the settings provided in the ACL 52. As noted above, ACL verification typically involves comparing the header of the packet to corresponding settings in the ACL 52. Packets which are authorized are further processed, while unauthorized packets are dropped. Box 240 is then carried out.

[00069] At box 240, the PFC 46 returns the packet to interface 42b for further processing. Box 250 is then carried out.

[00070] At box 250, the interface 42b passes the data packet to network 44b where the data packet is further processed.

[00071] Referring now to FIG. 6, as well as FIG. 2 through FIG. 5b, there is generally shown the acts associated with the Firewall Manager (FWM 57) processes in accordance with the present invention. This sequence is carried out during box 120 of FIG. 5b.

[00072] At box 300, the FWM 57 intercepts an “entering” packet. In the present illustrative case the packet entering firewall device 10 via interface 42a is intercepted at point 60. Preferably, FWM 57 intercepts the packet prior to interception by PFC 46 (box 130 of FIG. 5a). Box 310 is then carried out.

[00073] At box 310, the FWM 57 inspects the header component of the data packet to ascertain the address (source and destination) and port information contained therein. Box 320 is then carried out.

[00074] At box 320, the address and port information obtained in box 310 is compared with the corresponding information in the plurality of mini-sessions 58. If a match is established between the packet and a corresponding mini-session 58 according to address and port information, then box 330 is carried out. Otherwise box 340 is carried out.

[00075] At box 330, the intercepted packet has a matching mini-session 58. A match indicates that the intercepted packet is authorized for transfer without ACL verification and firewall application-level inspection through the firewall device 40. Thus, a “pass” flag is set with the packet to communicate this authorization. For example, as shown in FIG. 4, the “pass” bit of flag slot 66 may be set with a “1” bit to indicate a “pass” flag. Conversely, a “0” bit may be used in the “pass” bit of slot 66 to indicate a lack of a “pass” flag. As described above, the PFC 46 will bypass ACL verification if this “pass” flag is set.

[00076] The FWM 57 also determines if the intercepted packet has a matching mini-session which can be updated or inspected “in-place”. In general, sessions (and mini-sessions) can be updated in-place if application-level inspection is not required. If the mini-session can be updated in-place, a “do not divert” flag (e.g., a “1” bit in the “do not divert” bit of slot 66) is set to communicate that the switching process 48 will bypass firewall application level inspection. Box 340 is then carried out.

[00077] At box 340, the packet is returned to point 60 (the interception point) for further processing by the PFC 46.

[00078] Referring now to FIG. 7, as well as FIG. 2 through FIG. 6, there is generally shown the acts associated with the firewall services processes in accordance with the present invention. This sequence is carried out during box 180 of FIG. 5a.

[00079] At box 400, the switching process receives a data packet for inspection and routing, typically from the PFC 46. Diamond 410 is then carried out.

[00080] At diamond 410, the switching process inspects the data packet to determine whether the “do not divert” flag is set. As described above, the “do not divert” flag is set by the FWM 57 if the intercepted packet has a matching mini-session which can be updated or inspected “in-place” (box 330 of FIG. 6). In general, sessions can be updated in-place if application-level inspection is not required. As noted above, the FWM 57 may be configured to provide application-level inspection, but the switching process 48 suffers a performance penalty for carrying out such inspection. If the “do not divert” flag is set, diamond 430 is carried out, otherwise box 460 is carried out.

[00081] At diamond 430, the mini-session (as associated session) can be updated in-place. As such, the intercepted packet is authorized for transfer without ACL verification and firewall application-level inspection through the firewall device 40. Thus, firewall application-level inspection (box 460 and 470) is bypassed. Instead the packet is inspected to ascertain whether the transfer is completed. This check is typically carried out by detecting a signal indicating the end of the data. If the data transfer is completed, box 450 is carried out. Otherwise diamond 440 is carried out.

[00082] At diamond 440, the FWM 57 tracks whether a predetermined timeout period for data transfer has been exceeded using conventional methods known in the art, and as described above. The timer to track this timeout period may be maintained by the FWM 57 or by the session manager 54. If the timeout period is exceeded, box 450 is carried out. Otherwise box 500 is carried out.

[00083] At box 450, the data transfer has either completed or exceeded the timeout threshold. As such the session and mini-session corresponding to the data transfer are deleted, typically by communicating a request to the session manger 54 which then carries out the deletion of the corresponding session and mini-session. Box 500 is then carried out.

[00084] At box 460, the “do not divert” flag is not set for the intercepted packet. Accordingly, the switching process 48 diverts the packet to the firewall services 50 for inspection and authorization of the packet. Box 470 is then carried out.

[00085] At box 470, the firewall services component 50 inspects the payload component of the data packet for authentication using conventional application-level inspection means. If the packet is authorized, box 480 is carried out. Otherwise the packet is deleted.

[00086] At box 480, the session manager 44 instantiates a session 56 in the firewall services 50 corresponding to the current data transfer. As note above, the created session includes header data (addresses and port information, for example) as well as payload data (user id and communication protocol, for example) to track the data transfer associated with the currently inspected packet. Box 490 is then carried out.

[00087] At box 490, the session manger 44 instantiates a corresponding mini-session 58 in the switching process to authorize future data transfers associated with the presently inspected packet. It is noted that as packets are processed herein, the session and associated mini-session are created only once if they do not exists, and not for every packet associated with the corresponding session. Box 500 is then carried out.

[00088] At box 500, the packet is then routed to the appropriate interface according to the address information contained in the header of the packet. In the present example, the data packet is communicated from network 44a to network 44b, and thus is routed to interface 42b via point 62 for further processing.

[00089] Accordingly, it will be seen that this invention provides a firewall system and method which optimizes the performance of the firewall process by reducing overhead associated with ACL verification and firewall-application level authorization. Although the description above contains many specificities, these should not be construed as limiting the scope of the invention but as merely providing an illustration of the presently preferred embodiment of the invention. Thus the scope of this invention should be determined by the appended claims and their legal equivalents.