Seven key IIS security tips

Seven key IIS security tips



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,

    Requires Free Membership to View

    Login

    When you register, my team of editors will also send you the latest expert resources covering pertinent IT topics such as Windows server backup and recovery, server administration, storage management, infrastructure security, virtualization, Hyper-V, Active Directory and Group Policy.

    Cathleen A. Gagne, Senior Editorial Director

    By submitting your registration information to SearchWindowsServer.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchWindowsServer.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

  1. links to other systems will become vulnerable.

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

  3. 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.

  4. 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.


This was first published in April 2002

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Back to top