Securing a Windows 2003 platform-based Web server

Windows-based IIS running Web sites always give people a feeling is fragile. Early IIS does have a lot of problems, but I personally think that since Windows Server 2003 was released, the new security features of IIS6 and Windows Server 2003, improved management capabilities, and system stability have been greatly enhanced. While Microsoft is not ready to develop ASP from Windows Server 2003, especially when it is no longer in good condition for access databases, the advantages of it have forced me to abandon Windows Server. And I don't need to run too many asp+access, because my program is php+mysql (honestly I don't like Microsoft's ASP and ASPNET), and I do trust Windows Server 2003!

Server, website, see these words everyone will think about, not only the performance of more attention is its security issues. Many people can not do a very perfect security reinforcement, because most of the data are from the Internet, and the Internet information is not so detailed, after all, each server's application environment and operating procedures are different.

I am engaged in the Internet industry only 2 years, during which encountered a lot of problems, I managed the server part is open (public), it is open to the Internet users, so I face more problems! Security first when it wants, the second is the stability of the system, the last is the performance. To know that there are many forms of applications on the server, some of the programs themselves are flawed, the light of the server when the machine, serious threat to the server's entire data security.

For example, there is a Windows server running more than 300 web sites, and for a while it often down machines, discovering that memory leaks are particularly fast, In a few minutes, memory usage soared to 900M or even 1.2G, a time when the server was not reachable by remote, but the server system itself was still running. This problem really gave me a headache for a long time, because if you want to troubleshoot the failure to start from these sites, and the number of sites to hinder my resolution progress. Later, through the Filemon monitoring file read to narrow the scope of the investigation, after the suspicious site isolation, and finally find the point of failure and solve. You know, a little bit of code is going to get the Windows server running IIS5 to hang up! The lower-level applications are changed to the program pool in Windows Servers 2003 so that we can set up a pool for memory and CPU protection. It's this feature that makes me lose a lot of work and the system is a lot more stable.