Messages protected with WS_Security must use time stamps with creation and expiration times.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-222399APSC-DV-000190SV-222399r960759_ruleCCI-000068high
Description
The lack of time stamps could lead to the eventual replay of the message, leaving the application susceptible to replay events which may result in an immediate loss of confidentiality.
STIGDate
Application Security and Development Security Technical Implementation Guide2025-02-12

Related Frameworks

3 paths across 3 frameworks
NIST 800-531 mapping
  • DISA · 6 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1711 mapping
3.1.13
1.00
  • DISA · 6 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000068
1.00
  • DISA · 6 · disa_xccdf · related

Details

Check Text (C-222399r960759_chk)

Ask the application representative for the design document. Review the design document for web services using WS-Security tokens. If the application does not utilize WS-Security tokens, this check is not applicable. Examine the contents of a SOAP message using WS Security; all messages should contain time stamps, sequence numbers, and expiration. If messages using WS Security do not contain time stamps, sequence numbers, and expiration, this is a finding.

Fix Text (F-24058r493106_fix)

Design and configure applications using WS-Security messages to use time stamps with creation and expiration times and sequence numbers.