Microsoft has just released version 2.0 of its Web Application Configuration Analyzer. A free download, the Web Application Configuration Analyzer scans IIS servers, hosted applications, and SQL Server instances for common security issues and misconfigurations. Version 2.0 contains 159 rules, each of which is a specific security check that generates a Passed, Failed, or Indeterminate outcome in the resulting report. Rules are broken down into three separate categories: General Applications, IIS Applications, and SQL Applications.
The rule checks were determined by Microsoft's own Information Security & Risk Management review team, whose job it is to harden pre-production and production servers within Microsoft. These checks are now being shared with the public. It's nice to know what Microsoft, one of the most attacked companies in the world, recommends doing on its own Web, application, and SQL servers to defeat hackers.
Each rule category can be expanded to reveal the underlying rule details.
As with any generic configuration scanner, false positives are bound to show up. Many of the Failed (or Indeterminate) findings were not true security vulnerabilities but a factor of the requirements of particular applications. Some of the rules that returned an Indeterminate finding surprised me, because they were normal checks appropriately rated by other Microsoft tools (such as Resultant Set of Policy for GPRESULT.exe). I expect these bugs to be fixed as the Web Application Configuration Analyzer matures.
I was especially impressed by the application rule checks, which pointed out specific application and configuration issues that I otherwise would have missed. An example:
Scans can be run against multiple computers, and future and historical findings can be compared. Reports are shown in HTML, but they can be exported into Microsoft Excel, saved to the normal file types (HTML, text, and so on), printed, or exported to Team Foundation Server.
In my first few tests, the Web Application Configuration Analyzer noted many issues that were not discovered by the more comprehensive and cross-platform scans by the Tenable Nessus vulnerability scanner or the excellent open source Nikto Web server scanner. This makes sense, considering the Web Application Configuration Analyzer's rules were created by the people who created and secure Microsoft's server software products.