The application must destroy the session ID value and/or cookie on logoff or browser close.

From Application Security and Development Security Technical Implementation Guide

Associated with: CCI-001185

SV-84829r1_rule The application must destroy the session ID value and/or cookie on logoff or browser close.

Vulnerability discussion

Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever possible it is recommended to utilize the provided session management framework.Session cookies contain application session information that can be used to impersonate the web application user or hijack their application session. Once the user's session has terminated, these session IDs must be destroyed and not reused.

Check content

Review the application documentation and interview the application administrator. Identify how the application destroys session IDs. If using a web development framework, ask the application administrator to provide details on the framework's session configuration. Review framework configuration setting to determine how the session identifiers are destroyed. Review the client system and using a browser or other tool capable of viewing client cookies, identify cookies set by the application and verify that application session ID cookies are destroyed once the user has logged off or the browser has closed. If the session IDs and associated cookies are not destroyed on logoff or browser close, this is a finding.

Fix text

Configure the application to destroy session ID cookies once the application session has terminated.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.