The ALG must recognize only system-generated session identifiers.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-204959	SRG-NET-000233	SRG-NET-000233-ALG-000115	SV-204959r396012_rule	2024-12-04	2

Description
Network elements (depending on function) utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier, or can inject or manually insert session information, the valid user's application session can 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.

Description

Network elements (depending on function) utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier, or can inject or manually insert session information, the valid user's application session can 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.

ℹ️ Check
Verify the ALG recognizes only system-generated session identifiers. If the ALG does not recognize only system-generated session identifiers, this is a finding.

✔️ Fix
Configure ALG to recognize only system-generated session identifiers.