The application must ensure messages are encrypted when the SessionIndex is tied to privacy data.

From Application Security and Development Security Technical Implementation Guide

Associated with: CCI-000068

SV-83915r1_rule The application must ensure messages are encrypted when the SessionIndex is tied to privacy data.

Vulnerability discussion

When the SessionIndex is tied to privacy data (e.g., attributes containing privacy data) the message should be encrypted. If the message is not encrypted there is the possibility of compromise of privacy data.

Check content

Ask the application representative for the design document. Review the design document for web services using SAML assertions. If the application does not utilize SAML assertions, this check is not applicable. Examine the contents of a SOAP message using a SessionIndex in the SAML element AuthnStatement. Verify the information which is tied to the SessionIndex. If the SessionIndex is tied to privacy information, and it is not encrypted, this is a finding.

Fix text

Encrypt messages when the SessionIndex is tied to privacy data.

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.