STIGQter STIGQter: STIG Summary: Database Security Requirements Guide

Version: 2

Release: 9 Benchmark Date: 25 Oct 2019

CheckedNameTitle
SV-42474r3_ruleThe DBMS must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
SV-42509r3_ruleThe DBMS must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.
SV-42520r3_ruleThe DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
SV-42684r4_ruleThe DBMS must protect against a user falsely repudiating having performed organization-defined actions.
SV-42699r3_ruleThe DBMS must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.
SV-42700r3_ruleThe DBMS must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
SV-42701r3_ruleThe DBMS must be able to generate audit records when privileges/permissions are retrieved.
SV-42702r2_ruleThe DBMS must initiate session auditing upon startup.
SV-42705r3_ruleThe DBMS must produce audit records containing sufficient information to establish what type of events occurred.
SV-42706r3_ruleThe DBMS must produce audit records containing time stamps to establish when the events occurred.
SV-42707r3_ruleThe DBMS must produce audit records containing sufficient information to establish where the events occurred.
SV-42708r3_ruleThe DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.
SV-42710r3_ruleThe DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
SV-42711r3_ruleThe DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
SV-42712r4_ruleThe DBMS must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
SV-42720r3_ruleThe DBMS must by default shut down upon audit failure, to include the unavailability of space for more audit log records; or must be configurable to shut down upon audit failure.
SV-42728r3_ruleThe DBMS must use system clocks to generate time stamps for use in audit records and application data.
SV-42730r3_ruleThe audit information produced by the DBMS must be protected from unauthorized read access.
SV-42731r3_ruleThe audit information produced by the DBMS must be protected from unauthorized modification.
SV-42732r3_ruleThe audit information produced by the DBMS must be protected from unauthorized deletion.
SV-42734r3_ruleThe DBMS must protect its audit features from unauthorized access.
SV-42735r3_ruleThe DBMS must protect its audit configuration from unauthorized modification.
SV-42736r3_ruleThe DBMS must protect its audit features from unauthorized removal.
SV-42749r3_ruleDatabase 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.
SV-42750r3_ruleDatabase software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.
SV-42751r3_ruleThe DBMS software installation account must be restricted to authorized users.
SV-42752r3_ruleThe DBMS must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS.
SV-42760r3_ruleDefault demonstration and sample databases, database objects, and applications must be removed.
SV-42761r3_ruleUnused database components, DBMS software, and database objects must be removed.
SV-42763r4_ruleUnused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.
SV-42764r3_ruleAccess to external executables must be disabled or restricted.
SV-42765r3_ruleThe 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.
SV-42779r4_ruleThe DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
SV-42805r3_ruleIf passwords are used for authentication, the DBMS must store only hashed, salted representations of passwords.
SV-42806r3_ruleIf passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.
SV-42812r3_ruleThe DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.
SV-42813r3_ruleThe DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.
SV-42815r3_ruleThe DBMS must map the PKI-authenticated identity to an associated user account.
SV-42816r4_ruleThe DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
SV-42817r3_ruleThe DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
SV-42818r3_ruleThe DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
SV-42851r3_ruleThe DBMS must separate user functionality (including user interface services) from database management functionality.
SV-42860r2_ruleThe DBMS must invalidate session identifiers upon user logout or other session termination.
SV-42863r2_ruleThe DBMS must recognize only system-generated session identifiers.
SV-42865r3_ruleThe DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
SV-42866r3_ruleIn 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.
SV-42871r4_ruleThe DBMS must protect the confidentiality and integrity of all information at rest.
SV-42873r3_ruleThe DBMS must isolate security functions from non-security functions.
SV-42884r3_ruleDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.
SV-42892r4_ruleThe DBMS must check the validity of all data inputs except those specifically identified by the organization.
SV-42907r4_ruleThe 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.
SV-42908r5_ruleThe DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.
SV-72449r1_ruleThe DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.
SV-72451r2_ruleExecution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.
SV-72453r1_ruleThe DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
SV-72455r1_ruleThe DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.
SV-72465r1_ruleThe DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user.
SV-72467r1_ruleThe DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.
SV-72469r1_ruleThe DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process.
SV-72471r1_ruleThe DBMS must associate organization-defined types of security labels having organization-defined security label values with information in transmission.
SV-72479r1_ruleThe DBMS must utilize centralized management of the content captured in audit records generated by all components of the DBMS.
SV-72481r1_ruleThe DBMS must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS.
SV-72483r1_ruleThe DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
SV-72485r1_ruleThe 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.
SV-72487r1_ruleThe DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.
SV-72489r1_ruleThe DBMS must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.
SV-72491r1_ruleThe DBMS must be configurable to overwrite audit log records, oldest first (First-In-First-Out - FIFO), in the event of unavailability of space for more audit log records.
SV-72493r1_ruleThe DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
SV-72495r1_ruleThe DBMS must generate time stamps, for audit records and application data, with a minimum granularity of one second.
SV-72497r1_ruleThe DBMS must provide the means for individuals in authorized roles to change the auditing to be performed on all application components, based on all selectable event criteria within organization-defined time thresholds.
SV-72499r1_ruleThe DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
SV-72501r2_ruleThe DBMS must generate audit records when privileges/permissions are added.
SV-72503r2_ruleThe DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur.
SV-72505r2_ruleThe DBMS must generate audit records when privileges/permissions are modified.
SV-72507r2_ruleThe DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
SV-72509r2_ruleThe DBMS must generate audit records when privileges/permissions are deleted.
SV-72511r2_ruleThe DBMS must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
SV-72513r1_ruleThe DBMS must be able to generate audit records when security objects are accessed.
SV-72515r1_ruleThe DBMS must generate audit records when unsuccessful attempts to access security objects occur.
SV-72517r1_ruleThe DBMS must generate audit records when security objects are modified.
SV-72519r1_ruleThe DBMS must generate audit records when unsuccessful attempts to modify security objects occur.
SV-72521r1_ruleThe DBMS must generate audit records when security objects are deleted.
SV-72523r1_ruleThe DBMS must generate audit records when unsuccessful attempts to delete security objects occur.
SV-72525r1_ruleThe DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.
SV-72527r1_ruleThe DBMS must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.
SV-72529r1_ruleThe DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are modified.
SV-72531r1_ruleThe DBMS must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.
SV-72533r1_ruleThe DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.
SV-72535r1_ruleThe DBMS must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.
SV-72537r1_ruleThe DBMS must generate audit records when successful logons or connections occur.
SV-72539r1_ruleThe DBMS must generate audit records when unsuccessful logons or connection attempts occur.
SV-72541r1_ruleThe DBMS must generate audit records showing starting and ending time for user access to the database(s).
SV-72543r1_ruleThe DBMS must generate audit records when concurrent logons/connections by the same user from different workstations occur.
SV-72545r1_ruleThe DBMS must generate audit records for all privileged activities or other system-level access.
SV-72547r1_ruleThe DBMS must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
SV-72549r1_ruleThe DBMS must be able to generate audit records when successful accesses to objects occur.
SV-72551r1_ruleThe DBMS must generate audit records when unsuccessful accesses to objects occur.
SV-72553r1_ruleThe DBMS must generate audit records for all direct access to the database(s).
SV-72555r1_ruleThe DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).
SV-72557r1_ruleThe DBMS must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).
SV-72559r1_ruleThe 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.
SV-72561r1_ruleThe 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.
SV-72563r1_ruleThe 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.
SV-72565r1_ruleThe DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.
SV-72567r1_ruleThe DBMS must prohibit the use of cached authenticators after an organization-defined time period.
SV-72577r1_ruleThe DBMS must require users to re-authenticate when organization-defined circumstances or situations require re-authentication.
SV-72579r1_ruleThe DBMS must prevent unauthorized and unintended information transfer via shared system resources.
SV-72581r1_ruleAccess to database files must be limited to relevant processes and to authorized, administrative users.
SV-72583r1_ruleThe DBMS must maintain the confidentiality and integrity of information during preparation for transmission.
SV-72585r1_ruleThe DBMS must maintain the confidentiality and integrity of information during reception.
SV-72587r1_ruleThe DBMS must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.
SV-72589r1_ruleThe DBMS must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.
SV-72591r1_ruleThe DBMS must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.
SV-72593r1_ruleThe DBMS must implement NIST FIPS 140-2 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.
SV-72595r1_ruleThe DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.
SV-72597r1_ruleThe 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.
SV-72599r1_ruleThe 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.
SV-72601r1_ruleThe DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.
SV-72603r1_ruleThe DBMS must maintain a separate execution domain for each executing process.
SV-72605r1_ruleWhen updates are applied to the DBMS software, any software components that have been replaced or made unnecessary must be removed.
SV-72607r1_ruleSecurity-relevant software updates to the DBMS must be installed within the time period directed by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
SV-72609r2_ruleThe DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.
SV-72611r2_ruleThe 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.
SV-72613r2_ruleWhen invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives.
SV-75897r3_ruleIf DBMS authentication, using passwords, is employed, the DBMS must enforce the DoD standards for password complexity and lifetime.