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"
(New page: {{Template:OWASP Testing Guide v3}} '''This is a draft of a section of the new Testing Guide v3''' == Brief Summary == <br> ..here: we describe in "natural language" what we want to test...) |
|||
| Line 3: | Line 3: | ||
'''This is a draft of a section of the new Testing Guide v3''' | '''This is a draft of a section of the new Testing Guide v3''' | ||
| − | == | + | === Authentication Testing === |
| − | + | ---- | |
| − | . | + | |
| − | <br> | + | 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> |
| − | + | 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> | |
| − | + | 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> | |
| − | + | 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> | |
| − | + | 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. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | .. | ||
| − | |||
| − | |||
Revision as of 16:54, 28 June 2008
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
This is a draft of a section of the new Testing Guide v3
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.
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.
4.6.1 Testing for Path Traversal
First we test if it is possible to find a way to execute a path traversal and access to not authorized information
4.6.2 Testing for bypassing authorization schema
This kind of test focus on verify how the authorization schema has been impleemted for each role/privilege to access to reserved functions/resources.
4.6.3 Testing for Privilege Escalation
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.
