19.09.2017 Views

the-web-application-hackers-handbook

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 21 n A Web Application Hacker’s Methodology 805<br />

4 Test <strong>the</strong> Au<strong>the</strong>ntication Mechanism<br />

4.1. Understand <strong>the</strong> mechanism<br />

Data attacks<br />

Special functions<br />

Credential handling<br />

Au<strong>the</strong>ntication<br />

logic<br />

4.2. Test password<br />

quality<br />

4.5. Test account<br />

recovery<br />

4.8. Test username<br />

uniqueness<br />

4.13.1. Test for<br />

fail-open logic<br />

4.3. Test for<br />

username<br />

enumeration<br />

4.6. Test “remember<br />

me”<br />

4.9. Test credential<br />

predictability<br />

4.13.2. Test<br />

multistage<br />

processes<br />

4.4. Test for<br />

password guessing<br />

4.7. Test<br />

impersonation<br />

functions<br />

4.10. Check for<br />

unsafe transmission<br />

4.11. Check for<br />

unsafe distribution<br />

4.12. Check for<br />

insecure storage<br />

4.14. Exploit vulnerabilities<br />

Figure 21-5: Testing <strong>the</strong> au<strong>the</strong>ntication mechanism<br />

4.1 Understand <strong>the</strong> Mechanism<br />

4.1.1 Establish <strong>the</strong> au<strong>the</strong>ntication technologies in use (for example, forms,<br />

certificates, or multifactor).<br />

4.1.2 Locate all <strong>the</strong> au<strong>the</strong>ntication-related functionality (including login,<br />

registration, account recovery, and so on).<br />

4.1.3 If <strong>the</strong> <strong>application</strong> does not implement an automated self-registration<br />

mechanism, determine whe<strong>the</strong>r any o<strong>the</strong>r means exists of obtaining<br />

several user accounts.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!