Pass ISC CISSP Exam in First Attempt Guaranteed!

This response addresses a different condition: A campus network has a loop prevention misconfiguration causing broadcast storms across critical switches. The present case requires the measure described by Place narrow application proxies and restricted flows across separate trust zones.

Unrestricted lateral traffic magnifies the impact of internet-facing compromise. The proposal would not be defensible for this case.

This is appropriate for a later condition (Payroll later adds a read-only reporting integration to an external auditor.), but it does not directly resolve the initial need. An auditor's new data need requires scoped data release, not a general DMZ route.

This is an advantage of another design (Use inline prevention or segmentation enforcement where blocking is required and monitor false positives.), not the particular flaw of Permit any DMZ destination to reach all payroll ports for future troubleshooting.

This is a limitation elsewhere: A secure branch passes traffic through an IDS but does not prevent active lateral exploitation on a trusted subnet. It does not explain the deficiency of the specified proposed approach.

This explains a later shift in requirements (Payroll later adds a read-only reporting integration to an external auditor.), not the failure of the current proposal.

An approved change without an executed test cannot prove operating effectiveness. The needed evidence is A network rule review and active tests prove only approved application operations cross the boundary.

This demonstrates controls in another circumstance: An industrial wireless gateway forwards Modbus control traffic across a generic IP network without validating permitted command sources.

This other observation is relevant to: A wireless enterprise deploys one SSID with a shared passphrase for employees, visitors and industrial sensors.

This is a record of how the initial safeguard would be checked, not an action implementing the newly requested condition: A network rule review and active tests prove only approved application operations cross the boundary.

This is the appropriate response to the original situation: A breached public-facing host must not inherit arbitrary access to sensitive internal systems. It does not directly meet the new condition.

This remains inappropriate: Unrestricted lateral traffic magnifies the impact of internet-facing compromise.

Untrusted headers allow identity spoofing and privilege escalation. The proposal would not be defensible for this case.

This is appropriate for a later condition (The application must support certificate-based client authentication for administrators.), but it does not directly resolve the initial need. Administrative mTLS adds stronger client-origin assurance beyond ordinary proxy operation.

This response addresses a different condition: A secure branch passes traffic through an IDS but does not prevent active lateral exploitation on a trusted subnet. The present case requires the measure described by Design end-to-end authentication, header trust and TLS termination policy across the proxy boundary.

This concerns a later and different need: The application must support certificate-based client authentication for administrators. Administrative mTLS adds stronger client-origin assurance beyond ordinary proxy operation.

The proposed control fits another scenario: An industrial wireless gateway forwards Modbus control traffic across a generic IP network without validating permitted command sources. It does not directly address this scenario's primary requirement.

Untrusted headers allow identity spoofing and privilege escalation.

This demonstrates controls in another circumstance: A public IPv6 application is reachable over unintended paths because firewall rules were copied only from IPv4 addresses.

This other observation is relevant to: A network architect proposes relying only on DNS records for failover to a remote payment processor, with no application health checks.

An approved change without an executed test cannot prove operating effectiveness. The needed evidence is Negative tests prove identity claims are generated only by the trusted proxy and TLS paths are validated.

This is the appropriate response to the original situation: A reverse proxy becomes a trust boundary and must not allow spoofed client assertions. It does not directly meet the new condition.

This remains inappropriate: Untrusted headers allow identity spoofing and privilege escalation.

This is a record of how the initial safeguard would be checked, not an action implementing the newly requested condition: Negative tests prove identity claims are generated only by the trusted proxy and TLS paths are validated.

Layer 2 loops can amplify traffic until applications fail. The proposal would not be defensible for this case.

This is appropriate for a later condition (The organization migrates inter-building transport to an IP routed fabric.), but it does not directly resolve the initial need. Routed fabrics change the fault and topology control problem relative to bridging loops.

This response addresses a different condition: An industrial wireless gateway forwards Modbus control traffic across a generic IP network without validating permitted command sources. The present case requires the measure described by Implement resilient topology controls and validate spanning-tree or loop-free design under failure.

This is a limitation elsewhere: A public IPv6 application is reachable over unintended paths because firewall rules were copied only from IPv4 addresses. It does not explain the deficiency of the specified proposed approach.

This explains a later shift in requirements (The organization migrates inter-building transport to an IP routed fabric.), not the failure of the current proposal.

This is an advantage of another design (Create explicit IPv6 filtering and routing policy with equivalent least-privilege verification.), not the particular flaw of Disable loop prevention globally to maximize forwarding speed.

This demonstrates controls in another circumstance: A company uses unencrypted administrative Telnet across a shared campus network to operate core routers.

This other observation is relevant to: A cloud virtual private network has several workloads using overlapping CIDR blocks after a merger.

An approved change without an executed test cannot prove operating effectiveness. The needed evidence is A failover and mispatch exercise shows controlled convergence without flooding.