The application must destroy the session ID value and/or cookie on logoff or browser close.
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.
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 (F-24237r493643_fix)
Configure the application to destroy session ID cookies once the application session has terminated.