Skip to main content
CUI

Vulnerability V-213911

Back

V-213911

CAT II

The Database Master Key encryption password must meet DOD password complexity requirements.

Ships Affected
1
Total Findings
5
Open
0
Closed
0

Check Text

From the query prompt: SELECT name FROM [master].sys.databases WHERE state = 0 Repeat for each database: From the query prompt: USE [database name] SELECT COUNT(name) FROM sys.symmetric_keys s, sys.key_encryptions k WHERE s.name = '##MS_DatabaseMasterKey##' AND s.symmetric_key_id = k.key_id AND k.crypt_type in ('ESKP', 'ESP2', 'ESP3') If the value returned is zero, this is not applicable. If the value returned is greater than zero, a Database Master Key exists and is encrypted with a password. Review procedures and evidence of password requirements used to encrypt Database Master Keys. If the passwords are not required to meet DoD password standards, currently a minimum of 15 characters with at least 1 upper-case character, 1 lower-case character, 1 special character, and 1 numeric character, and at least 8 characters changed from the previous password, this is a finding.

Fix Text

Assign an encryption password to the Database Master Key that is a minimum of 15 characters with at least 1 upper-case character, 1 lower-case character, 1 special character, and 1 numeric character, and at least 8 characters changed from the previous password. To change the Database Master Key encryption password: USE [database name]; ALTER MASTER KEY REGENERATE WITH ENCRYPTION BY PASSWORD = '[new password]'; Note: The Database Master Key encryption method should not be changed until the effects are thoroughly reviewed. Changing the master key encryption causes all encryption using the Database Master Key to be decrypted and re-encrypted. This action should not be taken during a high-demand time. Please see the MS SQL Server documentation prior to re-encrypting the Database Master Key for detailed information.

STIG Reference

STIG
MS SQL Server 2016 Database Security Technical Implementation Guide
Version
3
Release
5
Rule ID
SV-213911r961128_rule

All Occurrences

This vulnerability appears on 1 ship(s)

Ship Hull # Source File Status Assigned To Scan Date Actions
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_SQL2016DB_MONT-BE-002-BKUPEXEC64_tempdb_V3R3_20251023-144154.ckl
Unassigned 2026-01-14T12:57:40.769694 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_SQL2016DB_MONT-BE-002-BKUPEXEC64_msdb_V3R3_20251023-144148.ckl
Unassigned 2026-01-14T12:57:40.663257 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_SQL2016DB_MONT-BE-002-BKUPEXEC64_model_V3R3_20251023-144128.ckl
Unassigned 2026-01-14T12:57:40.569961 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_SQL2016DB_MONT-BE-002-BKUPEXEC64_master_V3R3_20251023-144120.ckl
Unassigned 2026-01-14T12:57:40.470811 View in Context
USNS MONTFORD POINT T-ESD-1 _Reviewed/MONT-BE-002/Checklist/MONT-BE-002_SQL2016DB_MONT-BE-002-BKUPEXEC64_BEDB_V3R3_20251023-143959.ckl
Unassigned 2026-01-14T12:57:40.371699 View in Context
CUI