Authentication and session audit

Inspect login, recovery, session lifecycle, and cookie controls from supplied evidence.

Customize the recipe

0/1500 characters

Prompt preview

# Authentication and session audit

Inspect login, recovery, session lifecycle, and cookie controls from supplied evidence.

## Read-only scope
Review only the authorized app, site, server, or local source named or supplied by the user. Work from provided code, configuration, redacted exports, and completed test results. Use URLs and hostnames as scope identifiers. Request the missing artifacts if evidence is insufficient.

Use existing offline, read-only analysis on those artifacts. Exclude live probing, vulnerability reproduction, exploit payloads, credential testing, new load generation, and changes to the target or its files.

## Tools and setup · Universal
Use the linked resources as references for interpreting the supplied material. Follow the read-only scope when a linked workflow describes other actions.

- [Security Best Practices](https://github.com/openai/skills/blob/main/skills/.curated/security-best-practices/SKILL.md) (Skill) — Use the language-specific guidance to identify insecure defaults and review supplied code.
- [OWASP Cheat Sheet Series](https://github.com/OWASP/CheatSheetSeries) (Repository) — Reference defensive guidance for authentication, sessions, data handling, and secure configuration.
- [OWASP ASVS](https://github.com/OWASP/ASVS) (Repository) — Map observed web security controls to relevant verification requirements.

## Workflow
Read the available identity configuration, authentication flows, cookie attributes, and redacted test results. Review session rotation, expiry, termination, password reset policy, and privileged access requirements.

## Deliverable
A session and identity control review with prioritized policy and implementation findings.
- Minimalism: Apply this style to report presentation only. Plain Markdown is sufficient.

## Acceptance checks
- [ ] Distinguish browser cookie settings from server-side session enforcement.
- [ ] Cite the evidence for each claimed login, renewal, logout, or recovery control.
- [ ] Give each finding a severity, confidence, affected component, evidence reference, impact, and recommended mitigation. Explicitly list unverified controls and gaps.
- [ ] Redact credentials, tokens, personal data, and sensitive values in the report.

Recipe resources

Source, setup, and compatibility details.