Article ID: 815150 - Last Review: May 13, 2007 - Revision: 3.5 HOW TO: Limit the Web Services Protocols that a Server PermitsOn This PageSUMMARYThis step-by-step article describes how to limit the
protocols that a Web service supports. XML–based Web services exchange XML documents to communicate. This exchange can occur across any type of application-layer protocol. By default, ASP.NET Web services are exposed through four different protocols: HttpSoap, HttpPost, HttpGet, and Documentation. In many cases, only a subset of these four protocols is required. For example, Web services typically use only the HttpSoap protocol for communications. In these circumstances, if you remove the unused protocols, you increase the security of the application by decreasing the attack surface. This article describes how to disable Web services protocols that are used to communicate with an ASP.NET application. Disable Web Services ProtocolsTo disable a Web Services protocol for an ASP.NET application, follow these steps:
REFERENCES For more information, visit the following Microsoft Web sites: http://msdn2.microsoft.com/en-us/library/aa719558(VS.71).aspx
(http://msdn2.microsoft.com/en-us/library/aa719558(VS.71).aspx)
http://msdn2.microsoft.com/en-us/library/ackhksh7(vs.71).aspx
(http://msdn2.microsoft.com/en-us/library/ackhksh7(vs.71).aspx)
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
815179
(http://support.microsoft.com/kb/815179/EN-US/
)
HOW TO: Create the Web.config File for an ASP.NET Application
815178
(http://support.microsoft.com/kb/815178/EN-US/
)
HOW TO: Edit the Configuration of an ASP.NET Application
818014
(http://support.microsoft.com/kb/818014/
)
HOW TO: Secure Applications That Are Built on the .NET Framework
| Article Translations
|
Back to the top
