Class | Description |
---|---|
CodeAccessPermission | CodeAccessPermission is an abstract base class that provides functionality required by all code access permissions. Some of its methods are abstract and must be implemented by non-abstract subclasses of CodeAccessPermission. Some of the implemented methods cannot be overridden. |
DynamicSecurityMethodAttribute | This attribute marks security methods in our runtime System.Security implementation that require additional stack space be allocated for a security object in methods that call them. |
NamedPermissionSet | A named permission set is a permission set that has a name and description associated with it. Named permission sets are used in security policy administration to specify the permissions to be granted to code that belongs to certain code groups. |
PermissionSet | Represents a set of permissions of different types. This class supports all functionality of a permission, for the set of permissions as a whole. |
SecurityElement | The SecurityElement class is defined to represent the XML object model for encoding security objects. The design is intended to be a lightweight implementation of a simple XML object model for use within the security system, and not intended for use as a general XML object model. |
SecurityException | Represents the exception that is thrown when there is a security error. |
SecurityManager | The SecurityManager class provides a general purpose API for interacting with the security system. Security provides methods to access and manipulate the security policy configuration. |
SuppressUnmanagedCodeSecurityAttribute | This attribute can be applied to methods that want to call into native code without incurring the cost of a security check in doing so: only code that has been granted SecurityPermission.UnmanagedCode permission may do this. |
UnverifiableCodeAttribute | Marks modules containing unverifiable code. |
VerifierException | Represents anexception that is thrown when a verication error occurs. |
XMLSyntaxException | Exception denotes syntax error in XML parsing. |
Interface | Description |
---|---|
IEvidenceFactory | Objects that provide evidence to policy use the IEvidenceFactory interface to do so. Both AppDomain and Assembly implement the interface.
Application code should have no need to implement this interface. AppDomain provides the evidence associated with the domain by its host at creation; Assembly returns assembly evidence if any as well as evidence for valid signatures such as software publisher and strong names. IEvidenceFactory |
IPermission | Defines the basic functionality of any permission object. Permissions in the NGWS runtime are objects that describe a set of operations the can be secured for a given resource. A permission object describes operations or access subject to security control; it does not represent a right to do such operations or access in and of itself. Permissions are used by both application code and the runtime security system as the building blocks of the NGWS runtime security system in the following ways:
|
ISecurityEncodable | This interface defines the methods that convert permission object state to and from XML element representation. The XML representation of permissions is used to describe instances of permissions for code requests, declarative security permission sets, and security policy configuration. |
ISecurityPolicyEncodable | XML encodable policy objects implement this interface to support standard to- and from-XML conversion- see ToXml and FromXml methods for details. |
IStackWalk | The IStackWalk interface defines methods handling the stack walk and override features that must be supported by all code access security permissions.
Code access security provides runtime protection against unauthorized calls by checking that all callers have the necessary granted permission that is demanded by the called code. In addition to demands, stack walk interface handles cases where code needs to override and either assert- not require further callers above it on the stack to have some permission- or deny (or permit-only) some permission. For a complete description of code access security and how demands and overrides work refer to the Permissions specification. |
Enumeration | Description |
---|---|
SecurityZone | Defines the integer values corresponding to security zones used by security policy. For more information about security zones refer to the security zones documentation. |