Applications making SAML assertions must use FIPS-approved random numbers in the generation of SessionIndex in the SAML element AuthnStatement.

From Application Security and Development Security Technical Implementation Guide

Part of SRG-APP-000514

Associated with: CCI-002450

SV-84819r1_rule Applications making SAML assertions must use FIPS-approved random numbers in the generation of SessionIndex in the SAML element AuthnStatement.

Vulnerability discussion

A predictable SessionIndex could lead to an attacker computing a future SessionIndex, thereby, possibly compromising the application.Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.

Check content

Interview the system administrator, review the application components, and the application requirements to determine if the application uses SAML assertions. If the application does not use SAML assertions, the requirement is not applicable. Review the application documentation and interview he application administrator to identify the cryptographic modules used by the application. Access the NIST site to determine if the cryptographic modules used by the application have been FIPS-validated. http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm If the application is using cryptographic modules that are not FIPS-validated when generating the SessionIndex in the SAML AuthnStatement, this is a finding.

Fix text

Configure the application to use a FIPS-validated cryptographic module.

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