Skip to content

Database Security Requirements Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-APP-000172

    <GroupDescription></GroupDescription>
    Group
  • If passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be us...
    Rule High Severity
  • SRG-APP-000175

    <GroupDescription></GroupDescription>
    Group
  • The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. A certificate’s certification path is the path from th...
    Rule Medium Severity
  • SRG-APP-000176

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

    &lt;VulnDiscussion&gt;One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers bas...
    Rule Medium Severity
  • SRG-APP-000225

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by re...
    Rule High Severity
  • SRG-APP-000177

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must map the PKI-authenticated identity to an associated user account.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be m...
    Rule Medium Severity
  • SRG-APP-000178

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Normally, with PKI authentication, the interaction wit...
    Rule High Severity
  • SRG-APP-000179

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.

    &lt;VulnDiscussion&gt;Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures ...
    Rule High Severity
  • SRG-APP-000180

    <GroupDescription></GroupDescription>
    Group
  • Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.

    &lt;VulnDiscussion&gt;Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. D...
    Rule Medium Severity
  • SRG-APP-000243

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

    &lt;VulnDiscussion&gt;Non-organizational users include all information system users other than organizational users, which include organizational e...
    Rule Medium Severity
  • SRG-APP-000211

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must separate user functionality (including user interface services) from database management functionality.

    &lt;VulnDiscussion&gt;Information system management functionality includes functions necessary to administer databases, network components, worksta...
    Rule Medium Severity
  • SRG-APP-000220

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must invalidate session identifiers upon user logout or other session termination.

    &lt;VulnDiscussion&gt;Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and contin...
    Rule Medium Severity
  • SRG-APP-000223

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must recognize only system-generated session identifiers.

    &lt;VulnDiscussion&gt;DBMSs utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the ...
    Rule Medium Severity
  • SRG-APP-000224

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

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

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

    <GroupDescription></GroupDescription>
    Group
  • In the event of a system failure, the DBMS 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. F...
    Rule Medium Severity
  • SRG-APP-000231

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must protect the confidentiality and integrity of all information at rest.

    &lt;VulnDiscussion&gt;This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers...
    Rule High Severity
  • SRG-APP-000233

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must isolate security functions from non-security functions.

    &lt;VulnDiscussion&gt;An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform...
    Rule Medium Severity
  • SRG-APP-000243

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

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must check the validity of all data inputs except those specifically identified by the organization.

    &lt;VulnDiscussion&gt;Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application ...
    Rule Medium Severity
  • SRG-APP-000251

    <GroupDescription></GroupDescription>
    Group
  • The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.

    &lt;VulnDiscussion&gt;With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection...
    Rule Medium Severity
  • SRG-APP-000251

    <GroupDescription></GroupDescription>
    Group
  • The DBMS and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.

    &lt;VulnDiscussion&gt;With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection...
    Rule Medium Severity
  • SRG-APP-000266

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

    &lt;VulnDiscussion&gt;Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromis...
    Rule Medium Severity
  • SRG-APP-000267

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.

    &lt;VulnDiscussion&gt;If the DBMS provides too much information in error logs and administrative messages to the screen, this could lead to comprom...
    Rule Medium Severity
  • The DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

    &lt;VulnDiscussion&gt;This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that ...
    Rule Medium Severity
  • SRG-APP-000296

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user.

    &lt;VulnDiscussion&gt;If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred...
    Rule Medium Severity
  • SRG-APP-000311

    <GroupDescription></GroupDescription>
    Group
  • The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.

    &lt;VulnDiscussion&gt;Without the association of security labels to information, there is no basis for the DBMS to make security-related access-con...
    Rule Medium Severity
  • SRG-APP-000313

    <GroupDescription></GroupDescription>
    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