Sentry must generate unique session identifiers using a FIPS 140-2 approved random number generator.
An XCCDF Rule
Description
<VulnDiscussion>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.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-250997r1028235_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Configure the Sentry Server to use a FIPS 140-2-validated cryptographic module.
On the Sentry console, do the following:
1. SSH to Sentry Server from any SSH client.
2. Enter the administrator credentials set at Sentry installation.
3. Enter "enable".