UCF STIG Viewer Logo

Applications must not use URL embedded session IDs.


Overview

Finding ID Version Rule ID IA Controls Severity
V-70213 APSC-DV-002270 SV-84835r1_rule Medium
Description
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. Using a session ID that is copied to the URL introduces the risks that the session ID information will be written to log files, made available in browser history files, or made publicly available within the URL. Using cookies to establish session ID information is desired.
STIG Date
Application Security and Development Security Technical Implementation Guide 2017-01-09

Details

Check Text ( C-70689r1_chk )
Review the application documentation and interview the application administrator.

Identify how the application generates session IDs.

If using a web development framework, ask the application administrator to provide details on the framework's session configuration.

Review the framework configuration setting to determine how the session identifiers are created.

Identify any compensating controls that may be leveraged to minimize risk to user sessions.

If the framework or the application is configured to transmit cookies within the URL or via URL rewriting, or if the session ID is created using a GET method and there are no compensating controls configured to address user session security, this is a finding.
Fix Text (F-76449r1_fix)
Configure the application to transmit session ID information via cookies.