11.07.2015 Views

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 17: Securing Your <strong>Application</strong> Server 483By default, DCOM uses RPC dynamic port allocation, which r<strong>and</strong>omly selects portnumbers above 1024. In addition, port 135 is used by the RPC endpoint mappingservice.Restrict the ports required to support DCOM on the internal firewall in two ways:●●Define port ranges.This allows you to control the ports dynamically allocated by RPC. For moreinformation about dynamic port restrictions, see Microsoft Knowledge Base article300083, “How To: Restrict TCP/IP Ports on Windows 2000 <strong>and</strong> Windows XP.”Use static endpoint mapping.Microsoft Windows 2000 SP3 (or QFE 18.1 <strong>and</strong> later) or Windows Server 2003allows you to configure Enterprise Services applications to use a static endpoint.Static endpoint mapping means that you only need to open two ports in thefirewall: port 135 for RPC <strong>and</strong> a nominated port for your Enterprise Servicesapplication.For more information about static endpoint mapping, see Microsoft KnowledgeBase article 312960, “Cannot Set Fixed Endpoint for a COM+ <strong>Application</strong>.”<strong>Web</strong> ServicesIf you cannot open ports on the internal firewall, then you can introduce a <strong>Web</strong>servicesfaçade layer in front of the serviced components on the application server.This means that you only need to open port 80 for HTTP traffic (specifically, SOAPmessages) to flow in both directions.This approach does not allow you to flow transaction context from client to server,although in many cases where your deployment architecture includes a middle-tierapplication server, it is appropriate to initiate transactions in the remote servicedcomponent on the application server.For information about physical deployment requirements for service agents <strong>and</strong>service interfaces, such as the <strong>Web</strong>-services façade layer, see “Physical Deployment<strong>and</strong> Operational Requirements” in the Reference section of MSDN article,“<strong>Application</strong> Architecture for .NET: Designing <strong>Application</strong>s <strong>and</strong> Services,” athttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/distapp.asp.DTC RequirementsIf your application uses COM+ distributed transactions <strong>and</strong> these are used acrossremote servers separated by an internal firewall, then the firewall must open thenecessary ports to support DTC traffic. The DTC uses RPC dynamic port allocation.In addition to port 135 for RPC, DTC communication requires at least one additionalport.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!