vulns.co
/
GKData.io MCP and API Buy me a coffee

OWASP Cheat Sheet Series

OWASP Session Management: privilege-transition integrity

OWASP explains why applications should issue session identifiers themselves and replace them at login or other privilege changes. Previous identifiers must be retired, and anonymous tracking kept separate from authenticated access. When several cookies represent one session, the application must also validate their relationship.

Open the referenceImplementation GuideReviewed 2026-10-03

How to use this reference

Model login and privilege changes as explicit session-state transitions, with server-controlled identity and authority bindings. Document which credentials represent anonymous and authenticated state and how superseded state loses authority.

Before reading

  • Basic HTTP cookie and authentication concepts

Context and limits

  • Renewing a session identifier does not establish authorization for every resource or action; access decisions remain a separate responsibility.
  • Official implementation guidance, not a product-specific finding, current-exposure claim or testing authorization.

Sources

  1. Session Management Cheat SheetOWASP Cheat Sheet Series · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software