During a DoS testing engagement, what is a primary objective?

• A. List weak points on their network
• B. Demonstrate that no system can be protected against DoS attacks
• C. Show outdated equipment so it can be replaced
• D. Use attack as a launching point to penetrate deeper into the network

Answer: (A)

In a DoS testing engagement, the focus is on understanding how the network holds up under high load and where disruption could occur. The primary objective is to identify weaknesses and points of failure in the network and services so you can prioritize remediation and improve resilience. By listing weak points, you uncover bottlenecks, misconfigurations, single points of failure, and insufficient defenses, which then guides actions like implementing rate limiting, load balancing, redundancy, and DoS protection.

It isn’t about proving that nothing can be protected—no system is expected to be 100% invulnerable in practice. It isn’t primarily about showing outdated equipment, though hardware findings may emerge. And it isn’t about using the attack to penetrate deeper into the network; evolving an attack into broader intrusion tests goes beyond the scope of DoS testing and isn’t the goal here.