Manage Learn to apply best practices and optimize your operations.

Seven key IIS security tips

Here are seven key IIS security tips you should know.

Over the past few years IIS has been the most maligned Web server out there. Whether it's popularity has made it an easy target or if it does have some basic weaknesses, there are still some things you should be aware of.

If you are using Internet Information Server, here are seven key security tips you need to know:

  1. The IUSR_<servername> account is just as well-known as the administrator account. If someone can learn your Web server's name, they also know the default Web user account. You should rename this account, but be sure to duplicate the changes both in Active Directory Users and Computers and the IIS Web and FTP services Properties.

  2. The IUSR account is a member of the Everyone & Authenticated Users groups. The IUSR account has the Access this computer from the network and Log on locally User Rights. So, specifically deny access for the IUSR account on everything, then grant the IUSR account access only where needed.

  3. The IUSR account is authenticated automatically, so all anonymous Web and FTP users are logging in even if they don't know it.

  4. Avoid using common filenames and directory structures; i.e., don't use wwwroot, ftproot, or iispub since these are well-known. Using unique folder names will thwart many types of attacks that require a known directory path to function. Also, avoid using virtual directories or creating aliases to folders on other systems. If your directory structure is ever compromised, links to other systems will become vulnerable.

  5. Avoid deploying Web services on domain controllers, file servers and other servers that host sensitive and confidential data.

  6. When hosting internal or private Web services, use an alternate TCP port to make its discovery that much more difficult for those who are not authorized.

  7. Never use any script or programming component on a production IIS system until it has been thoroughly tested. For example, if an ISAPI scripts uses the RevertToSelf(); command, it can grant Web surfers system level privileges.
About the author
James Michael Stewart is a researcher and writer for Lanwrights, Inc.

Dig Deeper on Windows Server troubleshooting

Solve SQL Server permissions and authentication problems For the past two weeks I've been trying to resolve a permissions problem, an authentication problem, or both. I've run out of ideas of where to look. Here is what I have: (1) SQL Server 2005 on a Member Server (2003) (2) I'm running Visual Studio .NET 2005 on my work station. (3) I can access the SQL Server data from within my .NET project. (4) If I access the website from outside my .NET project, I get Login Failed for user NT_AUTHORITY/NETWORK SERVICE. This happens on any PC and even the member server that houses SQL and the Intranet site IIS. (5) The reason I think I have a permissions problem is because of the behavior of two seperate test projects. Project #1 uses PROFILES to save state. When the program gets to this line of code, the Login Failed message appears. In project #2, I'm not saving state. But when the code attempts to gather data into a dataset, the program halts with the Login Failed message. Can you give me specific instructions on where to look and what to try?

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.