Improving Web Application Security: Threats and - CGISecurity

Chapter 11: Building Secure Serviced Components 301Figure 11.2 highlights these top threats together with common serviced componentvulnerabilities.NetworkEavesdroppingOver privileged run-asidentityUnconstrainedDelegationClient(for exampleASP.NET)UnauthorizedAccessNo trafficencryptionEnterpriseServicesCatalogRepudiationDisclosure ofConfigurationDataPlain text secrets inconstructor stringsFigure 11.2Enterprise Services threatsNetwork EavesdroppingEnterprise Services applications often run on middle-tier application servers, remotefrom the Web server. As a result, sensitive application data must be protected fromnetwork eavesdroppers. You can use an Internet Protocol Security (IPSec) encryptedchannel between Web and application server. This solution is commonly used inInternet data centers. Serviced components also support remote procedure call (RPC)packet level authentication, which provides packet-based encryption. This is mosttypically used to secure communication to and from desktop-based clients.Unauthorized AccessBy enabling COM+ role-based authorization (it is disabled by default on MicrosoftWindows 2000), you can prevent anonymous access and provide role-basedauthorization to control access to the restricted operations exposed by your servicedcomponents.Unconstrained DelegationIf you enable delegation on Windows 2000 to allow a remote server to access networkresources using the client’s impersonated token, the delegation is unconstrained. Thismeans that there is no limit to the number of network hops that can be made.Microsoft Windows Server 2003 introduces constrained delegation.