A municipal public website starts returning 429 and gateway errors after the tester launches aggressive automated crawls. Rules of engagement cap request rates and protect availability. What should the tester do next?
Select an answer to reveal the explanation.
Short Explanation
Think of the site like a busy front counter: slamming it with requests just creates a line that breaks for real residents. Slow down to what the rules allow, watch for pain, and keep gathering intel without taking the service down.
Full Explanation
Active web recon remains in scope only when it respects availability constraints written into the rules of engagement. Aggressive crawling that triggers 429 responses or gateway failures is a signal to reduce rate, not escalate. Ethical throttling preserves evidence quality while avoiding unintentional denial of service against civic systems.