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

Test Account Provisioning Process (OTG-IDENT-003)

Revision as of 14:37, 14 May 2014 by Jane O'Connor (talk | contribs) (Final edit)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: Back to the OWASP Testing Guide 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 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?


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


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