Best Practices for Server Hardening?

[D_M_S]

SugarCE 5.2i
MySQL 5x
IIS(x64)

I am in the process of starting a new business and I have been very impressed with SugarCE. I've created a dedicated install of the server because I see Sugar as the future of my company pipeline.

I'd like to hear about some best practices for hardening a server and making sure that it's ready to release to my employees. Is there a generally accepted checklist of steps or changes that I should go through with both Sugar and MySQL?

[josh.sweeney]

These two articles have a good amount of information.

http://www.puschitz.com/SecuringLinux.shtml
http://www.ibm.com/developerworks/li...l-seclnx1.html

[D_M_S]

I appreciate the help.

But . . .
1 - I'm running on Windows

2 - I was referring more to Sugar specific items like files/folders that need X permission for install but don't need it in production. I would also assume that removing "install.php" would also be a good idea.

So, really, I'm looking for sugar folders/files that need to be taken care of properly before going into full-blown production.