The application server must recognize only system-generated session identifiers.

From Application Server Security Requirements Guide

Associated with: CCI-001664

SV-46708r3_rule The application server must recognize only system-generated session identifiers.

Vulnerability discussion

This requirement focuses on communications protection at the application session, versus network packet level. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted.Unique session IDs are the opposite of sequentially generated session IDs which can be easily guessed by an attacker. Unique session identifiers help to reduce predictability of said identifiers.Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions.

Check content

Review the application server configuration to determine if the application server recognizes only system-generated session identifiers. If the application server does not recognize only system-generated session identifiers, this is a finding.

Fix text

Design the application server to recognize only system-generated session identifiers.

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.