Improving Web Application Security: Threats and - CGISecurity

Checklist: Security Review for Managed Code 739Unmanaged Code Access (continued)Check DescriptionUnmanaged types or handles are never exposed to partially trusted code.Pointers are private fields.Methods that use IntPtr fields in a type that has a finalizer call GC.KeepAlive(object).Resource Access ConsiderationsFile I/OCheck DescriptionNo security decisions are made based on filenames.Input file paths and file names are well formed.Environment variables are not used to construct file paths.File access is constrained to the context of the application (by using a restrictedFileIOPermission).Assembly file I/O requirements are specified using declarative security attributes (withSecurityAction.RequestMinimum).Event LogCheck DescriptionEvent log access code is constrained using EventLogPermission.This particularly applies if your event logging code could be called by untrusted callers.Event sources are created at installation time (or the account used to run the code thatwrites to the event log must be allowed to create event sources by configuring anappropriate ACL in the registry).Security-sensitive data, such as passwords, is not written to the event log.RegistryCheck DescriptionSensitive data, such as database connection strings or credentials, is encrypted prior tostorage in the registry.Keys are restricted. If a key beneath HKEY_CURRENT_MACHINE is used, the key isconfigured with a restricted ACL. Alternatively, HKEY_CURRENT_USER is used.Registry access is constrained by using RegistryPermission. This applies especially if yourregistry access code could be called by untrusted callers.