.NET 247

Logon or Create an Account

System.Security.Permissions.SecurityAction Enumeration

Information

Base Types

Related Resources

Specifies the security actions that can be performed using declarative security.

Namespace: System.Security.Permissions

Assembly: mscorlib.dll

	System.Object
	System.IComparable
	System.IFormattable
	System.IConvertible

	View this type on MSDN
	Search for this type on MSDN using MSDN's own search engine
	Google for this type - all Web
	Google for this type - MSDN only

Articles (4)

Discussions (304)

Members

Rotor

Articles

Page:

Custom Permissions

C#Today

Any multi user system needs to have a concept of security to protect one users data from another. This security element could be anything from granting or denying a user access to a file, a network share, or certain entities in a database. These security mechanisms are controlled via the use of Permissions. Before the advent of .NET, using permissions in application code was hard, but now the framework allows a very open and extensible permission architecture. In this article, the third of the week's security-based articles, Kaushal Sanghavi explores the support that the .NET framework offers for working with permissions, and demonstrate how developers can design their own custom permissions to control access to protected data.

Implementing .NET Role-Based Security without COM+

Egg Head Cafe

Security is important. Most developers don't like security. It requires a lot of thought. It requires study. Most developers would rather just "write code", and leave security to "somebody else". Unfortunately, if you are a developer and your job is to produce an application, then guess who that "somebody else" usually is? It's YOU. Even behemoth Microsoft got the message loud and clear. They've made security the single most important thing, above everything else. Wanna know why .NET Server, which was supposed to be released back in March, is delayed until the third quarter? Security! They weren't satisfied, and so they went back to the drawing board, so to speak. And its for real, too. The Microsoft insiders with whom I am privileged to speak with from time to time are totally focused on security.

Security in .NET: Enforce Code Access Rights with the Common Language Runtime

MSDN

Component-based software is vulnerable to attack. Large numbers of DLLs that are not tightly controlled are at the heart of the problem. Code access security in the Common Language Runtime of the Microsoft .NET Framework addresses this common security hole. In this model, the CLR acts as the traffic cop to assemblies, keeping track of where they came from and what security restraints should be placed on them. Another way the .NET Framework addresses security is by providing preexisting classes which have built-in security.

Unify the Role-Based Security Models for Enterprise and Application Domains with .NET

MSDN

Role-based security allows administrators to assign access permissions to users based on the roles they play rather than on their individual identities. These privileges can be used to control access to objects and methods, and are easier to identify and maintain than user-based security. The .NET Framework provides two role-based security models, which are exposed as two namespaces: System.Enterprise-Services and System.Security.Permissions. Presented here is a comparison of the two options and a discussion of when each is the right choice. The author also demonstrates the process involved in setting up access security and discusses role memberships.

BootFX
Reliable and powerful .NET application framework.

Looking to invest in a major software project? Technical and commercial advice available here.

Other Helpful Sites
MBR 247
Topaz Filer
SharePoint Email Filing
Software Advisory Services