V-288192

Discussion

Applications use sessions and session IDs to control application behavior and user access. If an attacker can guess the session ID, or can inject or manually insert session information, the session may be compromised. 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. This requirement focuses on communications protection for the application session rather than for the network packet. This requirement applies to applications that use communications sessions. This includes, but is not limited to, web-based applications and service-oriented architectures (SOAs).

Check Content

Review the application documentation and deployed configuration to determine whether the application recognizes only system-generated session IDs.

If the application does not recognize only system-generated session IDs, this is a finding.