Skip to content

Application Security and Development Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • Applications with SOAP messages requiring integrity must include the following message elements:-Message ID-Service Request-Timestamp-SAML Assertion (optionally included in messages) and all elements of the message must be digitally signed.

    Digitally signed SOAP messages provide message integrity and authenticity of the signer of the message independent of the transport layer. Service requests may be intercepted and changed in transit...
    Rule Medium Severity
  • SRG-APP-000014

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

    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.
    Rule High Severity
  • SRG-APP-000014

    Group
  • Validity periods must be verified on all application messages using WS-Security or SAML assertions.

    When using WS-Security in SOAP messages, the application should check the validity of the time stamps with creation and expiration times. Time stamps that are not validated may lead to a replay eve...
    Rule High Severity
  • SRG-APP-000014

    Group
  • The application must ensure each unique asserting party provides unique assertion ID references for each SAML assertion.

    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 e...
    Rule Medium Severity
  • SRG-APP-000014

    Group
  • SRG-APP-000014

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

    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 ...
    Rule High Severity
  • SRG-APP-000014

    Group
  • The application must use both the NotBefore and NotOnOrAfter elements or OneTimeUse element when using the Conditions element in a SAML assertion.

    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 ...
    Rule High Severity
  • SRG-APP-000014

    Group
  • The application must ensure if a OneTimeUse element is used in an assertion, there is only one of the same used in the Conditions element portion of an assertion.

    Multiple <OneTimeUse> elements used in a SAML assertion can lead to elevation of privileges, if the application does not process SAML assertions correctly.
    Rule Medium Severity
  • SRG-APP-000014

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

    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 p...
    Rule Medium Severity
  • SRG-APP-000023

    Group
  • SRG-APP-000317

    Group
  • SRG-APP-000024

    Group
  • SRG-APP-000516

    Group

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules