Difference between revisions of "Test Account Provisioning Process (OTG-IDENT-003)"

From OWASP
Jump to: navigation, search
(Final edit)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{Template:OWASP Testing Guide v4}}
 +
 
== Summary ==
 
== Summary ==
  
 
The provisioning of accounts presents an opportunity for an attacker to create a valid account without application of the proper identification and authorization process.  
 
The provisioning of accounts presents an opportunity for an attacker to create a valid account without application of the proper identification and authorization process.  
 +
  
 
== Test objectives ==
 
== Test objectives ==
  
Verify which accounts may provision other accounts and of what type
+
Verify which accounts may provision other accounts and of what type.
 +
 
  
 
== How to test ==
 
== How to test ==
Line 11: Line 15:
 
Determine which roles are able to provision users and what sort of accounts they can provision.  
 
Determine which roles are able to provision users and what sort of accounts they can provision.  
  
Is there any verification, vetting and authorisation of provisioning requests?
+
* Is there any verification, vetting and authorization of provisioning requests?
  
Is there any verification, vetting and authorisation of de-provisioning requests?
+
* Is there any verification, vetting and authorization of de-provisioning requests?
  
Can an administrator provision other administrators or just users?  
+
* Can an administrator provision other administrators or just users?  
  
Can an administrator or other user provision accounts with privileges greater than their own?
+
* Can an administrator or other user provision accounts with privileges greater than their own?
  
Can an administrator/user deprovision themselves?
+
* Can an administrator or user de-provision themselves?
 +
 
 +
* How are the files or resources owned by the de-provisioned user managed? Are they deleted? Is access transferred?
  
How are the files/resources owned by the de-provisioned user managed? Are they deleted? Is access transferred?
 
  
 
=== Example ===
 
=== Example ===
  
In Wordpress, only a user's name and email address are required to provision the user, which can be done by
+
In WordPress, only a user's name and email address are required to provision the user, as shown below:
 +
 
 
[[File:Wordpress_useradd.png|800px]]
 
[[File:Wordpress_useradd.png|800px]]
  
De-provisioning of users requires the administrator to select the users to be de-provisioned, selecting Delete from the dropdown menu (circled) and then applying this action. The administrator is then presented with a dialog box asking what to do with the user's posts (delete or transfer them).
 
[[File:Wordpress_authandusers.png|800px]]
 
  
== Tools ==
+
De-provisioning of users requires the administrator to select the users to be de-provisioned, select Delete from the dropdown menu (circled) and then applying this action. The administrator is then presented with a dialog box asking what to do with the user's posts (delete or transfer them).
  
 +
[[File:Wordpress_authandusers.png|800px]]
  
== References ==
 
  
 +
== Tools ==
  
== Remediation ==
+
While the most thorough and accurate approach to completing this test is to conduct it manually, HTTP proxy tools could be also useful.

Latest revision as of 08:37, 14 May 2014

This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: https://www.owasp.org/index.php/OWASP_Testing_Guide_v4_Table_of_Contents Back to the OWASP Testing Guide Project: https://www.owasp.org/index.php/OWASP_Testing_Project

Summary

The provisioning of accounts presents an opportunity for an attacker to create a valid account without application of the proper identification and authorization process.


Test objectives

Verify which accounts may provision other accounts and of what type.


How to test

Determine which roles are able to provision users and what sort of accounts they can provision.

  • Is there any verification, vetting and authorization of provisioning requests?
  • Is there any verification, vetting and authorization of de-provisioning requests?
  • Can an administrator provision other administrators or just users?
  • Can an administrator or other user provision accounts with privileges greater than their own?
  • Can an administrator or user de-provision themselves?
  • How are the files or resources owned by the de-provisioned user managed? Are they deleted? Is access transferred?


Example

In WordPress, only a user's name and email address are required to provision the user, as shown below:

Wordpress useradd.png


De-provisioning of users requires the administrator to select the users to be de-provisioned, select Delete from the dropdown menu (circled) and then applying this action. The administrator is then presented with a dialog box asking what to do with the user's posts (delete or transfer them).

Wordpress authandusers.png


Tools

While the most thorough and accurate approach to completing this test is to conduct it manually, HTTP proxy tools could be also useful.