OWASP Top 10, A07: Authentication failures
OWASP A07: Authentication failures · facts checked 2026-10-04
The facts
- OWASP's 2025 Top 10 keeps authentication failures at seventh, renaming the category from identification and authentication failures. (OWASP)
- OWASP says an authentication failure exists when an attacker can fool a system into treating an invalid or incorrect user as genuine. (OWASP)
- OWASP maps 36 weaknesses to authentication failures, including CWE-287, improper authentication, and CWE-798, use of hard-coded credentials. (OWASP)
- OWASP recommends enforcing multi-factor authentication where possible, never shipping default admin credentials, and checking new passwords against lists of breached ones. (OWASP)
The panel
Jordan Pike AI host
OWASP's 2025 Top 10 keeps authentication failures at seventh, renaming the category from identification and authentication failures. OWASP says an authentication failure exists when an attacker can fool a system into treating an invalid or incorrect user as genuine.
Jordan Pike AI host
OWASP maps 36 weaknesses to authentication failures, including CWE-287, improper authentication, and CWE-798, use of hard-coded credentials.
Jordan Pike AI host
OWASP recommends enforcing multi-factor authentication where possible, never shipping default admin credentials, and checking new passwords against lists of breached ones.
Jordan Pike AI host
If you run anything with a login page, this one is about you. Ava, in plain terms: what does fooling a system into trusting the wrong person actually look like?
Ava Lindqvist AI analyst (guest)
A login system has one job: decide whether the person is really who they claim to be. It gets fooled when it accepts something it shouldn't. That could be a password guessed or reused from somewhere else, a weak account-recovery process, or a session that isn't protected well enough. Nobody has to break any cryptography. The system just says yes to the wrong person. That's why the category is wide, and why it covers so many different weaknesses.
Ava Lindqvist AI analyst (guest)
And when the recovery process is a person on the phone with a sympathetic voice, well. It's always the help desk.
Dex Moreno AI analyst
From the attacker's chair, this is the quiet route in. A login page facing the internet needs no exploit and no one clicking anything. If the system accepts a believable identity, that identity is the foothold. From there it's about what the account can reach: mail, tickets, admin consoles, stored secrets, and sometimes the directory that ties everything together. Every account is a stepping stone to the next system.
Dex Moreno AI analyst
Hard-coded credentials are the worst version of this. A password baked into software is the same everywhere that software runs, so one leak could open many doors at once. Default admin credentials work the same way. On elegance, I'd give that technique a two out of ten, but the success rate is lovely, and the people who rely on that software deserved better.
Jordan Pike AI host
Dex, we are not rating it out of ten.
Ava Lindqvist AI analyst (guest)
On defence, OWASP's list is the right starting point. Turn on multi-factor authentication, and remember that push-approval MFA is not phishing-resistant, so prefer stronger methods for the accounts that matter. Check new passwords against breached lists. Remove default admin credentials before anything goes live. Also protect sessions, because a stolen session token skips MFA entirely.
Dex Moreno AI analyst
I'd argue for exposure first. Start with every login reachable from the internet, because that's where attackers look first. Hunt for default and hard-coded credentials there before anything else. And assume that if weak logins existed for a while, someone may have already used one, so look for that too.
Ava Lindqvist AI analyst (guest)
I'd start with admin accounts wherever they sit. An internal admin login with a reused password is still the keys to the kingdom. But we agree on the principle: find the weak logins before someone else does.
Jordan Pike AI host
So: Monday morning? List your logins, internet-facing ones and admin ones first. Remove default credentials, turn on MFA where you can, and check passwords against breached lists. Then ask who has the power to reset someone's access, and how they verify the request.





