Access Control Cheat Sheet - Revision history

Dominique RIGHETTO: Point to the official site

2019-07-15T13:54:00Z

Point to the official site

2019-02-14T10:32:29Z

removed footer and the modification tag

2019-02-13T08:13:47Z

added common CS header

2019-02-13T07:56:04Z

migration to github

2016-03-06T18:38:05Z

2016-03-06T07:14:44Z

Starting work on fleshing out this section

2016-02-21T03:37:37Z

‎Authors and Primary Editors

2016-02-21T03:37:22Z

‎Permission Based Access Control

2016-02-21T03:34:39Z

‎Mandatory Access Control (MAC)

2016-02-21T03:33:50Z

trojan horses? confuses the issue.

← Older revision		Revision as of 13:54, 15 July 2019
Line 4:		Line 4:
	The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!		The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!

−	Please visit [https://~~github~~.~~com/OWASP/CheatSheetSeries/blob/master~~/cheatsheets/Access_Control_Cheat_Sheet.md Access Control Cheat Sheet] to see the latest version of the cheat sheet.	+	Please visit [https://cheatsheetseries.owasp.org/cheatsheets/Access_Control_Cheat_Sheet.html Access Control Cheat Sheet] to see the latest version of the cheat sheet.

@@ Line 1: / Line 1: @@
   __NOTOC__
 <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg|link=]]</div>
 The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!
 Please visit [https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Access_Control_Cheat_Sheet.md Access Control Cheat Sheet] to see the latest version of the cheat sheet.

← Older revision		Revision as of 08:13, 13 February 2019
Line 1:		Line 1:
		+	__NOTOC__
		+	<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Cheatsheets-header.jpg\|link=]]</div>
		+
		+	Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
		+
	The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!		The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!

@@ Line 1: / Line 1: @@
-=Introduction=
+The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!
-This article is focused on providing clear, simple, actionable guidance for providing access control security in your applications. The objective is to provide guidance to developers, reviewers, designers, architects on designing, creating and maintaining access controls in web applications
+Please visit [https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Access_Control_Cheat_Sheet.md Access Control Cheat Sheet] to see the latest version of the cheat sheet.
 = Other Cheatsheets =

@@ Line 91: / Line 91: @@
 Shruti Kulkarni - shruti.kulkarni [at] owasp.org<br/>
 Mennouchi Islam Azeddine - azeddine.mennouchi [at] owasp.org<br/>
 Jim Manico - jim [at] owasp.org<br/>

@@ Line 82: / Line 82: @@
 = Permission Based Access Control =
-TODO
+The key concept in Permission Based Access Control is the abstraction of application actions into a set of ''permissions''. A ''permission'' may be represented simply as a string based name, for example "READ". Access decisions are made by checking if the current user ''has'' the permission associated with the requested application action.
 = Authors and Primary Editors =

@@ Line 90: / Line 90: @@
 Jim Manico - jim [at] owasp.org<br/>
-== Other Cheatsheets ==
+= Other Cheatsheets =
 {{Cheatsheet_Navigation_Body}}
 __NOTOC__ <headertabs />
 [[Category:Cheatsheets]]

← Older revision		Revision as of 03:37, 21 February 2016
Line 81:		Line 81:

	= Permission Based Access Control =		= Permission Based Access Control =
		+
		+	TODO

	= Authors and Primary Editors =		= Authors and Primary Editors =

@@ Line 68: / Line 68: @@
 The advantages of using this methodology are:
-*Access to an object is based on the sensitivity of the object
+* Access to an object is based on the sensitivity of the object
-*Access based on need to know is strictly adhered to and scope creep has minimal possibility
+* Access based on need to know is strictly adhered to and scope creep has minimal possibility
-*Only an administrator can grant access
+* Only an administrator can grant access
 Problems that can be encountered while using this methodology:
-*Difficult and expensive to implement
+* Difficult and expensive to implement
-*Not agile
+* Not agile
 The areas of caution while using MAC are:
-*Classification and sensitivity assignment at an appropriate and pragmatic level
+* Classification and sensitivity assignment at an appropriate and pragmatic level
+* Assurance for MAC must be carried out to ensure that the classification of the objects is at the appropriate level.
 = Permission Based Access Control =

@@ Line 55: / Line 55: @@
 Problems that can be encountered while using this methodology:
 *Documentation of the roles and accesses has to be maintained stringently.
 *Multi-tenancy can not be implemented effectively unless there is a way to associate the roles with multi-tenancy capability requirements e.g. OU in Active Directory
 *There is a tendency for scope creep to happen e.g. more accesses and privileges can be given than intended for.