Which ASV Scan characteristic accounts for load balancers?

Which ASV Scan characteristic accounts for load balancers?

• A. Be Accurate
• B. Be Platform Independent
• C. Perform Service/OS Discovery
• D. Account for Load Balancers

Answer: (D)

Load balancers change what the scanner sees on the network. They can front many backend servers or terminate TLS, presenting a single endpoint to the outside while the actual services run behind it. If you don’t account for this, you might miss vulnerabilities on the real backend hosts or misinterpret what the front-end appears to be securing. The ability to account for load balancers ensures the scan covers all underlying hosts and handles front-end behavior like TLS offloading, so the assessment reflects the true security posture behind the load balancer. The other options are broader or unrelated to this specific scenario: accuracy is important in general, platform independence isn’t about load balancers, and service/OS discovery focuses on identifying services rather than addressing how traffic is distributed or terminated by a load balancer.

Load balancers change what the scanner sees on the network. They can front many backend servers or terminate TLS, presenting a single endpoint to the outside while the actual services run behind it. If you don’t account for this, you might miss vulnerabilities on the real backend hosts or misinterpret what the front-end appears to be securing. The ability to account for load balancers ensures the scan covers all underlying hosts and handles front-end behavior like TLS offloading, so the assessment reflects the true security posture behind the load balancer. The other options are broader or unrelated to this specific scenario: accuracy is important in general, platform independence isn’t about load balancers, and service/OS discovery focuses on identifying services rather than addressing how traffic is distributed or terminated by a load balancer.