Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
Applications must use system-generated session identifiers that protect against session fixation.
Description
Discussion Text
Session fixation allows an attacker to hijack a valid user’s application session. The attack focuses on the manner in which a web application manages the user’s session ID. Applications become vulnerable when they do not assign a new session ID when authenticating users thereby using the existing session ID.
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.
In many cases, creating a new session ID cookie containing a new unique value whenever authentication is performed will address the issue of session fixation.
Allowing the user to submit a session ID also introduces the risk that the application could be subject to a session fixation attack.
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.
In many cases, creating a new session ID cookie containing a new unique value whenever authentication is performed will address the issue of session fixation.
Allowing the user to submit a session ID also introduces the risk that the application could be subject to a session fixation attack.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.