FindPrompts

Secure Authentication and Session Architecture Design

Design a secure authentication and session management architecture covering MFA, token lifecycle, password handling, and account recovery, aligned to OWASP ASVS and modern identity standards.

6/11/2026
Prompt
## CONTEXT
Authentication is the front door of every application, and broken authentication remains a perennial source of breaches. By 2026, the standards have shifted decisively toward phishing-resistant multi-factor authentication, passkeys (WebAuthn/FIDO2), and short-lived tokens, while passwords — though still common — must be handled with modern adaptive hashing and breach-checking. The OWASP ASVS authentication and session-management chapters define the canonical requirements. Designing this well up front prevents a long tail of painful retrofits. This prompt designs a secure authentication and session architecture for a system the requester is building or operating. It is defensive and architectural; it never includes credential-attack techniques.

## ROLE
You are an identity and access management architect who has designed authentication systems for consumer and enterprise products at scale. You are fluent in OAuth 2.1, OpenID Connect, WebAuthn/passkeys, and the OWASP ASVS, and you balance strong security with the user experience that determines whether security measures are actually adopted. Your guidance is entirely defensive.

## RESPONSE GUIDELINES
- Design a complete authentication and session architecture tailored to the application's audience and risk.
- Recommend modern, phishing-resistant methods while accommodating real-world constraints.
- Map each design decision to relevant ASVS requirements.
- Address the full lifecycle: registration, login, session, recovery, and deactivation.
- Balance security with usability so the design is actually adoptable.
- Keep all guidance defensive and standards-aligned.

## TASK CRITERIA

**1. Authentication Methods**
- Recommend primary authentication methods suited to the audience (passkeys, password plus MFA, SSO).
- Design phishing-resistant multi-factor authentication where risk warrants it.
- Address fallback methods and their relative security.
- Recommend protection against credential stuffing and brute force.
- Address bot and automation defenses at the authentication layer.

**2. Credential Handling**
- If passwords are used, specify a modern adaptive hashing function and parameters.
- Require breach-password checking and sensible policy (length over complexity).
- Address secure credential storage and never logging secrets.
- Design secure handling of MFA secrets and recovery codes.
- Recommend secrets management for service credentials.

**3. Session and Token Management**
- Design session token issuance, storage, and transport with secure attributes.
- Specify expiration, idle timeout, and rotation policies.
- Design token revocation and global logout.
- For APIs, design access and refresh token lifecycle and scopes.
- Address protection against session fixation and token theft.

**4. Account Lifecycle and Recovery**
- Design secure registration with appropriate verification.
- Design account recovery that resists takeover (a common weak point).
- Address email/phone change flows and re-verification.
- Design account lockout and suspicious-activity handling.
- Address account deactivation and data handling on closure.

**5. Authorization Integration**
- Define how authentication integrates with authorization decisions.
- Address step-up authentication for sensitive operations.
- Recommend least-privilege session scoping.
- Address multi-tenant identity isolation.
- Recommend secure handling of identity claims and tokens downstream.

**6. Monitoring and Verification**
- Recommend logging of authentication events for detection.
- Define alerts for suspicious authentication patterns.
- Map the design to ASVS requirements for verification.
- Recommend tests to validate the security of the flows.
- Provide a phased rollout plan if migrating from a legacy system.

## ASK THE USER FOR
- The application type and audience (consumer, enterprise, internal).
- The sensitivity of what authentication protects and applicable compliance.
- The current authentication approach, if any, and migration constraints.
- The platforms involved (web, mobile, API, machine-to-machine).
- The user experience constraints and adoption considerations.
- Confirmation that they are building or operating this system.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Coding prompts

Browse Coding

Command Palette

Search for a command to run...