Network & Infrastructure / Segmentation, TLS & Secure Connectivity
Detect security-policy drift between redundant gateways
A failover exposes traffic that was blocked on the former active gateway. The pair shares session state but carries different effective access policies or object definitions.
Environment and inputs: Stateful network boundaries, TLS endpoints and IPsec gateways; use the deployed security policy and implementation manual. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Compare normalized effective rules, address objects, dynamic group membership and firmware-dependent defaults on both nodes. Include per-node local overrides that a central manager may not overwrite.
Explain the result
High availability of forwarding does not imply identical policy. Synchronization can cover sessions or configuration subsets while leaving operational dependencies inconsistent.
Plan the fix
Establish a reviewed policy source and explicit node-specific exceptions, then verify the applied result after deployment. Treat semantic differences across software releases as more than a text diff.
Check the result and rollback
Run positive and negative flow tests through each gateway and during failover. Revert the drift correction if it removes an intentional local dependency, then document that exception rather than leaving unexplained divergence.