STIGQter STIGQter: STIG Summary:

Microsoft SQL Server 2022 Database Security Technical Implementation Guide

Version: 1

Release: 3 Benchmark Date: 01 Apr 2026

CheckedNameTitle
SV-271118r1107970_ruleSQL Server must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.
SV-271119r1137654_ruleSQL Server must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.
SV-271121r1109177_ruleSQL Server must protect against a user falsely repudiating by using system-versioned tables (Temporal Tables).
SV-271122r1109180_ruleSQL Server must protect against a user falsely repudiating by ensuring databases are not in a trust relationship.
SV-271124r1109215_ruleSQL Server must allow only the information system security manager (ISSM) (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.
SV-271143r1167490_ruleSQL Server must limit privileges to change software modules, to include stored procedures, functions, and triggers, and links to software external to SQL Server.
SV-271146r1109183_ruleDatabase 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-271147r1111078_ruleThe role(s)/group(s) used to modify database structure (including but not 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-271168r1109218_ruleIn 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-271169r1109188_ruleThe Database Master Key encryption password must meet DOD password complexity requirements.
SV-271170r1109190_ruleThe 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-271171r1109192_ruleThe certificate used for encryption must be backed up and stored in a secure location that is not on the SQL Server.
SV-271172r1109195_ruleSQL Server must isolate security functions from nonsecurity functions.
SV-271173r1137656_ruleDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data transfer policy.
SV-271176r1109200_ruleSQL Server must check the validity of all data inputs except those specifically identified by the organization.
SV-271179r1108921_ruleSQL Server must provide nonprivileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.
SV-271184r1138541_ruleSQL Server must associate organization-defined types of security labels having organization-defined security label values with information in process, transit, or storage.
SV-271186r1109206_ruleSQL Server must enforce discretionary access control (DAC) policies, as defined by the data owner, over defined subjects and objects.
SV-271188r1167492_ruleExecution of stored procedures and functions that use execute as must be restricted to necessary cases only.
SV-271195r1109208_ruleSQL Server must enforce access restrictions associated with changes to the configuration of the database(s).
SV-271199r1117186_ruleSQL Server must use NSA-approved cryptography to protect classified information in accordance with the data owner’s requirements.
SV-271201r1192914_ruleSQL Server must implement cryptographic mechanisms to prevent unauthorized modification or disclosure of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.
SV-283667r1192917_ruleSQL Server must protect against a user falsely repudiating by ensuring that only unique Active Directory user accounts can connect to the database.