Authentication vs Identification: Terminology Changes
You'll learn why OWASP changed "Broken Authentication" to "Identification and Authentication Failures" in 2021 and what that shift means for secure coding.
Why the Name Changed
In the 2017 OWASP Top 10, the second-ranked vulnerability was called "Broken Authentication." By 2021, it became "Identification and Authentication Failures." This wasn't just wordsmithing—it reflected a more complete understanding of how identity security actually fails.
Authentication is proving you are who you claim to be (showing your passport). Identification is establishing which identity you're claiming (stating your name). The old name focused only on the proof part, but ignored the equally critical step of correctly identifying who's even trying to authenticate.
What This Covers Now
The expanded terminology acknowledges that vulnerabilities occur at both stages:
- Identification failures: username enumeration, account discovery, predictable account IDs, user impersonation
- Authentication failures: weak passwords, broken session management, missing MFA, credential stuffing
Think of a hotel check-in: identification is looking up your reservation by name; authentication is verifying your ID matches. If the desk clerk accepts a fake name (identification failure) or doesn't check your ID properly (authentication failure), security breaks down.
Why It Matters
This terminology shift reminds developers that securing identity isn't just about passwords and tokens—it starts the moment you ask "who are you?" Both steps need protection against enumeration attacks, brute force, and bypasses.
Key Takeaway: The 2021 change from "Broken Authentication" to "Identification and Authentication Failures" emphasizes that securing user identity requires protecting both who claims access and how they prove it.