Skip to main content

Declarative Security to Protect Assemblies



Namespace: System.Security.Permissions

What is Declarative Code Access Security?
                Declarative Code Access security helps in restricting access to different resources; it also intimates the user if assembly required resource can’t be granted at the time of loading; it also helps in predetermining the resources an application require to run and it also protects system and resource from an attacker who intends to access unintended/protected resources. It also makes fine-tuned permission outline to make your application run in partially-trusted zone.

Because permission attribute classes are inherited from CodeAccesSecurityAttribute they share the following two most common properties.

Action:                  Specifies the security action to take. Use SecurityAction enumeration.

Unrestricted:     Set it to true if you want to give complete access to the specified resource.

Types of Assembly Permission Declaration:
             Set action property of the all CAS security attributes to one the following when using:

1.       SecurityAction.RequestMinimum
The resource is very critical to run the application. Runtime will throw exception if it is not granted.

2.       SecurityAction.RequestOptional
Refuse all permission except specified with RequestMinimum and RequestOptional. It is similar to saying RefuseAllExcept. Runtime will not throw exception if it is not granted.

3.       SecurityAction.RequestRefuse
Reduce the access to specified resources.

Use [assembly: UIPermission(SecurityAction.RequestMinimum, Unrestricted = true)] to enable application debugging, If you used SecrityAction.RequestionOptional.

Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »