This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Testing for Authorization"

From OWASP
Jump to: navigation, search
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
{{Template:OWASP Testing Guide v3}}
 
{{Template:OWASP Testing Guide v3}}
  
'''This is a draft of a section of the new Testing Guide v3'''
+
''' 4.6 Authorization Testing '''
 +
----
 +
 
 +
Authorization is the concept of allowing access to resources only to those permitted to use them. Testing for Authorization means understanding how the authorization process works, and using that information to circumvent the authorization mechanism.<br><br>
 +
Authorization is a process that comes after a successful authentication, so the tester will verify this point after he holds valid credentials, associated with a well-defined set of roles and privileges. During this kind of assessment, it should be verified if it is possible to bypass the authorization schema, find a path traversal vulnerability, or find ways to escalate the privileges assigned to the tester.
  
=== Authentication Testing ===
 
----
 
  
Authorization is the concept of allowing access to resources only to those permitted to use them. Testing for Authorization means understanding how the authorization process works and using that information to circumvent the authorization mechanism.<br>
+
[[Testing for Path Traversal  (OTG-AUTHZ-001)|4.6.1 Testing Directory traversal/file include (OTG-AUTHZ-001)]]
Authorization is a process that comes after a successfull authentication, so the tester will verify this point once that he holds a valid credentials with roles and privileges assigned. During this kind of assessement should be verified if it is possible to bypass the authorization schema, find a path Traversal, or found a way to escalate the privilege the tester holds.
 
  
[[Testing for Path Traversal|4.6.1 Testing for Path Traversal]]<br>
+
[[Testing for Bypassing Authorization Schema  (OTG-AUTHZ-002)|4.6.2 Testing for bypassing authorization schema (OTG-AUTHZ-002)]]
First we test if it is possible to find a way to execute a path traversal and access to not authorized information
 
  
[[Testing_for_Bypassing_Authorization_Schema|4.6.2 Testing for bypassing authorization schema]]<br>
+
[[Testing for Privilege escalation  (OTG-AUTHZ-003)|4.6.3 Testing for Privilege Escalation (OTG-AUTHZ-003)]]
This kind of test focus on verify how the authorization schema has been impleemted for each role/privilege to access to reserved functions/resources.
 
  
[[Testing for Privilege Escalation|4.6.3 Testing for Privilege Escalation]]<br>
+
[[Testing for Insecure Direct Object References (OTG-AUTHZ-004)|4.6.4 Testing for Insecure Direct Object References (OTG-AUTHZ-004)]]
During this phase the tester should verify that is not possible for a user to modify his privileges/roles inside the application that could allow a privilege escalation.
 

Latest revision as of 12:27, 8 August 2014

OWASP Testing Guide v3 Table of Contents

This article is part of the OWASP Testing Guide v3. The entire OWASP Testing Guide v3 can be downloaded here.

OWASP at the moment is working at the OWASP Testing Guide v4: you can browse the Guide here


4.6 Authorization Testing


Authorization is the concept of allowing access to resources only to those permitted to use them. Testing for Authorization means understanding how the authorization process works, and using that information to circumvent the authorization mechanism.

Authorization is a process that comes after a successful authentication, so the tester will verify this point after he holds valid credentials, associated with a well-defined set of roles and privileges. During this kind of assessment, it should be verified if it is possible to bypass the authorization schema, find a path traversal vulnerability, or find ways to escalate the privileges assigned to the tester.


4.6.1 Testing Directory traversal/file include (OTG-AUTHZ-001)

4.6.2 Testing for bypassing authorization schema (OTG-AUTHZ-002)

4.6.3 Testing for Privilege Escalation (OTG-AUTHZ-003)

4.6.4 Testing for Insecure Direct Object References (OTG-AUTHZ-004)