UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The application must use the NotOnOrAfter condition when using the SubjectConfirmation element in a SAML assertion.


Overview

Finding ID Version Rule ID IA Controls Severity
V-222403 APSC-DV-000230 SV-222403r879519_rule High
Description
SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens containing assertions to pass information about a principal (usually an end user) between a SAML authority, (identity provider), and a SAML consumer, (service provider). SAML assertions are usually made about a subject, (user) represented by the <Subject> element. When a SAML assertion is used with a <SubjectConfirmation> element, a begin and end time for the <SubjectConfirmation> should be set to prevent reuse of the message at a later time. Not setting a specific time period for the <SubjectConfirmation>, may grant immediate access to an attacker and result in an immediate loss of confidentiality.
STIG Date
Application Security and Development Security Technical Implementation Guide 2023-06-08

Details

Check Text ( C-24073r493117_chk )
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 the element. All messages should contain the element. This can be accomplished if the application allows the ability to view XML messages or via a protocol analyzer like Wireshark.

If SOAP messages do not contain elements, this is a finding.
Fix Text (F-24062r493118_fix)
Design and configure the application to use the condition when using the element in a SAML assertion.