This step-by-step article describes how to configure
the URLScan security tool to protect ASP.NET Web applications.
URLScan is an Internet
Server API (ISAPI) filter that screens and
monitors HTTP requests for Internet Information Server
4.0, Internet Information Services 5.0, and Internet Information Services 5.1 (IIS). URLScan is used to reduce the exposure of IIS to potential Internet attacks.
By default, URLScan
does not make special accommodations for file name extensions that ASP.NET
Web applications use. You can change the URLScan configuration to add an extra
layer of security for these applications. You must disable or enable different file name extensions for application level tracing, XML Web services, and remoting.back to the
URLScan to enable standard ASP.NET file name extensions that users may requested, follow these steps:
- Install the URLScan tool. For information and instructions, visit the following Microsoft Web site:
- Open the Urlscan.ini file in a text editor (such as Notepad). This file is located in the \System Root\System32\Inetsrv\Urlscan\ folder.
- In the [AllowExtensions] section, add the following file name extensions:
- In the [DenyExtensions] section, add the following file name extensions:
- To turn on application level tracing, add the .axd file name extension to the [AllowExtensions] section. If you do not want to turn on application level tracing, add .axd to the [DenyExtensions] section.
- To allow Web services, add the .asmx file name extension to the [AllowExtensions] section. If you do not want to allow Web services, add .asmx to the [DenyExtensions] section.
- To turn on remoting, add the .rem file name extension and the .soap file name extension to the [AllowExtensions] section. If you do not want to turn on remoting, add .rem and .soap to the [DenyExtensions] section.
- Save and then close the Urlscan.ini file. You must restart IIS for the changes to take effect.
These steps are designed to offer optimal protection, regardless of whether the UseAllowVerbs
setting is turned on in URLScan.back to the top
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
How to secure an ASP.NET application by using Windows
How to secure an ASP.NET application using client-side certificates
back to the top
How to secure applications that are built on the .NET Framework