| Checked | Name | Title |
|---|
| ☐ | SV-213900r508025_rule | SQL Server databases must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. |
| ☐ | SV-213901r508025_rule | SQL Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-213902r508025_rule | SQL Server must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the database. |
| ☐ | SV-213903r508025_rule | SQL Server must protect against a user falsely repudiating by use of system-versioned tables (Temporal Tables). |
| ☐ | SV-213904r508025_rule | SQL Server must protect against a user falsely repudiating by ensuring databases are not in a trust relationship. |
| ☐ | SV-213905r508025_rule | SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-213906r508025_rule | SQL Server must limit privileges to change software modules, to include stored procedures, functions, and triggers. |
| ☐ | SV-213907r508025_rule | SQL Server must limit privileges to change software modules, to include stored procedures, functions, and triggers, and links to software external to SQL Server. |
| ☐ | SV-213908r508025_rule | Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to SQL Server, etc.) must be owned by database/DBMS principals authorized for ownership. |
| ☐ | SV-213909r508025_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 SQL Server, etc.) must be restricted to authorized users. |
| ☐ | SV-213910r508025_rule | In the event of a system failure, hardware loss or disk failure, SQL Server must be able to restore necessary databases with least disruption to mission processes. |
| ☐ | SV-213911r508025_rule | The Database Master Key encryption password must meet DOD password complexity requirements. |
| ☐ | SV-213912r508025_rule | The Database Master Key must be encrypted by the Service Master Key, where a Database Master Key is required and another encryption method has not been specified. |
| ☐ | SV-213913r508025_rule | The Certificate used for encryption must be backed up, stored offline and off-site. |
| ☐ | SV-213914r508025_rule | SQL Server must isolate security functions from non-security functions. |
| ☐ | SV-213915r508025_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-213916r508025_rule | SQL Server must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-213917r508025_rule | SQL Server 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-213918r508025_rule | SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-213919r508025_rule | SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-213920r508025_rule | SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-213921r508025_rule | SQL Server must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-213922r508025_rule | Execution of stored procedures and functions that utilize execute as must be restricted to necessary cases only. |
| ☐ | SV-213923r508025_rule | SQL Server must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-213924r508025_rule | SQL Server must enforce access restrictions associated with changes to the configuration of the database(s). |
| ☐ | SV-213926r508025_rule | SQL Server 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-213927r508025_rule | SQL Server must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components. |
| ☐ | SV-220329r508025_rule | SQL Server must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements. |
STIGQter: STIG Summary: