UCF STIG Viewer Logo

Database Security Requirements Guide


Overview

Date Finding Count (126)
2017-06-23 CAT I (High): 0 CAT II (Med): 126 CAT III (Low): 0
STIG Description
The Database Security Requirements Guide (SRG) is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the NIST 800-53 and related documents. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.stig_spt@mail.mil.

Available Profiles



Findings (MAC III - Administrative Classified)

Finding ID Severity Title
V-32514 Medium The DBMS must separate user functionality (including user interface services) from database management functionality.
V-58111 Medium The DBMS must generate audit records showing starting and ending time for user access to the database(s).
V-58059 Medium The DBMS must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts.
V-58113 Medium The DBMS must generate audit records when concurrent logons/connections by the same user from different workstations occur.
V-58115 Medium The DBMS must generate audit records for all privileged activities or other system-level access.
V-58117 Medium The DBMS must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.
V-58119 Medium The DBMS must be able to generate audit records when successful accesses to objects occur.
V-58051 Medium The DBMS must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS.
V-58053 Medium The DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.
V-58055 Medium The 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-58057 Medium The DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.
V-58085 Medium The DBMS must generate audit records when unsuccessful attempts to access security objects occur.
V-58183 Medium When invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives.
V-58181 Medium 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.
V-58065 Medium The DBMS must generate time stamps, for audit records and application data, with a minimum granularity of one second.
V-58067 Medium The 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.
V-58061 Medium The 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.
V-58063 Medium The DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).
V-58069 Medium The DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.
V-58109 Medium The DBMS must generate audit records when unsuccessful logons or connection attempts occur.
V-32469 Medium If passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.
V-32468 Medium If passwords are used for authentication, the DBMS must store only hashed, salted representations of passwords.
V-58105 Medium The DBMS must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.
V-58103 Medium The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.
V-58101 Medium The DBMS must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.
V-58107 Medium The DBMS must generate audit records when successful logons or connections occur.
V-32399 Medium The DBMS must protect its audit features from unauthorized removal.
V-32375 Medium The DBMS must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.
V-32374 Medium The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.
V-58071 Medium The DBMS must generate audit records when privileges/permissions are added.
V-32371 Medium The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.
V-32370 Medium The DBMS must produce audit records containing sufficient information to establish where the events occurred.
V-32373 Medium The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.
V-58075 Medium The DBMS must generate audit records when privileges/permissions are modified.
V-58079 Medium The DBMS must generate audit records when privileges/permissions are deleted.
V-32203 Medium The DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
V-58179 Medium The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.
V-32394 Medium The audit information produced by the DBMS must be protected from unauthorized modification.
V-32478 Medium The DBMS must map the PKI-authenticated identity to an associated user account.
V-32479 Medium The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.
V-32476 Medium The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.
V-32393 Medium The audit information produced by the DBMS must be protected from unauthorized read access.
V-58171 Medium The DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.
V-32475 Medium The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.
V-58177 Medium Security-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).
V-58175 Medium When updates are applied to the DBMS software, any software components that have been replaced or made unnecessary must be removed.
V-61407 Medium If DBMS authentication, using passwords, is employed, the DBMS must enforce the DoD standards for password complexity and lifetime.
V-32481 Medium The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).
V-32480 Medium The DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.
V-32571 Medium The DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.
V-32362 Medium The DBMS must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.
V-32363 Medium The DBMS must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
V-32366 Medium The DBMS must provide the capability for authorized users to capture, record, and log all content related to a user session.
V-32364 Medium The DBMS must be able to generate audit records when privileges/permissions are retrieved.
V-32365 Medium The DBMS must initiate session auditing upon startup.
V-58087 Medium The DBMS must generate audit records when security objects are modified.
V-32368 Medium The DBMS must produce audit records containing sufficient information to establish what type of events occurred.
V-32369 Medium The DBMS must produce audit records containing time stamps to establish when the events occurred.
V-58083 Medium The DBMS must be able to generate audit records when security objects are accessed.
V-58081 Medium The DBMS must generate audit records when unsuccessful attempts to delete privileges/permissions occur.
V-58169 Medium The 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-58161 Medium The DBMS must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes.
V-58163 Medium The 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.
V-58165 Medium The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.
V-58167 Medium The 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-32192 Medium The 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-58089 Medium The DBMS must generate audit records when unsuccessful attempts to modify security objects occur.
V-58019 Medium The DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.
V-58155 Medium The DBMS must maintain the confidentiality and integrity of information during reception.
V-58157 Medium The DBMS must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.
V-58151 Medium Access to database files must be limited to relevant processes and to authorized, administrative users.
V-58099 Medium The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are modified.
V-58153 Medium The DBMS must maintain the confidentiality and integrity of information during preparation for transmission.
V-32398 Medium The DBMS must protect its audit configuration from unauthorized modification.
V-32397 Medium The DBMS must protect its audit features from unauthorized access.
V-58095 Medium The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.
V-32395 Medium The audit information produced by the DBMS must be protected from unauthorized deletion.
V-58097 Medium The DBMS must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.
V-58159 Medium The DBMS must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.
V-58091 Medium The DBMS must generate audit records when security objects are deleted.
V-32391 Medium The DBMS must use system clocks to generate time stamps for use in audit records and application data.
V-58093 Medium The DBMS must generate audit records when unsuccessful attempts to delete security objects occur.
V-32555 Medium The DBMS must check the validity of all data inputs except those specifically identified by the organization.
V-32412 Medium Database 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-32413 Medium Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.
V-32414 Medium The DBMS software installation account must be restricted to authorized users.
V-32415 Medium The DBMS must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS.
V-32529 Medium 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.
V-32347 Medium The DBMS must protect against a user falsely repudiating having performed organization-defined actions.
V-32424 Medium Unused database components, DBMS software, and database objects must be removed.
V-32427 Medium Access to external executables must be disabled or restricted.
V-32426 Medium Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.
V-58147 Medium The DBMS must require users to re-authenticate when organization-defined circumstances or situations require re-authentication.
V-32423 Medium Default demonstration and sample databases, database objects, and applications must be removed.
V-58149 Medium The DBMS must prevent unauthorized and unintended information transfer via shared system resources.
V-32428 Medium 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.
V-32383 Medium The 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.
V-58021 Medium Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.
V-58023 Medium The DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
V-58025 Medium The DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.
V-58073 Medium The DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur.
V-32547 Medium Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.
V-58077 Medium The DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.
V-32523 Medium The DBMS must invalidate session identifiers upon user logout or other session termination.
V-58137 Medium The DBMS must prohibit the use of cached authenticators after an organization-defined time period.
V-58135 Medium The DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.
V-58133 Medium The 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-58131 Medium The 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-58039 Medium The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process.
V-58037 Medium The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.
V-58035 Medium The DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user.
V-32536 Medium The DBMS must isolate security functions from non-security functions.
V-32534 Medium The DBMS must protect the confidentiality and integrity of all information at rest.
V-58121 Medium The DBMS must generate audit records when unsuccessful accesses to objects occur.
V-32157 Medium The DBMS must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.
V-32528 Medium The DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
V-58125 Medium The DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).
V-58049 Medium The DBMS must utilize centralized management of the content captured in audit records generated by all components of the DBMS.
V-58127 Medium The DBMS must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).
V-32442 Medium The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).
V-58123 Medium The DBMS must generate audit records for all direct access to the database(s).
V-58041 Medium The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in transmission.
V-32570 Medium 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.
V-58129 Medium 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.
V-32526 Medium The DBMS must recognize only system-generated session identifiers.
V-58173 Medium The DBMS must maintain a separate execution domain for each executing process.