Skip to content

Database Security Requirements Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-APP-000880

    Group
  • SRG-APP-000910

    Group
  • The DBMS must include only approved trust anchors in trust stores or certificate stores managed by the organization.

    Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the internal operations of systems, such as application-...
    Rule Medium Severity
  • SRG-APP-000915

    Group
  • SRG-APP-000920

    Group
  • SRG-APP-000925

    Group
  • SRG-APP-000456

    Group
  • DBMS products must be a version supported by the vendor.

    Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilit...
    Rule High Severity
  • The DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

    Authentication with a DoD-approved PKI certificate does not necessarily imply authorization to access the DBMS. To mitigate the risk of unauthorized access to sensitive information by entities tha...
    Rule High Severity
  • The DBMS must protect against a user falsely repudiating having performed organization-defined actions.

    Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving info...
    Rule Medium Severity
  • The DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

    Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically mak...
    Rule Medium Severity
  • The DBMS must produce audit records containing sufficient information to establish what type of events occurred.

    Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate t...
    Rule Medium Severity
  • The DBMS must produce audit records containing sufficient information to establish where the events occurred.

    Information system auditing capability is critical for accurate forensic analysis. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events r...
    Rule Medium Severity
  • The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.

    Information system auditing capability is critical for accurate forensic analysis. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events...
    Rule Medium Severity
  • The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.

    Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of events, security personnel cannot make an accurate assessment as to wheth...
    Rule Medium Severity
  • The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.

    Information system auditing capability is critical for accurate forensic analysis. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of us...
    Rule Medium Severity
  • The DBMS must use system clocks to generate time stamps for use in audit records and application data.

    Internal system clocks are typically a feature of server hardware and are maintained and used by the operating system. They are typically synchronized with an authoritative time server at regular i...
    Rule Medium Severity
  • The audit information produced by the DBMS must be protected from unauthorized modification.

    If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veraci...
    Rule Medium Severity
  • The audit information produced by the DBMS must be protected from unauthorized deletion.

    If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. To ensure the veracit...
    Rule Medium Severity
  • The DBMS must protect its audit features from unauthorized removal.

    Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on au...
    Rule Medium Severity
  • The DBMS software installation account must be restricted to authorized users.

    When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effec...
    Rule High Severity
  • Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.

    When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have signi...
    Rule Medium Severity
  • The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be restricted to authorized users.

    If the DBMS were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of ...
    Rule Medium Severity
  • Default demonstration and sample databases, database objects, and applications must be removed.

    Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizatio...
    Rule Medium Severity
  • Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.

    Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizatio...
    Rule Medium Severity
  • Access to external executables must be disabled or restricted.

    Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizatio...
    Rule Medium Severity
  • The DBMS must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

    In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable...
    Rule Medium Severity
  • The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

    To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational use...
    Rule Medium Severity
  • If DBMS authentication, using passwords, is employed, the DBMS must enforce the DOD standards for password complexity and lifetime.

    OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable; and must be documented a...
    Rule High Severity
  • The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

    The DoD standard for authentication is DoD-approved PKI certificates. A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA)....
    Rule Medium Severity
  • The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.

    The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of ...
    Rule High Severity
  • The DBMS must map the PKI-authenticated identity to an associated user account.

    The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to a DBMS user account for the authenticated identity to be meanin...
    Rule Medium Severity
  • The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

    The DoD standard for authentication is DoD-approved PKI certificates. Normally, with PKI authentication, the interaction with the user for authentication will be handled by a software component se...
    Rule High Severity
  • The DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.

    Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated ...
    Rule High Severity
  • The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

    Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status...
    Rule Medium Severity
  • The DBMS must separate user functionality (including user interface services) from database management functionality.

    Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The s...
    Rule Medium Severity
  • The DBMS must invalidate session identifiers upon user logout or other session termination.

    Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and continue to employ previously valid session IDs. This requirement focuses on ...
    Rule Medium Severity
  • The DBMS must recognize only system-generated session identifiers.

    DBMSs utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier or can inject or manually insert session information,...
    Rule Medium Severity
  • The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

    One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique fo...
    Rule Medium Severity
  • 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.

    Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, ...
    Rule Medium Severity
  • The DBMS must isolate security functions from non-security functions.

    An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. Security functions are the hardware, software, an...
    Rule Medium Severity
  • Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.

    Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Data used for the development and testing of applications often involves ...
    Rule Medium Severity
  • The DBMS must check the validity of all data inputs except those specifically identified by the organization.

    Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated applic...
    Rule Medium Severity
  • The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.

    With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various pr...
    Rule Medium Severity
  • 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.

    Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of er...
    Rule Medium Severity
  • The DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.

    If the DBMS provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully co...
    Rule Medium Severity
  • The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.

    Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic...
    Rule Medium Severity
  • The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process.

    Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions. Security labels are abstractions representing the basic...
    Rule Medium Severity
  • The DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.

    Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which...
    Rule Medium Severity
  • The DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.

    Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to the DBMS on its own server will not be an issue. However, space will sti...
    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