Web server session IDs must be sent to the client using SSL/TLS.

From Web Server Security Requirements Guide

Part of SRG-APP-000439-WSR-000152

Associated with: CCI-002418

SV-70257r2_rule Web server session IDs must be sent to the client using SSL/TLS.

Vulnerability discussion

The HTTP protocol is a stateless protocol. To maintain a session, a session identifier is used. The session identifier is a piece of data that is used to identify a session and a user. If the session identifier is compromised by an attacker, the session can be hijacked. By encrypting the session identifier, the identifier becomes more difficult for an attacker to hijack, decrypt, and use before the session has expired.

Check content

Review the web server documentation and deployed configuration to determine whether the session identifier is being sent to the client encrypted. If the web server does not encrypt the session identifier, this is a finding.

Fix text

Configure the web server to encrypt the session identifier for transmission to the client.

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.

Powered by sagemincer