The DataPower Gateway must generate unique session identifiers using a FIPS 140-2 approved random number generator.

From IBM DataPower Network Device Management Security Technical Implementation Guide

Part of SRG-APP-000224-NDM-000270

Associated with: CCI-001188

SV-79599r1_rule The DataPower Gateway must generate unique session identifiers using a FIPS 140-2 approved random number generator.

Vulnerability discussion

Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generation of unique session identifiers 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.This requirement is applicable to devices that use a web interface for device management.

Check content

From the web interface for DataPower device management, verify that the DataPower Gateway Cryptographic Mode is Set to FIPS 140-2 Level 1; Status >> Crypto >> Cryptographic Mode Status. If it is not set to FIPS 140-2, this is a finding. Then, verify that the session identifiers (TIDs) in the System Log are random: Status >> View Logs >> Systems Logs. If they are not random, this is a finding.

Fix text

From the DataPower command line, enter "use-fips on" to configure DataPower to generate unique session identifiers using a FIPS 140-2 approved random number generator. From the web interface, use "Set Cryptographic Mode" (Administration >> Miscellaneous >> Crypto Tools, Set Cryptographic Mode tab) to set the appliance to "FIPS 140-2 Level 1" mode. This will achieve NIST SP800-131a compliance.

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