Improving Web Application Security: Threats and - CGISecurity

Chapter 13: Building Secure Remoted Components 365Using a Custom Channel SinkYou could implement a custom channel sink to perform client-side and/or serversideexception logging. You can log exception details in the SyncProcessMessage,ProcessMessage, or SyncProcessMessage methods if an exception occurs. TheIMessage and Exception parameters provide exception details.Auditing and LoggingIf you use the ASP.NET host, you can use IIS auditing features. If you use a customhost, implement custom auditing. To do this, you could implement a custom channelsink.Using a Custom Channel SinkYou could implement a custom channel sink to perform client-side and/or serversideauditing. You can get details from the SyncProcessMessage, ProcessMessage,or SyncProcessMessage methods.Code Access Security (CAS) ConsiderationsSummaryRemoting clients require full trust on version 1.0 and 1.1 of the .NET Framework.The System.Runtime.Remoting.dll assembly is not marked withAllowPartiallyTrustedCallersAttribute.To use remoting to call a remote component from partial trust code such as a partialtrust Web application, you must create a full trust wrapper assembly and sandbox theremote object method calls. For more information about sandboxing code and usingwrapper assemblies, see Chapter 9, “Using Code Access Security with ASP.NET.”The .NET Framework remoting infrastructure is designed for use in trusted serverscenarios where you can limit callers to trusted clients, for example by using IPSecsecurity policies. If you use an ASP.NET host and the HttpChannel, you benefit frombeing able to use the underlying security features provided by ASP.NET and IIS. Ifyou use a custom host and the TcpChannel, perhaps for performance reasons, youmust implement your own authentication and authorization solutions. IPSec can helpin these scenarios by providing machine level authentication and securecommunication.