III - Administrative Sensitive
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000015
<GroupDescription></GroupDescription>Group -
The application must implement cryptographic mechanisms to protect the integrity of remote access sessions.
<VulnDiscussion>Without integrity protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote acces...Rule Medium Severity -
SRG-APP-000015
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Digitally signed SOAP messages provide message integrity and authenticity of the signer of the message independent of the tra...Rule Medium Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
Messages protected with WS_Security must use time stamps with creation and expiration times.
<VulnDiscussion>The lack of time stamps could lead to the eventual replay of the message, leaving the application susceptible to replay event...Rule High Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
Validity periods must be verified on all application messages using WS-Security or SAML assertions.
<VulnDiscussion>When using WS-Security in SOAP messages, the application should check the validity of the time stamps with creation and expir...Rule High Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
The application must ensure each unique asserting party provides unique assertion ID references for each SAML assertion.
<VulnDiscussion>SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens c...Rule Medium Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
The application must ensure encrypted assertions, or equivalent confidentiality protections are used when assertion data is passed through an intermediary, and confidentiality of the assertion data is required when passing through the intermediary.
<VulnDiscussion>SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens ...Rule Medium Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
The application must use the NotOnOrAfter condition when using the SubjectConfirmation element in a SAML assertion.
<VulnDiscussion>SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens ...Rule High Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
The application must use both the NotBefore and NotOnOrAfter elements or OneTimeUse element when using the Conditions element in a SAML assertion.
<VulnDiscussion>SAML is a standard for exchanging authentication and authorization data between security domains. SAML uses security tokens ...Rule High Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>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.
<VulnDiscussion>Multiple <OneTimeUse> elements used in a SAML assertion can lead to elevation of privileges, if the application does no...Rule Medium Severity -
SRG-APP-000014
<GroupDescription></GroupDescription>Group -
The application must ensure messages are encrypted when the SessionIndex is tied to privacy data.
<VulnDiscussion>When the SessionIndex is tied to privacy data (e.g., attributes containing privacy data) the message should be encrypted. If ...Rule Medium Severity
Node 2
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.