V1R4 changes
Microsoft SQL Server 2022 Instance STIG V1R4 (2026-04-01) replaced V1R3 (2026-01-05): 1 check removed, 1 updated. It has 79 checks, against 80 in V1R3.
V1R4 checklistV1R3 checklist Compare V1R3 and V1R4 in STIG Compare
- 0 added
- 1 removed
- 1 updated
Updated fields: Check text 1
Removed since V1R3 (1)
- V-274453CAT IISQL Server must protect against a user falsely repudiating by ensuring that only clearly unique Active Directory user accounts can connect to the database.
Updated in V1R4 (1)
V-271324CAT ISQL Server must protect the confidentiality and integrity of all information at rest.Check text
Check text
Review system documentation to determine whether the system handles classified information. If the system does not handle classified information, the severity of this check is downgraded to CAT II.
If the application owner and authorizing official (AO) have determined that encryption of data at rest is required, verify that the data on secondary devices is encrypted.
If full-disk encryption is being used, this is not a finding.
If data encryption is required, verify that the data is encrypted before being put on the secondary device by executing the following:
SELECT
db.name AS DatabaseName,
db.is_encrypted AS IsEncrypted,
CASE
WHEN dm.encryption_state = 0 THEN 'No database encryption key present, no encryption'
WHEN dm.encryption_state = 1 THEN 'Unencrypted'
WHEN dm.encryption_state = 2 THEN 'Encryption in progress'
WHEN dm.encryption_state = 3 THEN 'Encrypted'
WHEN dm.encryption_state = 4 THEN 'Key change in progress'
WHEN dm.encryption_state = 5 THEN 'Decryption in progress'
WHEN dm.encryption_state = 6 THEN 'Protection change in progress'
END AS EncryptionState,
dm.encryption_state AS EncryptionState,
dm.key_algorithm AS KeyAlgorithm,
dm.key_length AS KeyLength
FROM
sys.databases db
LEFT JOIN sys.dm_database_encryption_keys dm ON db.database_id = dm.database_id
WHERE db.database_id > 4
ORDER BY [Database NameDatabaseName] ;
For each user database where encryption is required, verify that encryption is in effect. If it is not, this is a finding.
Verify that there are physical security measures, operating system access control lists, and organizational controls appropriate to the sensitivity level of the data in the database(s).; Ifif not, this is a finding.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V1R4 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.