V-288193

Discussion

Sequentially generated session identifiers (IDs) can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session IDs helps to protect against brute-force attacks to determine future session 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. The DRBGs Hash_DRBG, HMAC_DRBG, and CTR_DRBG are recommended for use with RNGs. This is applicable to devices that use a web interface for device management.

Check Content

Review the application documentation and deployed configuration to determine whether the application generates unique session identifiers using a FIPS-validated RNG based on the DRBG algorithm.

If the application does not generate unique session identifiers using a FIPS-validated RNG based on the DRBG algorithm, this is a finding.