An enterprise deploys active inline Network Intrusion Prevention System (NIPS) appliances on two parallel border gateway links configured for active-active asymmetric routing. Shortly after deployment, users experience intermittent session terminations and dropped connections on legitimate TCP applications. Packet inspection reveals that outbound TCP SYN packets traverse Link 1 (monitored by NIPS 1), while the corresponding SYN-ACK return packets traverse Link 2 (monitored by NIPS 2), causing NIPS 2 to drop the return packets as invalid out-of-state traffic. Which of the following architectural adjustments will eliminate these session drops while maintaining active inline threat prevention across both links?
- Establish a dedicated high-speed inter-appliance state-sharing connection between NIPS 1 and NIPS 2 to synchronize TCP flow tables in real time.Answer
- BRelocate both NIPS appliances to out-of-band SPAN ports on the core switches so they can perform passive TCP stream reassembly.
- CReconfigure the inline NIPS engine to use signature-based pattern matching exclusively rather than anomaly-based heuristic inspection.
- DModify the NIPS firewall rulebase to remap TCP application traffic to UDP port 53 to bypass stateful handshake verification.
Answer
The correct architecture requires establishing a dedicated inter-appliance state-sharing bus between NIPS 1 and NIPS 2 to synchronize TCP session state tables across both active asymmetric paths.
Establishing a state-synchronization link between dual inline NIPS appliances allows TCP session creation records from NIPS 1 to be mirrored immediately to NIPS 2. Consequently, when return SYN-ACK traffic arrives at NIPS 2 via an asymmetric route, NIPS 2 recognizes the established session state and passes the legitimate traffic inline without dropping it.
Step-by-Step Solution
Key Concept
Stateful Inspection and Asymmetric Routing in Inline NIPS Deployment
Estimated Time:3m 0s