Back to overview

Authorization 4

Once an authorization failure is detected, access needs to be blocked. It is also useful to log (associated with the user's identity if possible) and flag these as possibly malicious activity for further analysis, or as input for application intrusion detection systems.

NB: the key concept for this card is allowing access, even though authorization checks were undertaken and detected a failure. See AT 8 for the similar authentication failure.

How to play?

Kelly can bypass authorization controls because they do not fail securely (i.e. they default to allowing access)


Owasp ASVS (4.0): 4.1.5

Capec: 122

Owasp SCP: 79,80

Owasp Appsensor:

Safecode: 8,10,11

ASVS (4.0) Cheatsheetseries Index

ASVS V4.1 - General Access Control Design


Privilege escalation

Password Guessing/Brute Force Attacks

Insider Threats

Social engineering attack

Session Hijacking (Man-in-the-Middle)

Loading comments 0%

Github logo View source on GitHub

Provided by dotNET lab

This website is created, hosted and provided by dotNET lab. dotNET lab provides training and guidance on secure software development. Contact us to get in touch!

OWASP Cornucopia

OWASP Cornucopia is originally created by Colin Watson. It is open source and can be downloaded free of charge from the OWASP website. It is is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. OWASP does not endorse or recommend commercial products or services. OWASP Cornucopia is licensed under the Creative Commons Attribution-ShareAlike 3.0 license and is © 2012-2016 OWASP Foundation.