| Checked | Name | Title |
|---|
| ☐ | SV-206519r617447_rule | The DBMS must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types. |
| ☐ | SV-206520r617447_rule | 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. |
| ☐ | SV-206521r617447_rule | The DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-206522r617447_rule | The DBMS must protect against a user falsely repudiating having performed organization-defined actions. |
| ☐ | SV-206523r617447_rule | The DBMS must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-206524r617447_rule | The DBMS must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-206525r617447_rule | The DBMS must be able to generate audit records when privileges/permissions are retrieved. |
| ☐ | SV-206526r617447_rule | The DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur. |
| ☐ | SV-206527r617447_rule | The DBMS must initiate session auditing upon startup. |
| ☐ | SV-206528r617447_rule | The DBMS must produce audit records containing sufficient information to establish what type of events occurred. |
| ☐ | SV-206529r617447_rule | The DBMS must produce audit records containing time stamps to establish when the events occurred. |
| ☐ | SV-206530r617447_rule | The DBMS must produce audit records containing sufficient information to establish where the events occurred. |
| ☐ | SV-206531r617447_rule | The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events. |
| ☐ | SV-206532r617447_rule | The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. |
| ☐ | SV-206533r617447_rule | The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. |
| ☐ | SV-206534r617447_rule | The DBMS must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject. |
| ☐ | SV-206535r617447_rule | 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. |
| ☐ | SV-206536r617447_rule | 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. |
| ☐ | SV-206537r617447_rule | The DBMS must use system clocks to generate time stamps for use in audit records and application data. |
| ☐ | SV-206538r617447_rule | The audit information produced by the DBMS must be protected from unauthorized read access. |
| ☐ | SV-206539r617447_rule | The audit information produced by the DBMS must be protected from unauthorized modification. |
| ☐ | SV-206540r617447_rule | The audit information produced by the DBMS must be protected from unauthorized deletion. |
| ☐ | SV-206541r617447_rule | The DBMS must protect its audit features from unauthorized access. |
| ☐ | SV-206542r617447_rule | The DBMS must protect its audit configuration from unauthorized modification. |
| ☐ | SV-206543r617447_rule | The DBMS must protect its audit features from unauthorized removal. |
| ☐ | SV-206544r617447_rule | The DBMS must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS. |
| ☐ | SV-206545r617447_rule | The DBMS software installation account must be restricted to authorized users. |
| ☐ | SV-206546r617447_rule | Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. |
| ☐ | SV-206547r617447_rule | 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. |
| ☐ | SV-206548r617447_rule | 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. |
| ☐ | SV-206549r617447_rule | Default demonstration and sample databases, database objects, and applications must be removed. |
| ☐ | SV-206550r617447_rule | Unused database components, DBMS software, and database objects must be removed. |
| ☐ | SV-206551r617447_rule | Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled. |
| ☐ | SV-206552r617447_rule | Access to external executables must be disabled or restricted. |
| ☐ | SV-206553r617447_rule | 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. |
| ☐ | SV-206554r617447_rule | The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-206555r617447_rule | If DBMS authentication, using passwords, is employed, the DBMS must enforce the DoD standards for password complexity and lifetime. |
| ☐ | SV-206556r617447_rule | If passwords are used for authentication, the DBMS must store only hashed, salted representations of passwords. |
| ☐ | SV-206557r617447_rule | If passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords. |
| ☐ | SV-206558r617447_rule | The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation. |
| ☐ | SV-206559r617447_rule | The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS. |
| ☐ | SV-206560r617447_rule | The DBMS must map the PKI-authenticated identity to an associated user account. |
| ☐ | SV-206561r617447_rule | The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-206562r617447_rule | The DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-206563r617447_rule | The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-206564r617447_rule | The DBMS must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-206565r617447_rule | The DBMS must invalidate session identifiers upon user logout or other session termination. |
| ☐ | SV-206566r617447_rule | The DBMS must recognize only system-generated session identifiers. |
| ☐ | SV-206567r617447_rule | The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-206568r617447_rule | The DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-206569r617447_rule | 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. |
| ☐ | SV-206570r617447_rule | The DBMS must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-206571r617447_rule | The DBMS must isolate security functions from non-security functions. |
| ☐ | SV-206572r617447_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-206573r617447_rule | The DBMS must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-206574r617447_rule | Access to database files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-206575r617447_rule | The DBMS must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-206576r617447_rule | The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-206577r617447_rule | 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. |
| ☐ | SV-206578r617447_rule | 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. |
| ☐ | SV-206579r617447_rule | The DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA. |
| ☐ | SV-206580r617447_rule | The DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect. |
| ☐ | SV-206581r617447_rule | The DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user. |
| ☐ | SV-206582r617447_rule | The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-206583r617447_rule | The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-206584r617447_rule | The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-206585r617447_rule | The DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-206586r617447_rule | The DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-206587r617447_rule | Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only. |
| ☐ | SV-206589r617447_rule | The DBMS must utilize centralized management of the content captured in audit records generated by all components of the DBMS. |
| ☐ | SV-206590r617447_rule | The DBMS must provide centralized configuration of the content to be captured in audit records generated by all components of the DBMS. |
| ☐ | SV-206591r617447_rule | The DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-206592r617447_rule | The DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity. |
| ☐ | SV-206593r617447_rule | The DBMS must provide an immediate real-time alert to appropriate support staff of all audit log failures. |
| ☐ | SV-206594r617447_rule | The DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT). |
| ☐ | SV-206595r617447_rule | The DBMS must generate time stamps, for audit records and application data, with a minimum granularity of one second. |
| ☐ | SV-206596r617447_rule | The DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-206597r617447_rule | The DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s). |
| ☐ | SV-206598r617447_rule | The DBMS must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s). |
| ☐ | SV-206599r617447_rule | 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. |
| ☐ | SV-206600r617447_rule | The DBMS must require users to re-authenticate when organization-defined circumstances or situations require re-authentication. |
| ☐ | SV-206601r617447_rule | The DBMS must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-206603r617447_rule | 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. |
| ☐ | SV-206604r617447_rule | 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. |
| ☐ | SV-206605r617447_rule | The DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-206606r617447_rule | The DBMS must maintain a separate execution domain for each executing process. |
| ☐ | SV-206607r617447_rule | The DBMS must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-206608r617447_rule | The DBMS must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-206609r617447_rule | When invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-206610r617447_rule | When updates are applied to the DBMS software, any software components that have been replaced or made unnecessary must be removed. |
| ☐ | SV-206611r617447_rule | 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). |
| ☐ | SV-206612r617447_rule | The DBMS must be able to generate audit records when security objects are accessed. |
| ☐ | SV-206613r617447_rule | The DBMS must generate audit records when unsuccessful attempts to access security objects occur. |
| ☐ | SV-206614r617447_rule | The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed. |
| ☐ | SV-206615r617447_rule | The DBMS must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-206616r617447_rule | The DBMS must generate audit records when privileges/permissions are added. |
| ☐ | SV-206617r617447_rule | The DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur. |
| ☐ | SV-206618r617447_rule | The DBMS must generate audit records when privileges/permissions are modified. |
| ☐ | SV-206619r617447_rule | The DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur. |
| ☐ | SV-206620r617447_rule | The DBMS must generate audit records when security objects are modified. |
| ☐ | SV-206621r617447_rule | The DBMS must generate audit records when unsuccessful attempts to modify security objects occur. |
| ☐ | SV-206622r617447_rule | The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are modified. |
| ☐ | SV-206623r617447_rule | The DBMS must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-206624r617447_rule | The DBMS must generate audit records when privileges/permissions are deleted. |
| ☐ | SV-206625r617447_rule | The DBMS must generate audit records when unsuccessful attempts to delete privileges/permissions occur. |
| ☐ | SV-206626r617447_rule | The DBMS must generate audit records when security objects are deleted. |
| ☐ | SV-206627r617447_rule | The DBMS must generate audit records when unsuccessful attempts to delete security objects occur. |
| ☐ | SV-206628r617447_rule | The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are deleted. |
| ☐ | SV-206629r617447_rule | The DBMS must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur. |
| ☐ | SV-206630r617447_rule | The DBMS must generate audit records when successful logons or connections occur. |
| ☐ | SV-206631r617447_rule | The DBMS must generate audit records when unsuccessful logons or connection attempts occur. |
| ☐ | SV-206632r617447_rule | The DBMS must generate audit records for all privileged activities or other system-level access. |
| ☐ | SV-206633r617447_rule | The DBMS must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur. |
| ☐ | SV-206634r617447_rule | The DBMS must generate audit records showing starting and ending time for user access to the database(s). |
| ☐ | SV-206635r617447_rule | The DBMS must generate audit records when concurrent logons/connections by the same user from different workstations occur. |
| ☐ | SV-206636r617447_rule | The DBMS must be able to generate audit records when successful accesses to objects occur. |
| ☐ | SV-206637r617447_rule | The DBMS must generate audit records when unsuccessful accesses to objects occur. |
| ☐ | SV-206638r617447_rule | The DBMS must generate audit records for all direct access to the database(s). |
| ☐ | SV-206639r617447_rule | The DBMS must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures. |
| ☐ | SV-206640r617447_rule | The DBMS must implement NIST FIPS 140-2 validated cryptographic modules to generate and validate cryptographic hashes. |
| ☐ | SV-206641r617447_rule | 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. |
| ☐ | SV-206642r617447_rule | 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. |
| ☐ | SV-206643r617447_rule | 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. |
| ☐ | SV-233492r617447_rule | DBMS products must be a version supported by the vendor. |
STIGQter: STIG Summary: