Summary of what happens to a packet as it enters and then leaves the  PIX\ASA firewall - please correct if you see something wrong - thx

Summary of what happens to a packet as it enters and then leaves the PIX\ASA firewall - please correct if you see something wrong - thx

Secure Home | Search | About
 Networking Firewalls    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
Summary of what happens to a packet as it enters and then leaves the PIX\ASA firewall - please correct if you see something wrong - thx t.eliason 11-27-2007
Posted by on November 27, 2007, 2:46 am
If you were  Registered and logged in, you could reply and use other advanced thread options
I get questions from clients asking what are the steps involved when a
packet enters a fw and leaves it.
So I did some research and came up with this sequence. Please suggest
corrections if you see a mistake. It is always good to have this kind
of summary handy.

Summary of Basic PIX\ASA Inspection Sequence and Operations:

The PIX\ASA inspection sequence is performed as follows:
1. As a packet enters an interface, the PIX evaluates the security
level for the source and destination interfaces. A low-to-high is
allowed only if there is an access-list that allows the connection and
a high-to-low is allowed by default unless a specific access-list
denies it. It there are ACL's present, the packet is checked against
these here.

2. Then the packet is checked against the stateful connection table.
If the packet is part of an already established connection, then it is
passed forward in order to be routed out and eventually translated if
specified. If the packet is identified as part of a new session, it
is passed to the ASA that performs the inbound network translation
(destination NAT).

3. ASA performs the inbound network translation (destination NAT) if
applicable.

4. The ASA updates the connections table with the packet's connection
state and the timers are started for that session.

5. The packet is checked against the Inspections database to
determine if the connection requires application-level inspection.
(checks to see if it needs a Fixup)

6. The packet gets routed to the interface designated by the routing
table.

7. At the exit interface, the source translation is performed, if
specified by using global statements and nat groups.

8. The packet is sent to the next hop router in the routing table or
to the final destination if it is present in the local firewall's
subnets.

Similar ThreadsPosted
KPF Summary Query March 26, 2005, 5:06 pm
Norton Internet Security doesnt find correct profile January 27, 2005, 1:37 pm
What's wrong with opening a port on the firewall? February 18, 2005, 7:26 am
What is wrong with GoogleDesktopNetwork3.dll ? June 26, 2007, 8:40 pm
Sonicwall 4100 wrong NAT May 22, 2007, 2:53 am
VPN-1 Checkpoint wrong gateway May 27, 2007, 6:55 am
Anything wrong with blocking "new" SYN/ACK packets? October 18, 2007, 10:26 pm
Firewall vs. Packet Filter? October 26, 2006, 1:43 am
Checkpoint Firewall-1 altering packet data: January 23, 2008, 12:05 am
impossible IP packet March 18, 2005, 8:23 am

The site map in XML format XML site map

Contact Us | Privacy Policy