| Checked | Name | Title |
|---|
| ☐ | SV-81847r1_rule | SQL Server must enforce approved authorizations for logical access to information and database-level system resources in accordance with applicable access control policies. |
| ☐ | SV-81849r2_rule | SQL Server must generate Trace or Audit records for organization-defined auditable events. |
| ☐ | SV-81851r2_rule | Where SQL Server Audit is in use at the database level, SQL Server must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited at the database level. |
| ☐ | SV-81855r2_rule | SQL Server must be monitored to discover unauthorized changes to functions. |
| ☐ | SV-81857r2_rule | SQL Server must be monitored to discover unauthorized changes to triggers. |
| ☐ | SV-81859r2_rule | SQL Server must be monitored to discover unauthorized changes to stored procedures. |
| ☐ | SV-81861r1_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-81863r1_rule | In a database owned by a login not having administrative privileges at the instance level, the database property TRUSTWORTHY must be OFF unless required and authorized. |
| ☐ | SV-81865r1_rule | In a database owned by [sa], or by any other login having administrative privileges at the instance level, the database property TRUSTWORTHY must be OFF. |
| ☐ | SV-81867r2_rule | In the event of a system failure, SQL Server must preserve any information necessary to return to operations with least disruption to mission processes. |
| ☐ | SV-81871r1_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-81873r1_rule | Database Master Key passwords must not be stored in credentials within the database. |
| ☐ | SV-81875r2_rule | Symmetric keys (other than the database master key) must use a DoD certificate to encrypt the key. |
| ☐ | SV-81879r1_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-81881r2_rule | SQL Server must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-81883r2_rule | The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-81885r2_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-81887r2_rule | The DBMS and associated applications 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-81889r2_rule | SQL Server must reveal detailed error messages only to the ISSO, ISSM (or their designees), SA and DBA. |
| ☐ | SV-81891r2_rule | When supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-81893r2_rule | When supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in process. |
| ☐ | SV-81895r2_rule | When supporting applications that require security labeling of data, SQL Server must associate organization-defined types of security labels having organization-defined security label values with information in transmission. |
| ☐ | SV-81897r1_rule | Time stamps in database tables, intended for auditing or activity-tracking purposes, must include both date and time of day, with a minimum granularity of one second. |
| ☐ | SV-81899r1_rule | SQL Server must implement and/or support 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-81901r2_rule | When invalid inputs are received, SQL Server must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-81903r2_rule | Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is accessed. |
| ☐ | SV-81905r2_rule | Trace or Audit records must be generated when unsuccessful attempts to access categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-81907r2_rule | SQL Server must generate Trace or Audit records when privileges/permissions are modified via locally-defined security objects. |
| ☐ | SV-81909r2_rule | SQL Server must generate Trace or Audit records when unsuccessful attempts to modify privileges/permissions via locally-defined security objects occur. |
| ☐ | SV-81911r2_rule | SQL Server must generate Trace or Audit records when locally-defined security objects are modified. |
| ☐ | SV-81913r3_rule | SQL Server must generate Trace or Audit records when unsuccessful accesses to designated objects occur. |
| ☐ | SV-81915r3_rule | SQL Server must generate Trace or Audit records when successful accesses to designated objects occur. |
| ☐ | SV-81917r2_rule | Trace or Audit records must be generated when unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-81919r2_rule | Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is deleted. |
| ☐ | SV-81921r3_rule | SQL Server must generate Trace or Audit records when unsuccessful attempts to drop locally-defined security objects occur. |
| ☐ | SV-81923r3_rule | SQL Server must generate Trace or Audit records when locally-defined security objects are dropped. |
| ☐ | SV-81925r2_rule | SQL Server must generate Trace or Audit records when unsuccessful attempts to modify locally-defined security objects occur. |
| ☐ | SV-81927r2_rule | Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is created. |
| ☐ | SV-81929r2_rule | Trace or Audit records must be generated when unsuccessful attempts to create categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-81931r2_rule | Trace or Audit records must be generated when categorized information (e.g., classification levels/security levels) is modified. |
| ☐ | SV-81933r2_rule | Trace or Audit records must be generated when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur. |
| ☐ | SV-82367r3_rule | SQL Server must protect data at rest and ensure confidentiality and integrity of data. |
STIGQter: STIG Summary: