Improving Web Application Security: Threats and - CGISecurity

142 Part III: Building Secure Web ApplicationsSystem.Security.PolicyThis namespace contains types that are used to implement the code access securitypolicy system. It includes types to represent code groups, membership conditions,policy levels, and evidence.System.Security.PermissionsThis namespace contains the majority of permission types that are used toencapsulate the rights of code to access resources and perform privileged operations.The following table shows the permission types that are defined in this namespace(in alphabetical order).Table 6.2 Permission Types Within the System.Security.Permissions NamespacePermissionDirectoryServicesPermissionDescriptionRequired to access Active Directory.DNSPermissionEndpointPermissionEnvironmentPermissionEventLogPermissionFileDialogPermissionFileIOPermissionIsolatedStorageFilePermissionIsolatedStoragePermissionMessageQueuePermissionOdbcPermissionRequired to access domain name system (DNS) servers on thenetwork.Defines an endpoint that is authorized by a SocketPermissionobject.Controls read and write access to individual environmentvariables. It can also be used to restrict all access toenvironment variables.Required to access the event log.Allows read-only access to files only if the file name is specifiedby the interactive user through a system-provided file dialog box.It is normally used when FileIOPermission is not granted.Controls read, write, and append access to files and directorytrees. It can also be used to restrict all access to the filesystem.Controls the usage of an application’s private virtual file system(provided by isolated storage). Isolated storage creates a uniqueand private storage area for the sole use by an application orcomponent.Required to access isolated storage.Required to access Microsoft Message Queuing messagequeues.Required to use the ADO.NET ODBC data provider. (Full trust isalso required.)