While automated attack toolkits may pose the biggest threat to Web apps, is there a good way to use such toolkits within my enterprise for the purposes of pen testing? Or is it too risky to use such volatile tools?
You can also use automated attack toolkits to improve the IT staff’s security awareness by showing them how easy it is to compromise a system. There are significant caveats to using any security tool, but they can be used safely. To use an attack tool safely, you should understand what the tool is doing, how to limit any potential damage and how to recover from any potential damage.
Recovery could be restoring relevant systems and databases from backup, but this might be a significant effort. You can learn how to use an attack tool safely and limit damage by testing it in a non-production or test environment. Some vendors and open source projects have test sites you can use for testing their tools. This testing could include monitoring all system and network access if that is the level of detail desired, but may not be necessary to understand the tool enough to use in a test environment. If you are not confident in your understanding of what the tool does, how to limit potential damage and how to recover from that damage, then you might not want to run the tool in a production environment.
One of the issues you might run into when running an automated Web attack toolkit that tests for SQL injection is that your database is filled with bad data from the tool testing multiple permutations to determine if the Web application is vulnerable. The attacks could also fill shared log files.
This was first published in November 2011