How to split responsibilities in a dual-firewall design without duplicating policy
With an Internet-edge firewall and a server-zone firewall, define ownership for Internet access, NAT/secure remote access, east-west traffic and server segmentation so policy is clear and routes cannot bypass controls.

Establish a factual baseline with “outbound NAT/secure remote access/internet boundaries” and “east-west access in the server zone”, then move to “routing responsibility across the two firewalls”. Use routing, policy, session state and real application traffic as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking outbound NAT/secure remote access/internet boundaries, east-west access in the server zone and routing responsibility across the two firewalls independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · outbound NAT/secure remote access/internet boundaries | Checking outbound NAT/secure remote access/internet boundaries helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of outbound NAT/secure remote access/internet boundaries. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 02 · east-west access in the server zone | Checking east-west access in the server zone helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of east-west access in the server zone. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 03 · routing responsibility across the two firewalls | Checking routing responsibility across the two firewalls helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of routing responsibility across the two firewalls. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 04 · duplicate policies or unintended bypass | Checking duplicate policies or unintended bypass helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of duplicate policies or unintended bypass. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 05 · logging and change ownership | Checking logging and change ownership helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of logging and change ownership. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 06 · bypass and rollback plan for failures | Checking bypass and rollback plan for failures helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of bypass and rollback plan for failures. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
Investigation and change sequence
- Capture a baseline for outbound NAT/secure remote access/internet boundaries and east-west access in the server zone and compare it with a known-good system.
- Correlate evidence from routing responsibility across the two firewalls and duplicate policies or unintended bypass to distinguish the direct fault from dependent symptoms.
- Only if evidence points to logging and change ownership, plan a controlled change with backups, a change window and rollback triggers.
- Finally check bypass and rollback plan for failures and the real business workflow. Verify end-to-end business access, return routing and error logs, with a defined rollback check.
Validation and rollback evidence
- Verify end-to-end business access, return routing and error logs, with a defined rollback check.
- Recheck logging and change ownership and bypass and rollback plan for failures against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming outbound NAT/secure remote access/internet boundaries is sufficient while overlooking east-west access in the server zone and dependent checks.
- Changing several settings before preserving the original evidence for routing responsibility across the two firewalls.
- A successful port probe is not proof of application functionality; do not broaden access rules blindly.
Common questions and acceptance criteria
What should be checked first?
Begin with outbound NAT/secure remote access/internet boundaries and east-west access in the server zone. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Verify end-to-end business access, return routing and error logs, with a defined rollback check.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
Need to assess your actual environment?
Share the current topology, device and software versions, symptoms, impact, maintenance window and available configuration or backup evidence. We will assess risk, dependencies and rollback before defining scope.
