Skip to content

Application Security and Development Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-APP-000411

    <GroupDescription></GroupDescription>
    Group
  • Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the integrity of non-local maintenance and diagnostic communications.

    &lt;VulnDiscussion&gt;Privileged access contains control and configuration information which is particularly sensitive, so additional protections a...
    Rule Medium Severity
  • SRG-APP-000412

    <GroupDescription></GroupDescription>
    Group
  • Applications used for non-local maintenance sessions must implement cryptographic mechanisms to protect the confidentiality of non-local maintenance and diagnostic communications.

    &lt;VulnDiscussion&gt;Privileged access contains control and configuration information which is particularly sensitive, so additional protections a...
    Rule Medium Severity
  • SRG-APP-000413

    <GroupDescription></GroupDescription>
    Group
  • Applications used for non-local maintenance sessions must verify remote disconnection at the termination of non-local maintenance and diagnostic sessions.

    &lt;VulnDiscussion&gt;Non-local maintenance and diagnostic activities are those activities conducted by individuals communicating through a network...
    Rule Medium Severity
  • SRG-APP-000185

    <GroupDescription></GroupDescription>
    Group
  • The application must employ strong authenticators in the establishment of non-local maintenance and diagnostic sessions.

    &lt;VulnDiscussion&gt;If maintenance tools are used by unauthorized personnel, they may accidentally or intentionally damage or compromise the syst...
    Rule Medium Severity
  • SRG-APP-000186

    <GroupDescription></GroupDescription>
    Group
  • The application must terminate all sessions and network connections when non-local maintenance is completed.

    &lt;VulnDiscussion&gt;If a maintenance session or connection remains open after maintenance is completed, it may be hijacked by an attacker and use...
    Rule Medium Severity
  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
  • The application must not be vulnerable to race conditions.

    &lt;VulnDiscussion&gt;A race condition is a timing event within an application that can become a security vulnerability. A race condition can occu...
    Rule Medium Severity
  • SRG-APP-000190

    <GroupDescription></GroupDescription>
    Group
  • If the application contains classified data, a Security Classification Guide must exist containing data elements and their classification.

    &lt;VulnDiscussion&gt;Without a classification guide the marking, storage, and output media of classified material can be inadvertently mixed with ...
    Rule Medium Severity
  • The application must terminate all network connections associated with a communications session at the end of the session.

    &lt;VulnDiscussion&gt;Networked applications routinely open connections to and from other systems as part of their design and function. When conne...
    Rule Medium Severity
  • SRG-APP-000514

    <GroupDescription></GroupDescription>
    Group
  • The application must utilize FIPS-validated cryptographic modules when signing application components.

    &lt;VulnDiscussion&gt;Applications that distribute components of the application must sign the components to provide an identity assurance to consu...
    Rule Medium Severity
  • SRG-APP-000514

    <GroupDescription></GroupDescription>
    Group
  • The application must utilize FIPS-validated cryptographic modules when generating cryptographic hashes.

    &lt;VulnDiscussion&gt;Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The applicatio...
    Rule Medium Severity
  • SRG-APP-000514

    <GroupDescription></GroupDescription>
    Group
  • The application must utilize FIPS-validated cryptographic modules when protecting unclassified information that requires cryptographic protection.

    &lt;VulnDiscussion&gt;Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The applicatio...
    Rule Medium Severity
  • SRG-APP-000514

    <GroupDescription></GroupDescription>
    Group
  • Applications making SAML assertions must use FIPS-approved random numbers in the generation of SessionIndex in the SAML element AuthnStatement.

    &lt;VulnDiscussion&gt;A predictable SessionIndex could lead to an attacker computing a future SessionIndex, thereby, possibly compromising the appl...
    Rule Medium Severity
  • SRG-APP-000211

    <GroupDescription></GroupDescription>
    Group
  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
  • The application user interface must be either physically or logically separated from data storage and management interfaces.

    &lt;VulnDiscussion&gt;Application management functionality includes functions necessary for administration and requires privileged user access. All...
    Rule Medium Severity
  • SRG-APP-000219

    <GroupDescription></GroupDescription>
    Group
  • The application must set the HTTPOnly flag on session cookies.

    &lt;VulnDiscussion&gt;HTTPOnly is a flag included in a Set-Cookie HTTP response header. If the HTTPOnly flag is included in the HTTP response heade...
    Rule Medium Severity
  • SRG-APP-000219

    <GroupDescription></GroupDescription>
    Group
  • The application must set the secure flag on session cookies.

    &lt;VulnDiscussion&gt;Many web development frameworks such as PHP, .NET, ASP as well as application servers include their own mechanisms for sessio...
    Rule Medium Severity
  • SRG-APP-000219

    <GroupDescription></GroupDescription>
    Group
  • The application must not expose session IDs.

    &lt;VulnDiscussion&gt;Authenticity protection provides protection against man-in-the-middle attacks/session hijacking and the insertion of false in...
    Rule High Severity
  • SRG-APP-000220

    <GroupDescription></GroupDescription>
    Group
  • Applications must use system-generated session identifiers that protect against session fixation.

    &lt;VulnDiscussion&gt;Session fixation allows an attacker to hijack a valid user’s application session. The attack focuses on the manner in which a...
    Rule Medium Severity
  • SRG-APP-000223

    <GroupDescription></GroupDescription>
    Group
  • Applications must validate session identifiers.

    &lt;VulnDiscussion&gt;Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever poss...
    Rule Medium Severity
  • SRG-APP-000223

    <GroupDescription></GroupDescription>
    Group
  • Applications must not use URL embedded session IDs.

    &lt;VulnDiscussion&gt;Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever poss...
    Rule Medium Severity
  • SRG-APP-000223

    <GroupDescription></GroupDescription>
    Group
  • The application must not re-use or recycle session IDs.

    &lt;VulnDiscussion&gt;Many web development frameworks such as PHP, .NET, and ASP include their own mechanisms for session management. Whenever poss...
    Rule Medium Severity
  • SRG-APP-000224

    <GroupDescription></GroupDescription>
    Group
  • The application must use the Federal Information Processing Standard (FIPS) 140-2-validated cryptographic modules and random number generator if the application implements encryption, key exchange, digital signature, and hash functionality.

    &lt;VulnDiscussion&gt;Sequentially generated session IDs can be easily guessed by an attacker. Employing the concept of randomness in the generatio...
    Rule Medium Severity
  • SRG-APP-000427

    <GroupDescription></GroupDescription>
    Group
  • The application must only allow the use of DoD-approved certificate authorities for verification of the establishment of protected sessions.

    &lt;VulnDiscussion&gt;Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that se...
    Rule Medium Severity
  • SRG-APP-000225

    <GroupDescription></GroupDescription>
    Group
  • The application must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

    &lt;VulnDiscussion&gt;Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized acces...
    Rule High Severity
  • SRG-APP-000226

    <GroupDescription></GroupDescription>
    Group
  • In the event of a system failure, applications must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

    &lt;VulnDiscussion&gt;Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Fa...
    Rule Medium Severity
  • SRG-APP-000231

    <GroupDescription></GroupDescription>
    Group
  • The application must protect the confidentiality and integrity of stored information when required by DoD policy or the information owner.

    &lt;VulnDiscussion&gt;Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive and...
    Rule Medium Severity

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