"The problem? Too much code, huge dynamic environments, and far too little time. The answer? Automation! During web application assessments, testers often leverage tools like DirBuster to identify valid endpoints/pages through brute force. But what about when they have the source code sitting in front of them? Will they use it to their advantage and automate forced browsing? Some time ago I was working on a hybrid assessment that contained ~2k Classic ASP files. As I spidered the dynamic application, I found I had only discovered ~250 endpoints. Concerned that I may have missed sections of the application simply because they weren't referenced within the immediate portion available from the landing page, I whipped up a quick script to treat all .asp files within the directory as if they were valid resources being served by the web server.