I found these earlier and thought they may help someone:

1. Use a Web application scanner to discover vulnerabilities and develop a security policy for each application based on its unique positive attributes.
2. When planning the security of a server, use a positive security model rather than a negative one. By default, turn off all access and then enable facilities on an as-needed basis. Although starting with everything turned on, and then looking for paths that can be closed off, is always more convenient, it's also a huge security risk.
3. Install a Web application firewall to ensure that all the security policies are enforced, just like you use a Network firewall to secure your network.
4. Be prepared to act on what you discover during your scans, by revising your business methods or your security policy.
5. Consider using an automated tool to check your server code against the OWASP Top Ten Web Application Vulnerabilities list.
6. Install all server OS security patches.

There is also an interesting article entitled "Is Your Site Being Hacked Without Your Knowledge?" and it can be found here: http://www.net-security.org/article.php?id=577