Application Security and Development Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000001
Group -
The application must provide a capability to limit the number of logon sessions per user.
Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in li...Rule Medium Severity -
SRG-APP-000295
Group -
SRG-APP-000295
Group -
The application must automatically terminate the non-privileged user session and log off non-privileged users after a 15 minute idle time period has elapsed.
Leaving a user’s application session established for an indefinite period of time increases the risk of session hijacking. Session termination terminates an individual user's logical application s...Rule Medium Severity -
SRG-APP-000295
Group -
The application must automatically terminate the admin user session and log off admin users after a 10 minute idle time period is exceeded.
Leaving an admin user's application session established for an indefinite period of time increases the risk of session hijacking. Session termination terminates an individual user's logical applic...Rule Medium Severity -
SRG-APP-000296
Group -
Applications requiring user access authentication must provide a logoff capability for user initiated communication session.
If a user cannot explicitly end an application session, the session may remain open and be exploited by an attacker. Applications providing user access must provide the ability for users to manual...Rule Medium Severity -
SRG-APP-000297
Group -
The application must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions.
If a user is not explicitly notified that their application session has been terminated, they cannot be certain that their session did not remain open. Applications with a user access interface mus...Rule Low Severity -
SRG-APP-000311
Group -
SRG-APP-000313
Group -
The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in process.
Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions represe...Rule Medium Severity -
SRG-APP-000314
Group -
The application must associate organization-defined types of security attributes having organization-defined security attribute values with information in transmission.
Without the association of security attributes to information, there is no basis for the application to make security related access-control decisions. Security attributes are abstractions represe...Rule Medium Severity -
SRG-APP-000014
Group -
The application must implement DoD-approved encryption to protect the confidentiality of remote access sessions.
Without confidentiality protection mechanisms, unauthorized individuals may gain access to sensitive information via a remote access session. Remote access is access to DoD nonpublic information s...Rule Medium Severity -
SRG-APP-000015
Group -
SRG-APP-000015
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.
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 application must have a process, feature or function that prevents removal or disabling of emergency accounts.
Emergency accounts are administrator accounts which are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation...Rule Low Severity -
SRG-APP-000025
Group -
The application must automatically disable accounts after a 35 day period of account inactivity.
Attackers that are able to exploit an inactive account can potentially obtain and maintain undetected access to an application. Owners of inactive accounts will not notice if unauthorized access to...Rule Low Severity -
SRG-APP-000025
Group -
SRG-APP-000026
Group -
SRG-APP-000027
Group -
SRG-APP-000028
Group -
The application must automatically audit account disabling actions.
When application accounts are disabled, user accessibility is affected. Accounts are utilized for identifying individual application users or for identifying the application processes themselves. I...Rule Medium Severity -
SRG-APP-000029
Group -
SRG-APP-000291
Group
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.