OpenControls Logo

STIG Viewer

STIGViewer Support

The application must not re-use or recycle session IDs.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-222582APSC-DV-002280SV-222582r1043180_ruleCCI-001664medium
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. Session identifiers are assigned to application users so they can be uniquely identified. This allows the user to customize their web application experience and also allows the developer to differentiate between users thereby providing the opportunity to customize the user’s features and functions. Once a user has logged out of the application or had their session terminated, their session IDs should not be re-used. Session IDs should also not be used for other purposes such as creating unique file names and they should also not be re-assigned to other users once the original user has logged out or otherwise quit the application. Allowing session ID reuse increases the risk of replay attacks. Session testing is a detailed undertaking and is usually done in the course of a web application vulnerability or penetration assessment.
STIGDate
Application Security and Development Security Technical Implementation Guide2025-09-09

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-09.2Unique System-Generated Session Identifiers
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (12) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AU-4(1)Transfer to Alternate Storage
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
SC-2Separation of System and User Functionality
1.00
SC-23(3)Unique System-generated Session Identifiers
1.00
SC-5Denial-of-service Protection
1.00
SC-8Transmission Confidentiality and Integrity
1.00
SC-8(2)Pre- and Post-transmission Handling
1.00

+2 more (top 10 by confidence shown)

CCI1 mapping
CCI-001664
1.00

Details

Check Text (C-222582r1043180_chk)

Review the application documentation and interview the application administrator to identify how the application generates user session IDs. Application session testing is required in order to verify this requirement. Request the latest application vulnerability or penetration test results. Verify the test configuration includes session handling vulnerability tests. If the application is re-using/copying the users existing session ID that was created on one system in order to maintain user state when traversing multiple application servers in the same domain, this is not a finding. If the session testing results indicate application session IDs are re-used after the user has logged out, this is a finding.

Fix Text (F-24241r493655_fix)

Design the application to not re-use session IDs.