STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Database Security Requirements Guide

Version

V4R5

Benchmark ID

Database_Generic

Total Checks

142

Tags

database
CAT I: 14CAT II: 128CAT III: 0

This Security Requirements Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSON

Checks (142)

V-206519MEDIUMThe DBMS must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.V-206520HIGHThe DBMS must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-206521HIGHThe DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-206522MEDIUMThe DBMS must protect against a user falsely repudiating having performed organization-defined actions.V-206523MEDIUMThe DBMS must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.V-206524MEDIUMThe DBMS must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.V-206525MEDIUMThe DBMS must be able to generate audit records when privileges/permissions are retrieved.V-206526MEDIUMThe DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.V-206527MEDIUMThe DBMS must initiate session auditing upon startup.V-206528MEDIUMThe DBMS must produce audit records containing sufficient information to establish what type of events occurred.V-206529MEDIUMThe DBMS must produce audit records containing time stamps to establish when the events occurred.V-206530MEDIUMThe DBMS must produce audit records containing sufficient information to establish where the events occurred.V-206531MEDIUMThe DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.V-206532MEDIUMThe DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.V-206533MEDIUMThe DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.V-206534MEDIUMThe DBMS must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.V-206537MEDIUMThe DBMS must use system clocks to generate time stamps for use in audit records and application data.V-206538MEDIUMThe audit information produced by the DBMS must be protected from unauthorized read access.V-206539MEDIUMThe audit information produced by the DBMS must be protected from unauthorized modification.V-206540MEDIUMThe audit information produced by the DBMS must be protected from unauthorized deletion.V-206541MEDIUMThe DBMS must protect its audit features from unauthorized access.V-206542MEDIUMThe DBMS must protect its audit configuration from unauthorized modification.V-206543MEDIUMThe DBMS must protect its audit features from unauthorized removal.V-206544MEDIUMThe DBMS must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS.V-206545HIGHThe DBMS software installation account must be restricted to authorized users.V-206546MEDIUMDatabase software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.V-206547MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/DBMS principals authorized for ownership.V-206548MEDIUMThe 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.V-206549MEDIUMDefault demonstration and sample databases, database objects, and applications must be removed.V-206550MEDIUMUnused database components, DBMS software, and database objects must be removed.V-206551MEDIUMUnused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.V-206552MEDIUMAccess to external executables must be disabled or restricted.V-206553MEDIUMThe 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.V-206554MEDIUMThe DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-206555HIGHIf DBMS authentication, using passwords, is employed, the DBMS must enforce the DOD standards for password complexity and lifetime.V-206556HIGHThe DBMS must for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash.V-206557HIGHIf passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.V-206558MEDIUMThe DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.V-206559HIGHThe DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.V-206560MEDIUMThe DBMS must map the PKI-authenticated identity to an associated user account.V-206561HIGHThe DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.V-206562HIGHThe DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.V-206563MEDIUMThe DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).V-206564MEDIUMThe DBMS must separate user functionality (including user interface services) from database management functionality.V-206565MEDIUMThe DBMS must invalidate session identifiers upon user logout or other session termination.V-206566MEDIUMThe DBMS must recognize only system-generated session identifiers.V-206567MEDIUMThe DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-206568MEDIUMThe DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.V-206569MEDIUMIn 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.V-206570HIGHThe DBMS must protect the confidentiality and integrity of all information at rest.V-206571MEDIUMThe DBMS must isolate security functions from non-security functions.V-206572MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-206573MEDIUMThe DBMS must prevent unauthorized and unintended information transfer via shared system resources.V-206574MEDIUMAccess to database files must be limited to relevant processes and to authorized, administrative users.V-206575MEDIUMThe DBMS must check the validity of all data inputs except those specifically identified by the organization.V-206576MEDIUMThe DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.V-206577MEDIUMThe 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.V-206578MEDIUMThe 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.V-206579MEDIUMThe DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.V-206580MEDIUMThe DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.V-206581MEDIUMThe DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user.V-206582MEDIUMThe DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-206583MEDIUMThe DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process.V-206584MEDIUMThe DBMS must associate organization-defined types of security labels having organization-defined security label values with information in transmission.V-206585MEDIUMThe DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.V-206586MEDIUMThe DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-206587MEDIUMExecution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.V-206591MEDIUMThe DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.V-206592MEDIUMThe DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.V-206593MEDIUMThe DBMS must provide an immediate real-time alert to appropriate support staff of all audit log failures.V-206594MEDIUMThe DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).V-206595MEDIUMThe DBMS must generate time stamps, for audit records and application data, with a minimum granularity of one second.V-206596MEDIUMThe DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-206597MEDIUMThe DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).V-206598MEDIUMThe DBMS must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).V-206599MEDIUMThe DBMS must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.V-206600MEDIUMThe DBMS must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.V-206601MEDIUMThe DBMS must prohibit the use of cached authenticators after an organization-defined time period.V-206603MEDIUMThe DBMS must only accept end entity certificates issued by DOD PKI or DOD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.V-206604HIGHThe DBMS must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.V-206605HIGHThe DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.V-206606MEDIUMThe DBMS must maintain a separate execution domain for each executing process.V-206607MEDIUMThe DBMS must maintain the confidentiality and integrity of information during preparation for transmission.V-206608MEDIUMThe DBMS must maintain the confidentiality and integrity of information during reception.V-206609MEDIUMWhen invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives.V-206610MEDIUMWhen updates are applied to the DBMS software, any software components that have been replaced or made unnecessary must be removed.V-206611MEDIUMSecurity-relevant software updates to the DBMS must be installed within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).V-206612MEDIUMThe DBMS must be able to generate audit records when security objects are accessed.V-206613MEDIUMThe DBMS must generate audit records when unsuccessful attempts to access security objects occur.V-206614MEDIUMThe DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.V-206615MEDIUMThe DBMS must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.V-206616MEDIUMThe DBMS must generate audit records when privileges/permissions are added.V-206617MEDIUMThe DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur.V-206618MEDIUMThe DBMS must generate audit records when privileges/permissions are modified.V-206619MEDIUMThe DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.V-206620MEDIUMThe DBMS must generate audit records when security objects are modified.V-206621MEDIUMThe DBMS must generate audit records when unsuccessful attempts to modify security objects occur.V-206622MEDIUMThe DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are modified.V-206623MEDIUMThe DBMS must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.V-206624MEDIUMThe DBMS must generate audit records when privileges/permissions are deleted.V-206625MEDIUMThe DBMS must generate audit records when unsuccessful attempts to delete privileges/permissions occur.V-206626MEDIUMThe DBMS must generate audit records when security objects are deleted.V-206627MEDIUMThe DBMS must generate audit records when unsuccessful attempts to delete security objects occur.V-206628MEDIUMThe DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.V-206629MEDIUMThe DBMS must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.V-206630MEDIUMThe DBMS must generate audit records when successful logons or connections occur.V-206631MEDIUMThe DBMS must generate audit records when unsuccessful logons or connection attempts occur.V-206632MEDIUMThe DBMS must generate audit records for all privileged activities or other system-level access.V-206633MEDIUMThe DBMS must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.V-206634MEDIUMThe DBMS must generate audit records showing starting and ending time for user access to the database(s).V-206635MEDIUMThe DBMS must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-206636MEDIUMThe DBMS must be able to generate audit records when successful accesses to objects occur.V-206637MEDIUMThe DBMS must generate audit records when unsuccessful accesses to objects occur.V-206638MEDIUMThe DBMS must generate audit records for all direct access to the database(s).V-206639MEDIUMThe DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.V-206640MEDIUMThe DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.V-206641MEDIUMThe DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.V-206642MEDIUMThe DBMS must off-load audit data to a separate log management facility; this shall be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.V-206643MEDIUMThe DBMS must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.V-233495HIGHThe DBMS must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements.V-263602MEDIUMThe DBMS must disable accounts when the accounts have expired.V-263603MEDIUMThe DBMS must disable accounts when the accounts are no longer associated to a user.V-263604MEDIUMThe DBMS must implement the capability to centrally review and analyze audit records from multiple components within the system.V-263605MEDIUMThe DBMS must alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.V-263606MEDIUMThe DBMS must prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate recognized and approved by the organization.V-263607MEDIUMThe DBMS must require users to be individually authenticated before granting access to the shared accounts or resources.V-263608MEDIUMThe DBMS must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access.V-263609MEDIUMThe DBMS must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements.V-263610MEDIUMThe DBMS must, for password-based authentication, maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency.V-263611MEDIUMThe DBMS must, for password-based authentication, update the list of passwords on an organization-defined frequency.V-263612MEDIUMThe DBMS must, for password-based authentication, update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly.V-263613MEDIUMThe DBMS must, for password-based authentication, verify that when users create or update passwords, the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a).V-263614MEDIUMThe DBMS must, for password-based authentication, require immediate selection of a new password upon account recovery.V-263615MEDIUMThe DBMS must, for password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters.V-263616MEDIUMThe DBMS must, for password-based authentication, employ automated tools to assist the user in selecting strong password authenticators.V-263617MEDIUMThe DBMS must, for public key-based authentication, implement a local cache of revocation data to support path discovery and validation.V-263618MEDIUMThe DBMS must protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths.V-263619MEDIUMThe DBMS must include only approved trust anchors in trust stores or certificate stores managed by the organization.V-263620MEDIUMThe DBMS must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store.V-263621MEDIUMThe DBMS must synchronize system clocks within and between systems or system components.V-263622MEDIUMThe DBMS must compare the internal system clocks on an organization-defined frequency with organization-defined authoritative time source.V-278969HIGHThe DBMS must be a version supported by the vendor.