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

Jump to: navigation, search
Line 1: Line 1:
{{Template:OWASP Testing Guide v4}}
== Summary ==
== Summary ==

Revision as of 10:40, 21 November 2013

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


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 authorisation of provisioning requests?

Is there any verification, vetting and authorisation 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/user deprovision themselves?

How are the files/resources owned by the de-provisioned user managed? Are they deleted? Is access transferred?


In Wordpress, only a user's name and email address are required to provision the user, which can be done by Wordpress useradd.png

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). Wordpress authandusers.png