security-review-owasp-authentication-patterns

Review authentication flows for OWASP-aligned weaknesses with evidence and severity.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-authentication-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review-owasp-authentication-patterns
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-authentication-patterns
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-authentication-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers find authentication-pattern weaknesses that can lead to account takeover, identity confusion, privilege escalation, or recovery bypass.

Core Features & Use Cases

  • End-to-End Auth Review: Trace identity proof, credential handling, session behavior, and trust propagation across services and boundaries.
  • OWASP-Aligned Findings: Evaluate recovery, step-up, logging, throttling, and failure handling against authentication guidance.
  • Use Case: Review a login, account recovery, or service-to-service trust flow and identify confirmed weaknesses with evidence, severity, and remediation.

Quick Start

Use the security-review-owasp-authentication-patterns skill to review the selected authentication flow and report confirmed findings, review gaps, and passed checks.

Frequently Asked Questions about security-review-owasp-authentication-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review authentication flows for account takeover and privilege escalation risks?▼

Reviewing authentication flows for account takeover involves tracing identity proof, credential handling, session behavior, and trust propagation to identify confirmed weaknesses with evidence and severity aligned to OWASP guidance.

What authentication patterns are vulnerable to identity confusion and recovery bypass?▼

Authentication patterns vulnerable to identity confusion include enrollment, recovery, session, step-up, and trust-propagation flows where failure handling, throttling, and logging lack proper control checks against OWASP authentication guidance.

How do I check service-to-service trust boundaries for privilege escalation weaknesses?▼

Checking trust boundaries for privilege escalation requires tracing trust propagation across services and boundaries to find evidence-backed weaknesses in identity proof, session behavior, and credential handling within configuration and code.

Can I use this approach to review step-up authentication and session management flows?▼

Yes, reviewing step-up authentication and session management evaluates recovery, logging, throttling, and failure handling against OWASP authentication guidance to identify weaknesses enabling account takeover or privilege escalation.

What do I need to conduct an end-to-end security review of authentication mechanisms?▼

Conducting an end-to-end security review of authentication mechanisms requires access to code, configuration, tests, and documentation to trace identity proof and trust propagation, reporting passed checks, review gaps, and confirmed findings.

Why does my account recovery flow fail OWASP authentication security checks?▼

Account recovery flows fail OWASP authentication security checks when they contain weaknesses in failure handling, throttling, or trust propagation that enable account takeover, requiring evidence-backed findings with clear severity for remediation.