Back to overview

Authentication 8

Once an authentication 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 permitting access, even though authentication checks were undertaken and detected a failure. See AT 4 for the similar authorization failure.

How to play?

Kate can bypass authentication because it does not fail secure (i.e. it defaults to allowing unauthenticated access)


Owasp ASVS (4.0): 4.1.5

Capec: 115

Owasp SCP: 28

Owasp Appsensor:

Safecode: 28

ASVS (4.0) Cheatsheetseries Index

ASVS V4.1 - General Access Control Design


SQL Injection

Cross-Site Scripting (XSS)

(Session) Data tampering

Privilege escalation

Password Guessing/Brute Force Attacks

Account Takeover (ATO) Attacks

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.