The common language runtime and the .NET Framework provide many useful classes and services that enable developers to easily write secure code and enable system administrators to customize the permissions granted to code so that it can access protected resources. In addition, the runtime and the .NET Framework provide useful classes and services that facilitate the use of cryptography and role-based security.
Important
Effective with the .NET Framework version 4, there are major changes to the code access security system. Security policy is no longer applied to applications. All applications that can be run from the desktop are now executed as full-trust applications. This includes both applications on the computer and applications that can be run from a network share. Partially trusted applications must be run in a sandbox, which determines their grant set. The permission system continues to be used, but it is transcended by security transparency rules. For information about these changes, see Security Changes in the .NET Framework 4.
Describes how to interact with code access security in your code. This section is important to developers and can be of interest to system administrators.
(Applies only to code that uses legacy security rules.) Describes how to manage code access security policy. This section is of interest to system administrators who manage .NET Framework applications.
(Applies only to code that uses legacy security rules.) Describes some of the best practices for administrating code access security policy. This section is of interest to system administrators who manage .NET Framework applications.
Describes the managed classes that enable you to programmatically create or modify discretionary access control lists (DACLs) and system access control lists (SACLs) for protected resources such as files and folders. This section is of interest to developers.
Describes command-line tools that help you perform security-related tasks, such as configuring security policy, managing certificates, and digitally signing files.
(Aapplies only to code that uses legacy security rules.) Describes how to configure security policy using the .NET Framework Configuration tool and the Code Access Security Policy tool, and how to import security components using XML files.