If a packet does not match an existing session, JUNOS software creates a new session for it as follows:
For policy details, see Security Policies Overview.
You can configure these timeouts to be more aggressive or less aggressive. If you have changed the session timeout value, it is applied here. See Controlling Session Termination, If no traffic uses the session during the service timeout period, the router ages out the session and releases its memory for reuse.
Session initialization screens are applied. For screen details, see Attack Detection and Prevention.
Together they determine which policy is applied to the packet.
For zone details, see Security Zones and Interfaces.
The system checks the packet against policies you have defined to determine how the packet is to be treated.
For policy details, see Security Policies.
For NAT details, see Network Address Translation.
For ALG details, see the Application Layer Gateways (ALGs).
Decisions made for the first packet of a flow are cached in a flow table for use with following, related flows.