Owasp Auth Failures
Authentication systems must implement: account lockout or exponential backoff after failed attempts, multi-factor authentication for sensitive operations, secure session management (HTTPOnly + Secure cookies, short-lived…
$ prime install @community/principle-owasp-auth-failures Projection
Always in _index.xml · the agent never has to ask for this.
OwaspAuthFailures [principle] v1.0.0
OWASP Top 10 A07:2021 (formerly Broken Authentication) — identification and authentication failures that allow attackers to assume other users' identities, temporarily or permanently.
Authentication systems must implement: account lockout or exponential backoff after failed attempts, multi-factor authentication for sensitive operations, secure session management (HTTPOnly + Secure cookies, short-lived tokens, server-side session invalidation on logout), and credential breach detection via HaveIBeenPwned API or similar.
Loaded when retrieval picks the atom as adjacent / supporting.
OwaspAuthFailures [principle] v1.0.0
OWASP Top 10 A07:2021 (formerly Broken Authentication) — identification and authentication failures that allow attackers to assume other users' identities, temporarily or permanently.
Authentication systems must implement: account lockout or exponential backoff after failed attempts, multi-factor authentication for sensitive operations, secure session management (HTTPOnly + Secure cookies, short-lived tokens, server-side session invalidation on logout), and credential breach detection via HaveIBeenPwned API or similar.
Attributed To
OWASP Foundation, Top 10 2021
Applies To
- Login form brute force and credential stuffing protection
- Password reset and account recovery flows
- Session token generation, storage, and invalidation
- Multi-factor authentication enrollment and bypass
- Remember-me token security and expiration
- OAuth/OIDC implementation (state parameter CSRF, redirect_uri validation)
Counter Examples
- Rockstar Games 2022: credential stuffing attack via an API endpoint with no rate limiting — attackers used leaked passwords from other sites to compromise GTA accounts.
- Password reset that sends a token as a GET parameter which lands in server access logs, Referer headers, and browser history — token remains valid for 7 days.
- JWT HS256 with
alg: noneaccepted by server — attacker strips signature, sets alg to none, and server accepts unsigned token as valid (CVE-2015-9235 and variants).
Loaded when retrieval picks the atom as a focal / direct hit.
OwaspAuthFailures [principle] v1.0.0
OWASP Top 10 A07:2021 (formerly Broken Authentication) — identification and authentication failures that allow attackers to assume other users' identities, temporarily or permanently.
Authentication systems must implement: account lockout or exponential backoff after failed attempts, multi-factor authentication for sensitive operations, secure session management (HTTPOnly + Secure cookies, short-lived tokens, server-side session invalidation on logout), and credential breach detection via HaveIBeenPwned API or similar.
Attributed To
OWASP Foundation, Top 10 2021
Applies To
- Login form brute force and credential stuffing protection
- Password reset and account recovery flows
- Session token generation, storage, and invalidation
- Multi-factor authentication enrollment and bypass
- Remember-me token security and expiration
- OAuth/OIDC implementation (state parameter CSRF, redirect_uri validation)
Counter Examples
- Rockstar Games 2022: credential stuffing attack via an API endpoint with no rate limiting — attackers used leaked passwords from other sites to compromise GTA accounts.
- Password reset that sends a token as a GET parameter which lands in server access logs, Referer headers, and browser history — token remains valid for 7 days.
- JWT HS256 with
alg: noneaccepted by server — attacker strips signature, sets alg to none, and server accepts unsigned token as valid (CVE-2015-9235 and variants).
Sources
Examples
- Okta: hardware FIDO2/WebAuthn tokens + phishing-resistant MFA — authenticator-bound credentials cannot be replayed even if intercepted.
- Google: suspicious login detection cross-references login IP, device fingerprint, and behavioral baseline — triggers step-up auth automatically.
- Auth0/Clerk: breached password detection using HaveIBeenPwned k-anonymity API at registration and login — blocks known-compromised passwords without storing or transmitting the plaintext.
- GitHub: mandatory 2FA for all contributors to critical open-source projects (npm ecosystem, etc.) — enforced at the platform level since 2023.
Source
- https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/
- Verizon DBIR 2023: 49% of breaches involved credentials; credential stuffing attacks use lists of billions of leaked username/password pairs.
- Troy Hunt / HaveIBeenPwned: 12+ billion breached accounts indexed; k-anonymity API allows checking passwords without sending the actual password.
Source
prime-system/examples/frontend-design/primes/compiled/@community/principle-owasp-auth-failures/atom.yaml