Difference between revisions of "Test User Registration Process (OTG-IDENT-002)"

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

Revision as of 11: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


Some websites offer a user registration process that automates (or semi-automates) the provisioning of people with system access. The identity requirements for access vary from positive identification to none at all, depending on the security requirements of the system. Many public applications completely automate the registration and provisioning process because the size of their userbase makes it impossible to manage manually. However, many corporate applications will provision users manually, so this test case may not apply.

Test objectives

Verify the identity requirements for user registration align with business/security requirements

Validate the registration process

How to test

  1. Verify the identity requirements for user registration align with business/security requirements
    1. Can anyone register for access?
    2. Are registrations vetted by a human prior to provisioning, or are they automatically granted if the criteria are met?
    3. Can the same person/identity register multiple times?
    4. Can users register for different roles/permissions?
    5. What proof of identity is required for a registration to be successful?
    6. Are registered identities verified?
  1. Validate the registration process
    1. Can identity information be easily forged or faked?
    2. Can the exchange of identity information be manipulated during registration?


In the Wordpress example below, the only identification requirement is an email address that is accessible to the registrant. Wordpress registration page.jpg

In contrast, the Google example below, the identification requirements include name, DOB, country, mobile phone number, email address and CAPTCHA response. While only two of these can be verified (email address and mobile number), the identification requirements are stricter than Wordpress. Google registration page.jpg


HTTP Proxy




Implement identification and verification requirements that correspond to the security requirements of the information the credentials protect.