A network security team is establishing a zero-trust transit pipeline for remote systems administrators managing a backend database server located in a restricted internal network zone. Place the traffic flow controls and access verification steps in the correct sequential order, from the initial remote connection request to establishing access on the target server.
- 1Authenticate to the enterprise perimeter gateway using TLS-encrypted VPN tunnels enforcing multi-factor authentication (MFA).
- 2Establish an encrypted administrative session to a hardened bastion host located within a dedicated management DMZ.
- 3Traverse an internal Next-Generation Firewall enforcing identity-aware microsegmentation policies and protocol inspection between the management DMZ and the database zone.
- 4Authenticate to the backend database server using ephemeral credentials issued via scoped just-in-time access controls.
Answer
The correct sequence for administrative transit into a highly segmented database zone begins at the external perimeter VPN gateway with MFA, proceeds to an isolated bastion host in a management DMZ, transitions through internal microsegmentation firewalls evaluating East-West traffic, and culminates with scoped authentication on the target database server.
Secure network architecture mandates defense-in-depth and strict boundary isolation. The correct order ensures that untrusted external traffic is authenticated at the perimeter VPN, proxied through a bastion host in a management DMZ, filtered through internal microsegmentation firewalls for East-West traffic control, and finally authorized at the destination asset using least-privilege credentials.
Step-by-Step Solution
Key Concept
Bastion Transit Rules and Zone-based Microsegmentation Flow Controls
Estimated Time:2m 0s