Improving Web Application Security: Threats and - CGISecurity

740 Improving Web Application Security: Threats and CountermeasuresEnvironment VariablesCheck DescriptionCode that accesses environment variables is restricted with EnvironmentPermission. Thisapplies especially if your code can be called by untrusted code.Environment permission requirements are declared by using declarative security attributeswith SecurityAction.RequestMinimum.Code Access Security ConsiderationsIf an entry is preceded by a star (*), it indicates that the checks are performed bythe FXCop analysis tool. For more information about FXCop security checks, seehttp://www.gotdotnet.com/team/libraries/FxCopRules/SecurityRules.aspx.Check DescriptionAssemblies marked with AllowPartiallyTrustedCallersAttribute (APTCA) do not expose objectsfrom non-APTCA assemblies.Code that only supports full-trust callers is strong named or explicitly demands the full-trustpermission set.All uses of Assert are thoroughly reviewed.All calls to Assert are matched with a corresponding call to RevertAssert.*The Assert window is as small as possible.*Asserts are proceeded with a full permission demand.*Use of Deny or PermitOnly is thoroughly reviewed.All uses of LinkDemand are thoroughly reviewed. (Why is a LinkDemand and not a fullDemand used?)LinkDemands within Interface declarations are matched by LinkDemands on the methodimplementation.*Unsecured members do not call members protected by a LinkDemand.Permissions are not demanded for resources accessed through the .NET Frameworkclasses.Access to custom resources (through unmanaged code) is protected with custom codeaccess permissions.Access to cached data is protected with appropriate permission demands.If LinkDemands are used on structures, the structures contain explicitly definedconstructors.