# stig_rules

vuln_id: V-214008
rule_id: SV-214008r961812_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records when successful and unsuccessful attempts to delete privileges/permissions occur.

description:
  <VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. 
   
  In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command.  
   
  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add the following events to the SQL Server Audit that is being used for the STIG compliant audit. 
   
  DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP 
  DATABASE_OBJECT_PERMISSION_CHANGE_GROUP 
  DATABASE_OWNERSHIP_CHANGE_GROUP 
  DATABASE_PERMISSION_CHANGE_GROUP 
  DATABASE_ROLE_MEMBER_CHANGE_GROUP 
  SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SERVER_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_PERMISSION_CHANGE_GROUP 
  SERVER_ROLE_MEMBER_CHANGE_GROUP 
   
  See the supplemental file "SQL 2016 Audit.sql".

  Reference: 
  https://msdn.microsoft.com/en-us/library/cc280663.aspx

check_text:
  Check that SQL Server Audit is being used for the STIG compliant audit. 
  Determine if an audit is configured and started by executing the following query. If no records are returned, this is a finding. 

  SELECT name AS 'Audit Name', 
  status_desc AS 'Audit Status', 
  audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status

  Execute the following query to verify the required audit actions are included in the server audit specification: 

  SELECT a.name AS 'AuditName', 
  s.name AS 'SpecName', 
  d.audit_action_name AS 'ActionName', 
  d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1
  AND d.audit_action_name IN ('DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP'
  ,'DATABASE_OBJECT_PERMISSION_CHANGE_GROUP'
  ,'DATABASE_OWNERSHIP_CHANGE_GROUP'
  ,'DATABASE_PERMISSION_CHANGE_GROUP'
  ,'DATABASE_ROLE_MEMBER_CHANGE_GROUP'
  ,'SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP'
  ,'SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP'
  ,'SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP'
  ,'SERVER_OBJECT_PERMISSION_CHANGE_GROUP'
  ,'SERVER_PERMISSION_CHANGE_GROUP'
  ,'SERVER_ROLE_MEMBER_CHANGE_GROUP')

  If the any of the following audit actions are not returned in an active audit, this is a finding.

  DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP 
  DATABASE_OBJECT_PERMISSION_CHANGE_GROUP 
  DATABASE_OWNERSHIP_CHANGE_GROUP 
  DATABASE_PERMISSION_CHANGE_GROUP 
  DATABASE_ROLE_MEMBER_CHANGE_GROUP 
  SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SERVER_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_PERMISSION_CHANGE_GROUP 
  SERVER_ROLE_MEMBER_CHANGE_GROUP 

  Reference: 
  https://msdn.microsoft.com/en-us/library/cc280663.aspx


vuln_id: V-214010
rule_id: SV-214010r961818_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records when successful and unsuccessful attempts to delete security objects occur.

description:
  <VulnDiscussion>The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. 
   
  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

  Satisfies: SRG-APP-000501-DB-000336</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add the "SCHEMA_OBJECT_CHANGE_GROUP" to the server audit specification 
  USE [master]; 
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_CHANGE_GROUP);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON);  
  GO 
   
  See the supplemental script "SQL 2016 Audit.sql" for complete script.

check_text:
  Determine if an audit is configured and started by executing the following query:
   
  SELECT name AS 'Audit Name', 
  status_desc AS 'Audit Status', 
  audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 
   
  If no records are returned, this is a finding.
   
  Execute the following query to verify the "SCHEMA_OBJECT_CHANGE_GROUP" is included in the server audit specification.
   
  SELECT a.name AS 'AuditName', 
  s.name AS 'SpecName', 
  d.audit_action_name AS 'ActionName', 
  d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_CHANGE_GROUP' 
   
  If the "SCHEMA_OBJECT_CHANGE_GROUP" is not returned in an active audit, this is a finding.


vuln_id: V-214012
rule_id: SV-214012r1018597_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records when successful and unsuccessful attempts to delete categorized information (e.g., classification levels/security levels) occur.

description:
  <VulnDiscussion>Changes in categorized information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected. 
   
  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. 
   
  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.

  Satisfies: SRG-APP-000502-DB-000348</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy an audit to audit when data classifications are unsuccessfully deleted. See the supplemental file "SQL 2016 Audit.sql".

check_text:
  Review the system documentation to determine if SQL Server is required to audit when data classifications are successfully and unsuccessfully deleted.
   
  If this is not required, this is not a finding.
   
  If the documentation does not exist, this is a finding.
   
  Determine if an audit is configured and started by executing the following query:
   
  SELECT name AS 'Audit Name', 
    status_desc AS 'Audit Status', 
    audit_file_path AS 'Current Audit File' 
  FROM  sys.dm_server_audit_status 
   
  If no records are returned, this is a finding.
   
  If the auditing the retrieval of privilege/permission/role membership information is required, execute the following query to verify the "SCHEMA_OBJECT_ACCESS_GROUP" is included in the server audit specification.
   
  SELECT a.name AS 'AuditName', 
   s.name AS 'SpecName', 
   d.audit_action_name AS 'ActionName', 
   d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' 
   
  If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.


vuln_id: V-214014
rule_id: SV-214014r961824_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records when successful and unsuccessful logons or connection attempts occur.

description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to SQL Server. It is also necessary to track failed attempts to log on to SQL Server. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured.

  Satisfies: SRG-APP-000503-DB-000350</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add both "SUCCESSFUL_LOGIN_GROUP" and "FAILED_LOGIN_GROUP" to the server audit specification. 
  USE [master];
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SUCCESSFUL_LOGIN_GROUP);  
  GO  

  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (FAILED_LOGIN_GROUP);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON);  
  GO 
   
  Alternatively, enable "Both failed and successful logins".

  In SQL Management Studio:
  Right-click on the instance.
  - Select "Properties".
  - Select "Security" on the left-hand side.
  - Select "Both failed and successful logins". 
  - Click "OK".

check_text:
  Determine if an audit is configured and started by executing the following query: 
   
  SELECT name AS 'Audit Name', 
    status_desc AS 'Audit Status', 
    audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 
   
  Execute the following query to verify the SUCCESSFUL_LOGIN_GROUP and FAILED_LOGIN_GROUP are included in the server audit specification.
   
  SELECT a.name AS 'AuditName', 
    s.name AS 'SpecName', 
   d.audit_action_name AS 'ActionName', 
    d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1 AND d.audit_action_name IN ('SUCCESSFUL_LOGIN_GROUP', 'FAILED_LOGIN_GROUP') 

  If both "SUCCESSFUL_LOGIN_GROUP" and "FAILED_LOGIN_GROUP" are returned in an active audit, this is not a finding.
   
  If both "SUCCESSFUL_LOGIN_GROUP" and "FAILED_LOGIN_GROUP" are not in the active audit, determine whether "Both failed and successful logins" is enabled.
   
  In SQL Management Studio 
  Right-click on the instance 
  >> Select "Properties" 
  >> Select "Security" on the left hand side 
  >> Check the setting for "Login auditing" 
   
  If "Both failed and successful logins" is not selected, this is a finding.


vuln_id: V-214015
rule_id: SV-214015r961827_rule
severity: CAT II
title: SQL Server must generate audit records for all privileged activities or other system-level access.
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
   
  System documentation should include a definition of the functionality considered privileged. 
   
  A privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to: 
  CREATE 
  ALTER 
  DROP 
  GRANT 
  REVOKE 
  DENY 
   
  There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples in SQL include: 
   
  TRUNCATE TABLE; 
  DELETE, or 
  DELETE affecting more than n rows, for some n, or 
  DELETE without a WHERE clause; 
   
  UPDATE or 
  UPDATE affecting more than n rows, for some n, or 
  UPDATE without a WHERE clause; 
   
  any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal. 
   
  Depending on the capabilities of SQL Server and the design of the database and associated applications, audit logging may be achieved by means of DBMS auditing features, database triggers, other mechanisms, or a combination of these. 
   
  Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add the required events to the server audit specification 
  USE [master]; 
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (APPLICATION_ROLE_CHANGE_PASSWORD_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (AUDIT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (BACKUP_RESTORE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OBJECT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OBJECT_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OPERATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_PRINCIPAL_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_PRINCIPAL_IMPERSONATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_ROLE_MEMBER_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DBCC_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (LOGIN_CHANGE_PASSWORD_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OBJECT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OBJECT_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OPERATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_PRINCIPAL_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_PRINCIPAL_IMPERSONATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_ROLE_MEMBER_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_STATE_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (TRACE_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (USER_CHANGE_PASSWORD_GROUP); 
  GO 
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON);  
  GO

check_text:
  Determine if an audit is configured and started by executing the following query:  

  SELECT name AS 'Audit Name', 
  status_desc AS 'Audit Status', 
  audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 

  If no records are returned, this is a finding. 

  Execute the following query to verify the following events are included in the server audit specification: 

  APPLICATION_ROLE_CHANGE_PASSWORD_GROUP 
  AUDIT_CHANGE_GROUP 
  BACKUP_RESTORE_GROUP 
  DATABASE_CHANGE_GROUP 
  DATABASE_OBJECT_CHANGE_GROUP 
  DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP 
  DATABASE_OBJECT_PERMISSION_CHANGE_GROUP 
  DATABASE_OPERATION_GROUP 
  DATABASE_OWNERSHIP_CHANGE_GROUP 
  DATABASE_PERMISSION_CHANGE_GROUP 
  DATABASE_PRINCIPAL_CHANGE_GROUP 
  DATABASE_PRINCIPAL_IMPERSONATION_GROUP 
  DATABASE_ROLE_MEMBER_CHANGE_GROUP 
  DBCC_GROUP 
  LOGIN_CHANGE_PASSWORD_GROUP 
  SCHEMA_OBJECT_CHANGE_GROUP 
  SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OBJECT_CHANGE_GROUP 
  SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SERVER_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OPERATION_GROUP 
  SERVER_PERMISSION_CHANGE_GROUP 
  SERVER_PRINCIPAL_CHANGE_GROUP 
  SERVER_PRINCIPAL_IMPERSONATION_GROUP 
  SERVER_ROLE_MEMBER_CHANGE_GROUP 
  SERVER_STATE_CHANGE_GROUP 
  TRACE_CHANGE_GROUP 
  USER_CHANGE_PASSWORD_GROUP 

  SELECT a.name AS 'AuditName', 
  s.name AS 'SpecName', 
  d.audit_action_name AS 'ActionName', 
  d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1  
  AND d.audit_action_name IN ('APPLICATION_ROLE_CHANGE_PASSWORD_GROUP','AUDIT_CHANGE_GROUP','BACKUP_RESTORE_GROUP','DATABASE_CHANGE_GROUP','DATABASE_OBJECT_CHANGE_GROUP','DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP','DATABASE_OBJECT_PERMISSION_CHANGE_GROUP','DATABASE_OPERATION_GROUP','DATABASE_OWNERSHIP_CHANGE_GROUP','DATABASE_PERMISSION_CHANGE_GROUP','DATABASE_PRINCIPAL_CHANGE_GROUP','DATABASE_PRINCIPAL_IMPERSONATION_GROUP','DATABASE_ROLE_MEMBER_CHANGE_GROUP','DBCC_GROUP','LOGIN_CHANGE_PASSWORD_GROUP','SCHEMA_OBJECT_CHANGE_GROUP','SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP','SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP','SERVER_OBJECT_CHANGE_GROUP','SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP','SERVER_OBJECT_PERMISSION_CHANGE_GROUP','SERVER_OPERATION_GROUP','SERVER_PERMISSION_CHANGE_GROUP','SERVER_PRINCIPAL_CHANGE_GROUP','SERVER_PRINCIPAL_IMPERSONATION_GROUP','SERVER_ROLE_MEMBER_CHANGE_GROUP','SERVER_STATE_CHANGE_GROUP','TRACE_CHANGE_GROUP','USER_CHANGE_PASSWORD_GROUP') 

  If the identified groups are not returned, this is a finding.


vuln_id: V-214016
rule_id: SV-214016r961827_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

description:
  <VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.  
   
  System documentation should include a definition of the functionality considered privileged. 
   
  A privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to: 
  CREATE 
  ALTER 
  DROP 
  GRANT 
  REVOKE 
  DENY 
   
  Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity. 
   
  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add the required events to the server audit specification 
  USE [master]; 
  GO  

  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);  
  GO  

  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (APPLICATION_ROLE_CHANGE_PASSWORD_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (AUDIT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (BACKUP_RESTORE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OBJECT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OBJECT_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OPERATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_PRINCIPAL_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_PRINCIPAL_IMPERSONATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DATABASE_ROLE_MEMBER_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (DBCC_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (LOGIN_CHANGE_PASSWORD_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (LOGOUT_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OBJECT_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OBJECT_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_OPERATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_PERMISSION_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_PRINCIPAL_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_PRINCIPAL_IMPERSONATION_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_ROLE_MEMBER_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SERVER_STATE_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (TRACE_CHANGE_GROUP); 
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (USER_CHANGE_PASSWORD_GROUP); 
  GO 

  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON);  
  GO

check_text:
  Determine if an audit is configured and started by executing the following query.  

  SELECT name AS 'Audit Name', 
  status_desc AS 'Audit Status', 
  audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 

  If no records are returned, this is a finding. 

  Execute the following query to verify the following events are included in the server audit specification: 

  APPLICATION_ROLE_CHANGE_PASSWORD_GROUP 
  AUDIT_CHANGE_GROUP 
  BACKUP_RESTORE_GROUP 
  DATABASE_CHANGE_GROUP 
  DATABASE_OBJECT_CHANGE_GROUP 
  DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP 
  DATABASE_OBJECT_PERMISSION_CHANGE_GROUP 
  DATABASE_OPERATION_GROUP 
  DATABASE_OWNERSHIP_CHANGE_GROUP 
  DATABASE_PERMISSION_CHANGE_GROUP 
  DATABASE_PRINCIPAL_CHANGE_GROUP 
  DATABASE_PRINCIPAL_IMPERSONATION_GROUP 
  DATABASE_ROLE_MEMBER_CHANGE_GROUP 
  DBCC_GROUP 
  LOGIN_CHANGE_PASSWORD_GROUP
  LOGOUT_GROUP 
  SCHEMA_OBJECT_CHANGE_GROUP 
  SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OBJECT_CHANGE_GROUP 
  SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SERVER_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OPERATION_GROUP 
  SERVER_PERMISSION_CHANGE_GROUP 
  SERVER_PRINCIPAL_CHANGE_GROUP 
  SERVER_PRINCIPAL_IMPERSONATION_GROUP 
  SERVER_ROLE_MEMBER_CHANGE_GROUP 
  SERVER_STATE_CHANGE_GROUP 
  TRACE_CHANGE_GROUP 
  USER_CHANGE_PASSWORD_GROUP 

  SELECT a.name AS 'AuditName', 
  s.name AS 'SpecName', 
  d.audit_action_name AS 'ActionName', 
  d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1  
  AND d.audit_action_name IN ('APPLICATION_ROLE_CHANGE_PASSWORD_GROUP',
  'AUDIT_CHANGE_GROUP',
  'BACKUP_RESTORE_GROUP',
  'DATABASE_CHANGE_GROUP',
  'DATABASE_OBJECT_CHANGE_GROUP',
  'DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP',
  'DATABASE_OBJECT_PERMISSION_CHANGE_GROUP',
  'DATABASE_OPERATION_GROUP',
  'DATABASE_OWNERSHIP_CHANGE_GROUP',
  'DATABASE_PERMISSION_CHANGE_GROUP',
  'DATABASE_PRINCIPAL_CHANGE_GROUP',
  'DATABASE_PRINCIPAL_IMPERSONATION_GROUP',
  'DATABASE_ROLE_MEMBER_CHANGE_GROUP',
  'DBCC_GROUP',
  'LOGIN_CHANGE_PASSWORD_GROUP',
  'LOGOUT_GROUP',
  'SCHEMA_OBJECT_CHANGE_GROUP',
  'SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP',
  'SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP',
  'SERVER_OBJECT_CHANGE_GROUP',
  'SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP',
  'SERVER_OBJECT_PERMISSION_CHANGE_GROUP',
  'SERVER_OPERATION_GROUP',
  'SERVER_PERMISSION_CHANGE_GROUP',
  'SERVER_PRINCIPAL_CHANGE_GROUP',
  'SERVER_PRINCIPAL_IMPERSONATION_GROUP',
  'SERVER_ROLE_MEMBER_CHANGE_GROUP',
  'SERVER_STATE_CHANGE_GROUP',
  'TRACE_CHANGE_GROUP',
  'USER_CHANGE_PASSWORD_GROUP'
  )
  Order by d.audit_action_name


  If the identified groups are not returned, this is a finding.


vuln_id: V-214017
rule_id: SV-214017r961830_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records showing starting and ending time for user access to the database(s).

description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to SQL Server lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs.  
   
  Disconnection may be initiated by the user or forced by the system (as in a timeout) or result from a system or network failure. To the greatest extent possible, all disconnections must be logged.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add the "LOGOUT_GROUP" to the server audit specification 
  USE [master]; 
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (LOGOUT_GROUP);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON);  
  GO

check_text:
  Determine if an audit is configured and started by executing the following query:  

  SELECT name AS 'Audit Name', 
  status_desc AS 'Audit Status', 
  audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 

  If no records are returned, this is a finding. 

  Execute the following query to verify the following events are included in the server audit specification: 

  APPLICATION_ROLE_CHANGE_PASSWORD_GROUP 
  AUDIT_CHANGE_GROUP 
  BACKUP_RESTORE_GROUP 
  DATABASE_CHANGE_GROUP 
  DATABASE_OBJECT_CHANGE_GROUP 
  DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP 
  DATABASE_OBJECT_PERMISSION_CHANGE_GROUP 
  DATABASE_OPERATION_GROUP 
  DATABASE_OWNERSHIP_CHANGE_GROUP 
  DATABASE_PERMISSION_CHANGE_GROUP 
  DATABASE_PRINCIPAL_CHANGE_GROUP 
  DATABASE_PRINCIPAL_IMPERSONATION_GROUP 
  DATABASE_ROLE_MEMBER_CHANGE_GROUP 
  DBCC_GROUP 
  LOGIN_CHANGE_PASSWORD_GROUP
  LOGOUT_GROUP 
  SCHEMA_OBJECT_CHANGE_GROUP 
  SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OBJECT_CHANGE_GROUP 
  SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP 
  SERVER_OBJECT_PERMISSION_CHANGE_GROUP 
  SERVER_OPERATION_GROUP 
  SERVER_PERMISSION_CHANGE_GROUP 
  SERVER_PRINCIPAL_CHANGE_GROUP 
  SERVER_PRINCIPAL_IMPERSONATION_GROUP 
  SERVER_ROLE_MEMBER_CHANGE_GROUP 
  SERVER_STATE_CHANGE_GROUP 
  TRACE_CHANGE_GROUP 
  USER_CHANGE_PASSWORD_GROUP 

  SELECT a.name AS 'AuditName', 
  s.name AS 'SpecName', 
  d.audit_action_name AS 'ActionName', 
  d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1  
  AND d.audit_action_name IN ('APPLICATION_ROLE_CHANGE_PASSWORD_GROUP',
  'AUDIT_CHANGE_GROUP',
  'BACKUP_RESTORE_GROUP',
  'DATABASE_CHANGE_GROUP',
  'DATABASE_OBJECT_CHANGE_GROUP',
  'DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP',
  'DATABASE_OBJECT_PERMISSION_CHANGE_GROUP',
  'DATABASE_OPERATION_GROUP',
  'DATABASE_OWNERSHIP_CHANGE_GROUP',
  'DATABASE_PERMISSION_CHANGE_GROUP',
  'DATABASE_PRINCIPAL_CHANGE_GROUP',
  'DATABASE_PRINCIPAL_IMPERSONATION_GROUP',
  'DATABASE_ROLE_MEMBER_CHANGE_GROUP',
  'DBCC_GROUP',
  'LOGIN_CHANGE_PASSWORD_GROUP',
  'LOGOUT_GROUP',
  'SCHEMA_OBJECT_CHANGE_GROUP',
  'SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP',
  'SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP',
  'SERVER_OBJECT_CHANGE_GROUP',
  'SERVER_OBJECT_OWNERSHIP_CHANGE_GROUP',
  'SERVER_OBJECT_PERMISSION_CHANGE_GROUP',
  'SERVER_OPERATION_GROUP',
  'SERVER_PERMISSION_CHANGE_GROUP',
  'SERVER_PRINCIPAL_CHANGE_GROUP',
  'SERVER_PRINCIPAL_IMPERSONATION_GROUP',
  'SERVER_ROLE_MEMBER_CHANGE_GROUP',
  'SERVER_STATE_CHANGE_GROUP',
  'TRACE_CHANGE_GROUP',
  'USER_CHANGE_PASSWORD_GROUP'
  )
  Order by d.audit_action_name


  If the identified groups are not returned, this is a finding.


vuln_id: V-214018
rule_id: SV-214018r961833_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must generate audit records when concurrent logons/connections by the same user from different workstations occur.

description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to track who logs on to SQL Server. 
   
  Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised. 
   
  (If the fact of multiple, concurrent logons by a given user can be reliably reconstructed from the log entries for other events (logons/connections; voluntary and involuntary disconnections), then it is not mandatory to create additional log entries specifically for this.)</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Add the "SUCCESSFUL_LOGIN_GROUP" to the server audit specification. 
  USE [master]; 
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = OFF);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION ADD (SUCCESSFUL_LOGIN_GROUP);  
  GO  
   
  ALTER SERVER AUDIT SPECIFICATION STIG_AUDIT_SERVER_SPECIFICATION WITH (STATE = ON);  
  GO 
   
  Alternatively, enable "Both failed and successful logins" 
  In SQL Management Studio: 
  Right-click on the instance >> Select "Properties" >> Select "Security" on the left hand side >> Select "Both failed and successful logins" >> Click "OK"

check_text:
  Determine if an audit is configured and started by executing the following query. 
   
  SELECT name AS 'Audit Name', 
    status_desc AS 'Audit Status', 
    audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 
   
  If no records are returned, this is a finding. 
   
  Execute the following query to verify the "SUCCESSFUL_LOGIN_GROUP" is included in the server audit specification. 
   
  SELECT a.name AS 'AuditName', 
  s.name AS 'SpecName', 
  d.audit_action_name AS 'ActionName', 
  d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SUCCESSFUL_LOGIN_GROUP' 
   
  If the "SUCCESSFUL_LOGIN_GROUP" is returned in an active audit, this is not a finding. 
   
  If "SUCCESSFUL_LOGIN_GROUP" is not in the active audit, determine whether "Both failed and successful logins" is enabled. 
   
  In SQL Management Studio: 
  Right-click on the instance >> Select "Properties" >> Select "Security" on the left hand side >> Check the setting for "Login auditing" 
   
  If "Both failed and successful logins" is not selected, this is a finding.


vuln_id: V-214020
rule_id: SV-214020r961836_rule
severity: CAT II
title: SQL Server must generate audit records when successful and unsuccessful accesses to objects occur.
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one.  
   
  In an SQL environment, types of access include, but are not necessarily limited to: 
  SELECT 
  INSERT 
  UPDATE 
  DELETE 
  EXECUTE 
   
  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

  Satisfies: SRG-APP-000507-DB-000356</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy an audit to audit when successful and unsuccessful accesses to objects occur. See the supplemental file "SQL 2016 Audit.sql".

check_text:
  Review the system documentation to determine if SQL Server is required to audit when successful and unsuccessful accesses to objects occur. 
   
  If this is not required, this is not a finding. 
   
  If the documentation does not exist, this is a finding. 
   
  Determine if an audit is configured and started by executing the following query:  
   
  SELECT name AS 'Audit Name', 
    status_desc AS 'Audit Status', 
    audit_file_path AS 'Current Audit File' 
  FROM sys.dm_server_audit_status 
   
  If no records are returned, this is a finding. 
   
  If the auditing the retrieval of privilege/permission/role membership information is required, execute the following query to verify the "SCHEMA_OBJECT_ACCESS_GROUP" is included in the server audit specification. 
   
  SELECT a.name AS 'AuditName', 
   s.name AS 'SpecName', 
   d.audit_action_name AS 'ActionName', 
   d.audited_result AS 'Result' 
  FROM sys.server_audit_specifications s 
  JOIN sys.server_audits a ON s.audit_guid = a.audit_guid 
  JOIN sys.server_audit_specification_details d ON s.server_specification_id = d.server_specification_id 
  WHERE a.is_state_enabled = 1 AND d.audit_action_name = 'SCHEMA_OBJECT_ACCESS_GROUP' 
   
  If the "SCHEMA_OBJECT_ACCESS_GROUP" is not returned in an active audit, this is a finding.


vuln_id: V-214021
rule_id: SV-214021r961839_rule
severity: CAT II
title: SQL Server must generate audit records for all direct access to the database(s).
cci: CCI-000172
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>In this context, direct access is any query, command, or call to SQL Server that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and non-standard sources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Check the system documentation for required SQL Server Audits. Remove any Audit filters that exclude or reduce required auditing. Update filters to ensure administrative activity is not excluded.

check_text:
  Determine whether any Server Audits are configured to filter records. From SQL Server Management Studio execute the following query: 
   
  SELECT name AS AuditName, predicate AS AuditFilter  
  FROM sys.server_audits  
  WHERE predicate IS NOT NULL 
   
  If any audits are returned, review the associated filters to determine whether administrative activities are being excluded.  
   
  If any audits are configured to exclude administrative activities, this is a finding.


vuln_id: V-214022
rule_id: SV-214022r961857_rule
severity: CAT I
cci: CCI-002450
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. 
   
  For detailed information, refer to NIST FIPS Publication 140-2 or Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  In Windows, open Administrative Tools >> Local Security Policy. 

  Expand Local Policies >> Security Options. 

  In the right-side pane, double-click on "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing."

check_text:
  Verify that Windows is configured to require the use of FIPS compliant algorithms. 
   
  Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography:  Use FIPS compliant algorithms for encryption, hashing, and signing." 
   
  If the Security Setting for this option is "Disabled" this is a finding.


vuln_id: V-214023
rule_id: SV-214023r961857_rule
severity: CAT I
cci: CCI-002450
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. 
   
  For detailed information, refer to NIST FIPS Publication 140-2 or Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure Windows to require the use of FIPS compliant algorithms. 
   
  Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography:  Use FIPS compliant algorithms for encryption, hashing, and signing." >> Change the Setting option to "Enabled" >> Restart Windows

check_text:
  Verify that Windows is configured to require the use of FIPS-compliant algorithms.

  Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography:  Use FIPS compliant algorithms for encryption, hashing, and signing."

  If  "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding.


vuln_id: V-214024
rule_id: SV-214024r961857_rule
severity: CAT II
cci: CCI-002450
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. 
   
  It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards. 
   
  For detailed information, refer to NIST FIPS Publication 140-2 or Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure Windows to require the use of FIPS compliant algorithms for the unclassified information that requires it. 
   
  Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography:  Use FIPS compliant algorithms for encryption, hashing, and signing." >> Change the Setting option to "Enabled" >> Restart Windows

check_text:
  Review the server documentation, if this system does not contain data that must be encrypted, this finding is NA.

  Verify that Windows is configured to require the use of FIPS compliant algorithms for the unclassified information that requires it.

  Click Start >> Type "Local Security Policy" >> Press Enter >> Expand "Local Policies" >> Select "Security Options" >> Locate "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing."

  If  "System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" is not enabled, this is a finding.


vuln_id: V-214025
rule_id: SV-214025r961860_rule
severity: CAT II
cci: CCI-001851
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  The system SQL Server must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.

description:
  <VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration. 
   
  Off-loading is a common process in information systems with limited audit storage capacity. 
   
  The system SQL Server may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the system or deploy and configure software tools to transfer audit records to a centralized log management system, continuously and in near-real time where a continuous network connection to the log management system exists, or at least weekly in the absence of such a connection.

check_text:
  Review the system documentation for a description of how audit records are off-loaded. 
   
  If the system has a continuous network connection to the centralized log management system, but the DBMS audit records are not written directly to the centralized log management system or transferred in near-real-time, this is a finding. 
   
  If the system does not have a continuous network connection to the centralized log management system, and the DBMS audit records are not transferred to the centralized log management system weekly or more often, this is a finding.


vuln_id: V-214026
rule_id: SV-214026r961863_rule
severity: CAT II
title: SQL Server must configure Customer Feedback and Error Reporting.
cci: CCI-000366
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>By default, Microsoft SQL Server enables participation in the customer experience improvement program (CEIP). This program collects information about how its customers are using the product. Specifically, SQL Server collects information about the installation experience, feature usage, and performance. This information helps Microsoft improve the product to better meet customer needs.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  To disable participation in the CEIP program, change the value of the following registry keys to zero (0). 
   
  To enable participation in the CEIP program, change the value of the following registry keys to one (1). 
   
  HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\[InstanceId]\CPE\CustomerFeedback 
  HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\[InstanceId]\CPE\EnableErrorReporting 
  HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\130\CustomerFeedback 
  HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\130\EnableErrorReporting

check_text:
  Launch "Registry Editor" 
   
  Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\[InstanceId]\CPE 
  Review the following values:  CustomerFeedback, EnableErrorReporting 
   
  Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\130 
  Review the following values:  CustomerFeedback, EnableErrorReporting 
   
  If this is a classified system, and any of the above values are not zero (0), this is a finding. 
   
  If this is an unclassified system, review the server documentation to determine whether CEIP participation is authorized. 
   
  If CEIP participation is not authorized, and any of the above values are one (1), this is a finding.


vuln_id: V-214027
rule_id: SV-214027r961863_rule
severity: CAT II
title: SQL Server must configure SQL Server Usage and Error Reporting Auditing.
cci: CCI-000366
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>By default, Microsoft SQL Server enables participation in the customer experience improvement program (CEIP). This program collects information about how its customers are using the product. Specifically, SQL Server collects information about the installation experience, feature usage, and performance. This information helps Microsoft improve the product to better meet customer needs. The Local Audit component of SQL Server Usage Feedback collection writes data collected by the service to a designated folder, representing the data (logs) that will be sent to Microsoft. The purpose of the Local Audit is to allow customers to see all data Microsoft collects with this feature, for compliance, regulatory or privacy validation reasons.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the instance to audit telemetry data. More information about auditing telemetry data can be found at https://msdn.microsoft.com/en-us/library/mt743085.aspx. 
   
  Create a folder to store the telemetry audit data in. 
   
  Grant the SQLTELEMETRY service the following permissions on the folder: 
   
  - List folder contents 
  - Read 
  - Write 
   
  Create and configure the following registry key: 
  Note: InstanceId refers to the type and instance of the feature. (e.g., MSSQL13.SqlInstance, MSAS13.SSASInstance, MSRS13.SSRSInstance) 
   
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\[InstanceId]\CPE\UserRequestedLocalAuditDirectory [string] 
   
  Set the "UserRequestedLocalAuditDirectory" key value to the path of the telemetry audit folder. 
   
  Set the telemetry service to start automatically. Restart the service. 
  - For Database Engine, use SQL Server CEIP service (<INSTANCENAME>). 
  - For Analysis Services, use SQL Server Analysis Services CEIP (<INSTANCENAME>).

check_text:
  Review the server documentation to determine if auditing of the telemetry data is required. If auditing of telemetry data is not required, this is not a finding. 
   
  If auditing of telemetry data is required, determine the telemetry service user name by executing the following query: 
   
  SELECT name 
  FROM sys.server_principals 
  WHERE name LIKE '%SQLTELEMETRY%' 
   
  Review the values of the following registry key: 
  Note: InstanceId refers to the type and instance of the feature. (e.g., MSSQL13.SqlInstance, MSAS13.SSASInstance, MSRS13.SSRSInstance) 
   
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\[InstanceId]\CPE\UserRequestedLocalAuditDirectory 
   
  If the registry key do not exist or the value is blank, this is a finding. 
   
  Navigate the path defined in the "UserRequestedLocalAuditDirectory" registry key in file explorer. 
   
  Right-click on the folder and choose "Properties". 
  Open the "Security" tab.
   
  Verify the SQLTELEMETRY account has the following permissions: 
   
  - List folder contents 
  - Read 
  - Write 
   
  If the permissions are not set properly on the folder, this is a finding. 
   
  Open services.msc and find the telemetry service. 
  - For Database Engine, use SQL Server CEIP service (<INSTANCENAME>). 
  - For Analysis Services, use SQL Server Analysis Services CEIP (<INSTANCENAME>). 
   
  Right-click on the service and choose "Properties". Verify the "Startup type" is "Automatic."  
   
  If the service is not configured to automatically start, this is a finding. 
   
  Review the processes and procedures for reviewing the telemetry data. If there is evidence that the telemetry data is periodically reviewed in accordance with the processes and procedures, this is not a finding. 
   
  If no processes and procedures exist for reviewing telemetry data, this is a finding.


vuln_id: V-214028
rule_id: SV-214028r960792_rule
severity: CAT I
title: The SQL Server default account [sa] must be disabled.
cci: CCI-000213
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>SQL Server's [sa] account has special privileges required to administer the database. The [sa] account is a well-known SQL Server account and is likely to be targeted by attackers and thus more prone to providing unauthorized access to the database. 

  This [sa] default account is administrative and could lead to catastrophic consequences, including the complete loss of control over SQL Server. If the [sa] default account is not disabled, an attacker might be able to gain access through the account. SQL Server by default disables the [sa] account at installation. 

  Some applications that run on SQL Server require the [sa] account to be enabled for the application to function properly. These applications that require the [sa] account to be enabled are usually legacy systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify the enabled flag of SQL Server's [sa] (system administrator) account by running the following script.
  USE master; 
  GO 
  ALTER LOGIN [sa] DISABLE; 
  GO

check_text:
  Check SQL Server settings to determine if the [sa] (system administrator) account has been disabled by executing the following query:

  USE master;
  GO
  SELECT name, is_disabled
  FROM sys.sql_logins
  WHERE principal_id = 1;
  GO

  Verify that the "name" column contains the current name of the [sa] database server account.

  If the "is_disabled" column is not set to "1", this is a finding.


vuln_id: V-214029
rule_id: SV-214029r960963_rule
severity: CAT II
title: SQL Server default account [sa] must have its name changed.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>SQL Server's [sa] account has special privileges required to administer the database. The [sa] account is a well-known SQL Server account name and is likely to be targeted by attackers, and is thus more prone to providing unauthorized access to the database. 

  Since the SQL Server [sa] is administrative in nature, the compromise of a default account can have catastrophic consequences, including the complete loss of control over SQL Server. Since SQL Server needs for this account to exist and it should not be removed, one way to mitigate this risk is to change the [sa] account name.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify the SQL Server's [sa] (system administrator) account by running the following script:

  USE master; 
  GO 
  ALTER LOGIN [sa] WITH NAME = <new name> 
  GO

check_text:
  Verify the SQL Server default [sa] (system administrator) account name has been changed by executing the following query: 

  USE master; 
  GO 
  SELECT * 
  FROM sys.sql_logins 
  WHERE [name] = 'sa' OR [principal_id] = 1; 
  GO 

  If the login account name "SA" or "sa" appears in the query output, this is a finding.


vuln_id: V-214030
rule_id: SV-214030r961359_rule
severity: CAT II
title: Execution of startup stored procedures must be restricted to necessary cases only.
cci: CCI-002233
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations.

  When 'Scan for startup procs' is enabled, SQL Server scans for and runs all automatically run stored procedures defined on the server.  The execution of start-up stored procedures will be done under a high privileged context, therefore it is a commonly used post-exploitation vector.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  To disable start up stored procedure(s), run the following in Master for each undocumented procedure:

  sp_procoption @procname = '<procedure name>', @OptionName = 'Startup', @optionValue = 'Off'

check_text:
  Review the system documentation to obtain a listing of documented stored procedures used by SQL Server during start up. Execute the following query:

  Select [name] as StoredProc
  From sys.procedures
  Where OBJECTPROPERTY(OBJECT_ID, 'ExecIsStartup') = 1

  If any stored procedures are returned that are not documented, this is a finding.


vuln_id: V-214031
rule_id: SV-214031r961863_rule
severity: CAT II
title: SQL Server Mirroring endpoint must utilize AES encryption.
cci: CCI-000366
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.

  Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. 

  SQL Mirroring endpoints support different encryption algorithms, including no-encryption. Using a weak encryption algorithm or plaintext in communication protocols can lead to data loss, data manipulation and/or connection hijacking.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Run the following to enable encryption on the mirroring endpoint:

  ALTER ENDPOINT <Endpoint Name>
  FOR DATABASE_MIRRORING
  (ENCRYPTION = REQUIRED ALGORITHM AES)

check_text:
  If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, and the requirement is documented and authorized, this is not a finding.

  If Database Mirroring is in use, run the following to check for encrypted transmissions:  

  SELECT name, type_desc, encryption_algorithm_desc
  FROM sys.database_mirroring_endpoints
  WHERE encryption_algorithm != 2

  If any records are returned, this is a finding.


vuln_id: V-214032
rule_id: SV-214032r961863_rule
severity: CAT II
title: SQL Server Service Broker endpoint must utilize AES encryption.
cci: CCI-000366
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.

  Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. 

  SQL Server Service Broker endpoints support different encryption algorithms, including no-encryption. Using a weak encryption algorithm or plaintext in communication protocols can lead to data loss, data manipulation and/or connection hijacking.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Run the following to enable encryption on the Service Broker endpoint:

  ALTER ENDPOINT <EndpointName>
  FOR SERVICE_BROKER
  (ENCRYPTION = REQUIRED ALGORITHM AES)

check_text:
  If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, and the requirement is documented and authorized, this is not a finding.

  If SQL Service Broker is in use, run the following to check for encrypted transmissions:  

  SELECT name, type_desc, encryption_algorithm_desc
  FROM sys.service_broker_endpoints
  WHERE encryption_algorithm != 2

  If any records are returned, this is a finding.


vuln_id: V-214033
rule_id: SV-214033r960963_rule
severity: CAT II
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server execute permissions to access the registry must be revoked, unless specifically required and approved.

description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system.

  The registry contains sensitive information, including password hashes as well as clear text passwords. Registry extended stored procedures allow Microsoft SQL Server to access the machine's registry. The sensitivity of these procedures are exacerbated if Microsoft SQL Server is run under the Windows account LocalSystem. LocalSystem can read and write nearly all values in the registry, even those not accessible by the Administrator. Unlike the xp_cmdshell extended stored procedure, which runs under a separate context if executed by a login not in the sysadmin role, the registry extended stored procedures always execute under the security context of the MSSQLServer service. Because the sensitive information is stored in the registry, it is essential that access to that information be properly guarded.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Remove execute permissions to any registry extended stored procedure from all users (other than dbo).

  USE master
  GO
  REVOKE EXECUTE ON [<procedureName>] FROM [<principal>]
  GO

check_text:
  To determine if permissions to execute registry extended stored procedures have been revoked from all users (other than dbo), execute the following command:

  SELECT OBJECT_NAME(major_id) AS [Stored Procedure]
  ,dpr.NAME AS [Principal]
  FROM sys.database_permissions AS dp
  INNER JOIN sys.database_principals AS dpr ON dp.grantee_principal_id = dpr.principal_id
  WHERE major_id IN (
   OBJECT_ID('xp_regaddmultistring')
  ,OBJECT_ID('xp_regdeletekey')
  ,OBJECT_ID('xp_regdeletevalue')
  ,OBJECT_ID('xp_regenumvalues')
  ,OBJECT_ID('xp_regenumkeys')
  ,OBJECT_ID('xp_regremovemultistring')
  ,OBJECT_ID('xp_regwrite')
  ,OBJECT_ID('xp_instance_regaddmultistring')
  ,OBJECT_ID('xp_instance_regdeletekey')
  ,OBJECT_ID('xp_instance_regdeletevalue')
  ,OBJECT_ID('xp_instance_regenumkeys')
  ,OBJECT_ID('xp_instance_regenumvalues')
  ,OBJECT_ID('xp_instance_regremovemultistring')
  ,OBJECT_ID('xp_instance_regwrite')
  )
  AND dp.[type] = 'EX'
  ORDER BY dpr.NAME;

  If any records are returned, review the system documentation to determine whether the accessing of the registry via  extended stored procedures are required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214034
rule_id: SV-214034r960963_rule
severity: CAT II
title: Filestream must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  The most significant potential for attacking an instance is through the use of features that expose an external interface or ad hoc execution capability. FILESTREAM integrates the SQL Server Database Engine with an NTFS file system by storing varbinary(max) binary large object (BLOB) data as files on the file system. Transact-SQL statements can insert, update, query, search, and back up FILESTREAM data.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable the use of Filestream.

  1. Delete all FILESTREAM columns from all tables. ALTER TABLE <name> DROP COLUMN <column name>
  2. Disassociate tables from the FILESTREAM filegroups. ALTER TABLE <name> SET (FILESTREAM_ON = 'NULL'
  3. Remove all FILESTREAM data containers. ALTER DATABASE <name> REMOVE FILE <file name>
  4. Remove all FILESTREAM filegroups. ALTER DATABASE <name> REMOVE FILEGROUP <file name>.
  5. Disable FILESTREAM.
  EXEC sp_configure filestream_access_level, 0 
      RECONFIGURE 
  6. Restart the SQL Service

check_text:
  Review the system documentation to see if FileStream is in use.  If in use authorized, this is not a finding.   

  If FileStream is not documented as being authorized, execute the following query.
  EXEC sp_configure 'filestream access level'

  If "run_value" is greater than "0", this is a finding.



  This rule checks that Filestream SQL specific option is disabled.

  SELECT CASE 
          WHEN EXISTS (SELECT * 
                       FROM sys.configurations 
                       WHERE Name = 'filestream access level' 
                              AND Cast(value AS INT) = 0) THEN 'No' 
          ELSE 'Yes'
        END AS TSQLFileStreamAccess;

  If the above query returns "Yes" in the "FileStreamEnabled" field, this is a finding.


vuln_id: V-214035
rule_id: SV-214035r960963_rule
severity: CAT II
title: Ole Automation Procedures feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system.

  SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The Ole Automation Procedures option controls whether OLE Automation objects can be instantiated within Transact-SQL batches. These are extended stored procedures that allow SQL Server users to execute functions external to SQL Server in the security context of SQL Server.

  The Ole Automation Procedures extended stored procedure allows execution of host executables outside the controls of database access permissions. This access may be exploited by malicious users who have compromised the integrity of the SQL Server database process to control the host operating system to perpetrate additional malicious activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Ole Automation Procedures" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'Ole Automation Procedures', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "Ole Automation Procedures" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'Ole Automation Procedures'; 

  If the value of "config_value" is "0", this is not a finding. 

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "Ole Automation Procedures" is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214036
rule_id: SV-214036r960963_rule
severity: CAT II
title: SQL Server User Options feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The user options option specifies global defaults for all users. A list of default query processing options is established for the duration of a user's work session. The user options option allows you to change the default values of the SET options (if the server's default settings are not appropriate).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "User Options" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'user options', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "User Options" option is enabled, execute the following query:

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'user options'; 

  If the value of "config_value" is "0", this is not a finding. 

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "user options" is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214037
rule_id: SV-214037r960963_rule
severity: CAT II
title: Remote Access feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system.

  SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The Remote Access option controls the execution of local stored procedures on remote servers or remote stored procedures on local server.  'Remote access' functionality can be abused to launch a Denial-of-Service (DoS) attack on remote servers by off-loading query processing to a target.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Remote Access" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'remote access', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "Remote Access" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'remote access'; 

  If the value of "config_value" is "0", this is not a finding. 

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "Remote Access" is required (linked servers) and authorized. If it is not authorized, this is a finding.


vuln_id: V-214038
rule_id: SV-214038r960963_rule
severity: CAT II
title: Hadoop Connectivity feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system.

  SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The Hadoop Connectivity feature allows multiple types of external data sources to be created and used across all sessions on the server.  An exploit to the SQL Server instance could result in a compromise of the host system and external SQL Server resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Hadoop Connectivity" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'hadoop connectivity', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "Hadoop Connectivity" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'hadoop connectivity'; 

  If the value of "config_value" is "0", this is not a finding.

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "Hadoop Connectivity" option is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214039
rule_id: SV-214039r960963_rule
severity: CAT II
title: Allow Polybase Export feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system.

  SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The Allow Polybase Export feature allows an export of data to an external data source such as Hadoop File System or Azure Data Lake. An exploit to the SQL Server instance could result in a compromise of the host system and external SQL Server resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Allow Polybase Export" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'allow polybase export', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "Allow Polybase Export" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'allow polybase export'; 

  If the value of "config_value" is "0", this is not a finding.

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "Allow Polybase Export" is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214040
rule_id: SV-214040r960963_rule
severity: CAT II
title: Remote Data Archive feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  SQL Server may spawn additional external processes to execute procedures that are defined in the SQL Server but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than SQL Server and provide unauthorized access to the host system.

  SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The Remote Data Archive feature allows an export of local SQL Server data to an Azure SQL Database. An exploit to the SQL Server instance could result in a compromise of the host system and external SQL Server resources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Remote Data Archive" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'remote data archive', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "Remote Data Archive" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'remote data archive'; 

  If the value of "config_value" is "0", this is not a finding. 

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "Remote Data Archive" is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214041
rule_id: SV-214041r960963_rule
severity: CAT II
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  SQL Server External Scripts Enabled feature must be disabled, unless specifically required and approved.

description:
  <VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  The External Scripts Enabled feature allows scripts external to SQL such as files located in an R library to be executed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "External Scripts Enabled" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'external scripts enabled', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if "External Scripts Enabled" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'external scripts enabled'; 

  If the value of "config_value" is "0", this is not a finding. 

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "External Scripts Enabled" is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214042
rule_id: SV-214042r961863_rule
severity: CAT III
title: The SQL Server Browser service must be disabled unless specifically required and approved.
cci: CCI-000366
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>The SQL Server Browser simplifies the administration of SQL Server, particularly when multiple instances of SQL Server coexist on the same computer. It avoids the need to hard-assign port numbers to the instances and to set and maintain those port numbers in client systems. It enables administrators and authorized users to discover database management system instances, and the databases they support, over the network. SQL Server uses the SQL Server Browser service to enumerate instances of the Database Engine installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the Database Engine on the same computer.

  This convenience also presents the possibility of unauthorized individuals gaining knowledge of the available SQL Server resources. Therefore, it is necessary to consider whether the SQL Server Browser is needed. Typically, if only a single instance is installed, using the default name (MSSQLSERVER) and port assignment (1433), the Browser is not adding any value. The more complex the installation, the more likely SQL Server Browser is to be helpful. 

  This requirement is not intended to prohibit use of the Browser service in any circumstances.  It calls for administrators and management to consider whether the benefits of its use outweigh the potential negative consequences of it being used by an attacker to browse the current infrastructure and retrieve a list of running SQL Server instances.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  If SQL Server Browser is needed, document the justification and obtain the appropriate authorization. 

  Where SQL Server Browser is judged unnecessary, the Service can be disabled. 

  To disable, in the Services tool, double-click "SQL Server Browser". Set "Startup Type" to "Disabled". If "Service Status" is "Running", click on "Stop". Click on "OK".

check_text:
  If the need for the SQL Server Browser service is documented and authorized, this is not a finding. 

  Open the Services tool. 

  Either navigate, via the Windows Start Menu and/or Control Panel, to "Administrative Tools", and select "Services"; or at a command prompt, type "services.msc" and press the "Enter" key. 

  Scroll to "SQL Server Browser". 

  If its Startup Type is not shown as "Disabled", this is a finding.


vuln_id: V-214043
rule_id: SV-214043r960963_rule
severity: CAT II
title: SQL Server Replication Xps feature must be disabled, unless specifically required and approved.
cci: CCI-000381
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>SQL Server is capable of providing a wide range of features and services. Some of the features and services, provided by default, may not be necessary, and enabling them could adversely affect the security of the system.

  Enabling the replication XPs opens a significant attack surface area that can be used by an attacker to gather information about the system and potentially abuse the privileges of SQL Server.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized. To disable the use of "Replication Xps" option, from the query prompt: 

  sp_configure 'show advanced options', 1;  
  GO  
  RECONFIGURE;  
  GO  
  sp_configure 'replication xps', 0;  
  GO  
  RECONFIGURE;  
  GO

check_text:
  To determine if the "Replication Xps" option is enabled, execute the following query: 

  EXEC SP_CONFIGURE 'show advanced options', '1'; 
  RECONFIGURE WITH OVERRIDE; 
  EXEC SP_CONFIGURE 'replication xps'; 

  If the value of "config_value" is "0", this is not a finding. 

  If the value of "config_value" is "1", review the system documentation to determine whether the use of "Replication Xps" is required and authorized. If it is not authorized, this is a finding.


vuln_id: V-214044
rule_id: SV-214044r961863_rule
severity: CAT III
cci: CCI-000366
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  If the SQL Server Browser Service is specifically required and approved, SQL instances must be hidden.

description:
  <VulnDiscussion>The SQL Server Browser simplifies the administration of SQL Server, particularly when multiple instances of SQL Server coexist on the same computer. It avoids the need to hard-assign port numbers to the instances and to set and maintain those port numbers in client systems. It enables administrators and authorized users to discover database management system instances, and the databases they support, over the network. SQL Server uses the SQL Server Browser service to enumerate instances of the Database Engine installed on the computer. This enables client applications to browse for a server, and helps clients distinguish between multiple instances of the Database Engine on the same computer.

  This convenience also presents the possibility of unauthorized individuals gaining knowledge of the available SQL Server resources. Therefore, it is necessary to consider whether the SQL Server Browser is needed. Typically, if only a single instance is installed, using the default name (MSSQLSERVER) and port assignment (1433), the Browser is not adding any value. The more complex the installation, the more likely SQL Server Browser is to be helpful. 

  This requirement is not intended to prohibit use of the Browser service in any circumstances.  It calls for administrators and management to consider whether the benefits of its use outweigh the potential negative consequences of it being used by an attacker to browse the current infrastructure and retrieve a list of running SQL Server instances.  In order to prevent this, the SQL instance(s) can be hidden.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  If SQL Server Browser is needed, document the justification and obtain the appropriate authorization. 

  To hide the SQL instance, in SQL Server Configuration Manager, expand SQL Server Network Configuration, right-click Protocols for <server instance>, select "Properties", on the "Flags" tab, select "Yes" in the "HideInstance" box, then click "OK".  The change takes effect immediately for new connections.

check_text:
  If the need for the SQL Server Browser service is documented and authorized, check to make sure the SQL Instances that do not require use of the SQL Browser Service are hidden with the following query: 

  DECLARE @HiddenInstance INT 
  EXEC master.dbo.Xp_instance_regread 
   N'HKEY_LOCAL_MACHINE', 
   N'Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib', 
   N'HideInstance', 
   @HiddenInstance output 

  SELECT CASE 
          WHEN @HiddenInstance = 0 
               AND Serverproperty('IsClustered') = 0 THEN 'No' 
          ELSE 'Yes' 
        END AS [Hidden]

  If the value of "Hidden" is "Yes", this is not a finding.

  If the value of "Hidden" is "No" and the startup type of the "SQL Server Browser" service is not "Disabled", this is a finding.


vuln_id: V-214045
rule_id: SV-214045r961047_rule
severity: CAT I
cci: CCI-000206
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  When using command-line tools such as SQLCMD in a mixed-mode authentication environment, users must use a logon method that does not expose the password.

description:
  <VulnDiscussion>To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism.

  Obfuscation of user-provided information when typed into the system is a method used in addressing this risk.

  For example, displaying asterisks when a user types in a password or PIN, is an example of obscuring feedback of authentication information.

  This requirement is applicable when mixed-mode authentication is enabled.  When this is the case, password-authenticated accounts can be created in and authenticated by SQL Server.  Other STIG requirements prohibit the use of mixed-mode authentication except when justified and approved.  This deals with the exceptions.

  SQLCMD and other command-line tools are part of any SQL Server installation. These tools can accept a plain-text password, but do offer alternative techniques. Since the typical user of these tools is a database administrator, the consequences of password compromise are particularly serious. Therefore, the use of plain-text passwords must be prohibited, as a matter of practice and procedure.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Where possible, change the login mode to Windows-only:
  USE [master]
  GO
  EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'LoginMode', REG_DWORD, 1;
  GO

  If mixed-mode authentication is necessary, then for SQLCMD, which cannot be configured not to accept a plain-text password when mixed-mode authentication is enabled, and any other essential tool with the same limitation:
  1) Document the need for it, who uses it, and any relevant mitigations, and obtain AO approval.
  2) Train all users of the tool in the importance of not using the plain-text password option and in how to keep the password hidden.

check_text:
  Run this query to determine whether SQL Server authentication is enabled:
  EXEC master.sys.xp_loginconfig 'login mode'; 

  If the config_value returned is "Windows NT Authentication", this is not a finding.

  For SQLCMD, which cannot be configured not to accept a plain-text password, and any other essential tool with the same limitation, verify that the system documentation explains the need for the tool, who uses it, and any relevant mitigations; and that AO approval has been obtained; if not, this is a finding.

  Request evidence that all users of the tool are trained in the importance of not using the plain-text password option and in how to keep the password hidden; and that they adhere to this practice; if not, this is a finding.


vuln_id: V-214046
rule_id: SV-214046r961047_rule
severity: CAT I
fix_text: Configure or modify applications to prohibit display of passwords in clear text.
cci: CCI-000206
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
title:
  Applications must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

description:
  <VulnDiscussion>To prevent the compromise of authentication information, such as passwords and PINs, during the authentication process, the feedback from the information system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism.

  Obfuscation of user-provided information when typed into the system is a method used in addressing this risk.

  For example, displaying asterisks when a user types in a password or PIN, is an example of obscuring feedback of authentication information.

  Database applications may allow for entry of the account name and password as a visible parameter of the application execution command. This practice must be prohibited and disabled to prevent shoulder surfing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Determine whether any applications that access the database allow for entry of the account name and password, or PIN.

  If any do, determine whether these applications obfuscate authentication data; if they do not, this is a finding.


vuln_id: V-265870
rule_id: SV-265870r999516_rule
severity: CAT I
title: Microsoft SQL Server products must be a version supported by the vendor.
cci: CCI-003376
created_at: 2026-02-12 15:25:32
updated_at: 2026-02-12 15:25:32
description:
  <VulnDiscussion>Unsupported commercial and database systems should not be used because fixes to newly identified bugs will not be implemented by the vendor. The lack of support can result in potential vulnerabilities.

  Systems at unsupported servicing levels or releases will not receive security updates for new vulnerabilities, which leaves them subject to exploitation.

  When maintenance updates and patches are no longer available, the database software is no longer considered supported and should be upgraded or decommissioned.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Remove or decommission all unsupported software products.

  Upgrade unsupported DBMS or unsupported components to a supported version of the product.

check_text:
  Review the system documentation and interview the database administrator.

  Identify all database software components.

  Review the version and release information.

  Verify the SQL Server version via one of the following methods: 
  Connect to the server by using Object Explorer in SQL Server Management Studio. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of SQL Server.

  Or, from SQL Server Management Studio:

  SELECT @@VERSION;

  More information for finding the version is available at the following link:
  https://learn.microsoft.com/en-us/troubleshoot/sql/releases/find-my-sql-version

  Access the vendor website or use other means to verify the version is still supported.
  https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2016

  If the installed version or any of the software components are not supported by the vendor, this is a finding.


vuln_id: V-278918
rule_id: SV-278918r1135272_rule
severity: CAT II
title: Windows 10 must be configured to audit file system failures.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
  <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Credential validation records events related to validation tests on credentials for a user account logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit File System" with "Failure" selected.

check_text:
  Verify that Audit File System auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit File System. 

  If "Audit File System" is not set to "Failure", this is a finding.


vuln_id: V-278919
rule_id: SV-278919r1135275_rule
severity: CAT II
title: Windows 10 must be configured to audit file system successes.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
  <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Credential validation records events related to validation tests on credentials for a user account logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit File System" with "Success" selected.

check_text:
  Verify that Audit File System auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit File System. 

  If "Audit File System" is not set to "Success", this is a finding.


vuln_id: V-278920
rule_id: SV-278920r1135278_rule
severity: CAT II
title: Windows 10 must be configured to audit handle manipulation failures.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
  <VulnDiscussion>Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Credential validation records events related to validation tests on credentials for a user account logon.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Handle Manipulation" with "Failure" selected.

check_text:
  Verify that Audit Handle Manipulation auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Handle Manipulation. 

  If "Audit Handle Manipulation" is not set to "Failure", this is a finding.


vuln_id: V-278921
rule_id: SV-278921r1135281_rule
severity: CAT II
title: Windows 10 must be configured to audit handle manipulation successes.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
[cell repeats an earlier one in this file: 927 characters]

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Handle Manipulation" with "Success" selected.

check_text:
  Verify that Audit Handle Manipulation auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Handle Manipulation. 

  If "Audit Handle Manipulation" is not set to "Success", this is a finding.


vuln_id: V-278922
rule_id: SV-278922r1135284_rule
severity: CAT II
title: Windows 10 must be configured to audit registry successes.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
[cell repeats an earlier one in this file: 927 characters]

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Registry" with "Success" selected.

check_text:
  Verify that Audit Registry auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Registry. 

  If "Audit Registry" is not set to "Success", this is a finding.


vuln_id: V-278923
rule_id: SV-278923r1135287_rule
severity: CAT II
title: Windows 10 must be configured to audit registry failures.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
[cell repeats an earlier one in this file: 927 characters]

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> "Audit Registry" with "Failure" selected.

check_text:
  Verify that Audit Registry auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Object Access >> Audit Registry. 

  If "Audit Registry" is not set to "Failure", this is a finding.


vuln_id: V-278924
rule_id: SV-278924r1141910_rule
severity: CAT II
title: Windows 10 must be configured to audit sensitive privilege use successes.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
[cell repeats an earlier one in this file: 927 characters]

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use with "Success" selected.

check_text:
  Verify that Audit Sensitive Privilege Use auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use. 

  If "Audit Sensitive Privilege Use" is not set to "Success", this is a finding.


vuln_id: V-278925
rule_id: SV-278925r1141913_rule
severity: CAT II
title: Windows 10 must be configured to audit sensitive privilege use failures.
cci: CCI-000172
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
[cell repeats an earlier one in this file: 927 characters]

fix_text:
  Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use with "Failure" selected.

check_text:
  Verify that Audit Sensitive Privilege Use auditing has been enabled: 

  Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Privilege Use >> Audit Sensitive Privilege Use. 

  If "Audit Sensitive Privilege Use" is not set to "Failure", this is a finding.


vuln_id: V-279687
rule_id: SV-279687r1154974_rule
severity: CAT II
title: Windows 10 systems must block consumer account user authentication.
cci: CCI-000381
created_at: 2026-03-05 13:41:37
updated_at: 2026-03-05 13:41:37
description:
  <VulnDiscussion>It is detrimental for operating systems to provide, or install by default, functionality exceeding requirements or mission objectives. These unnecessary capabilities or services are often overlooked and therefore, may remain unsecured. They increase the risk to the platform by providing additional attack vectors.

  Operating systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).

  The Copilot Rewrite functionality within Notepad and Image Generation within Paint is dependent upon the use of AI credits from a Microsoft 365 Personal or Family subscription. Organizational users must not use personal accounts to login to applications on enterprise machines.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the following Group Policy:
  Computer Configuration >> Administrative Templates >> Windows Components >> Microsoft Account "block all consumer Microsoft account user authentication" to "Enabled".

  For systems managed by Intune, apply the DOD Windows 10 STIG Settings Catalog (or equivalent Intune policy) found in the Intune policy package available on cyber.mil.
  Steps to create an Intune policy:
  1. Sign in to the Intune admin center >> Devices >> Configuration >> Create >> New Policy.
  2. Platform: Windows 10 and later. Profile type: Settings Catalog, then click "Create".
  3. Basics: Provide a Name and Description of the profile, then click "Next".
  4. Configuration settings: Click "+ Add settings" and search for consumer under the Settings picker. Under the Administrative Templates\Windows Components\Microsoft account category, check the box next to "Block all consumer Microsoft account user authentication". Click the "Enabled" radio button, then click "Next".
  5. Scope tags: (optional), then click "Next".
  6. Assignments: Assign the policy to Entra security groups that contain the target users or devices, then click "Next".
  7. Review + create: Review the deployment summary, then click "Create".

check_text:
  Verify the "block all consumer Microsoft account user authentication" is enabled.

  Registry Hive: HKEY_LOCAL_MACHINE
  Registry Path: \SOFTWARE\Policies\Microsoft\MicrosoftAccount

  Value Name: DisableUserAuth

  Value Type: REG_DWORD
  Value: 0x00000001 (1)

  If the registry value is not "1", this is a finding.


vuln_id: V-278355
rule_id: SV-278355r1152352_rule
severity: CAT II
title: Sending of diagnostic data to Microsoft must be disabled.
cci: CCI-000381
created_at: 2026-03-05 14:03:15
updated_at: 2026-03-05 14:14:58
description:
  <VulnDiscussion>Diagnostic data is used to keep Office secure and up to date; detect, diagnose and remediate problems; and make product improvements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Configure the level of client software diagnostic data sent by Office to Microsoft" to "Enabled" and select "Neither" from the Options.

check_text:
  Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Configure the level of client software diagnostic data sent by Office to Microsoft" is set to "Enabled", and "Neither" from the Options is selected.

  Use the Windows Registry Editor to navigate to the following key:
  HKCU\software\policies\Microsoft\office\common\clienttelemetry

  If the value "SendTelemetry" is "REG_DWORD = 3", this is not a finding. 

  If the registry key does not exist or is not configured properly, this is a finding.


vuln_id: V-278356
rule_id: SV-278356r1130624_rule
severity: CAT II
title: Connected experiences that analyze content must be disabled.
cci: CCI-000381
created_at: 2026-03-05 14:03:15
updated_at: 2026-03-05 14:14:58
description:
  <VulnDiscussion>These are experiences that use Office content to provide design recommendations, editing suggestions, data insights, and similar features. Examples include PowerPoint Designer and Translator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of connected experiences in Office that analyze content" to "Disabled".

check_text:
  Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of connected experiences in Office that analyze content" is set to "Disabled".

  Use the Windows Registry Editor to navigate to the following key:
  HKCU\software\policies\Microsoft\office\16.0\common\privacy\

  If the value "UserContentDisabled" is "REG_DWORD = 2", this is not a finding. 

  If the registry key does not exist or is not configured properly, this is a finding.


vuln_id: V-278357
rule_id: SV-278357r1130627_rule
severity: CAT II
title: Connected experiences that download online content must be disabled.
cci: CCI-000381
created_at: 2026-03-05 14:03:15
updated_at: 2026-03-05 14:14:58
description:
  <VulnDiscussion>These are experiences that use Office content to provide design recommendations, editing suggestions, data insights, and similar features. Examples include PowerPoint Designer and Translator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of connected experiences in Office that download online content" to "Disabled".

check_text:
  Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of connected experiences in Office that download online content" is set to "Disabled".

  Use the Windows Registry Editor to navigate to the following key:
  HKCU\software\policies\Microsoft\office\16.0\common\privacy\

  If the value "DownloadContentDisabled" is "REG_DWORD = 2", this is not a finding. 

  If the registry key does not exist or is not configured properly, this is a finding.


vuln_id: V-278358
rule_id: SV-278358r1130630_rule
severity: CAT II
title: Additional optional connected experiences must be disabled.
cci: CCI-000381
created_at: 2026-03-05 14:03:15
updated_at: 2026-03-05 14:14:58
description:
  <VulnDiscussion>These are experiences that use Office content to provide design recommendations, editing suggestions, data insights, and similar features. Examples include PowerPoint Designer and Translator.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of additional optional connected experiences in Office" to "Disabled".

check_text:
  Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of additional optional connected experiences in Office" is set to "Disabled".

  Use the Windows Registry Editor to navigate to the following key:
  HKCU\software\policies\Microsoft\office\16.0\common\privacy\

  If the value "ControllerConnectedServicesEnabled" is "REG_DWORD = 2", this is not a finding. 

  If the registry key does not exist or is not configured properly, this is a finding.


vuln_id: V-278359
rule_id: SV-278359r1130633_rule
severity: CAT II
title: Connected experiences must be disabled.
cci: CCI-000381
created_at: 2026-03-05 14:03:15
updated_at: 2026-03-05 14:14:58
description:
[cell repeats an earlier one in this file: 573 characters]

fix_text:
  Set the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of connected experiences in Office" to "Disabled".

check_text:
  Verify the policy value for User Configuration >> Administrative Templates >> Microsoft Office 2016 >> Privacy >> Trust Center >> "Allow the use of connected experiences in Office" is set to "Disabled".

  Use the Windows Registry Editor to navigate to the following key:
  HKCU\software\policies\Microsoft\office\16.0\common\privacy\

  If the value "DisconnectedState" is "REG_DWORD = 2", this is not a finding. 

  If the registry key does not exist or is not configured properly, this is a finding.


vuln_id: V-206519
rule_id: SV-206519r960735_rule
severity: CAT II
cci: CCI-000054
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must limit the number of concurrent sessions to an organization-defined number per user for all accounts and/or account types.

description:
  <VulnDiscussion>Database management includes the ability to control the number of users and user sessions utilizing a DBMS. Unlimited concurrent connections to the DBMS could allow a successful Denial of Service (DoS) attack by exhausting connection resources; and a system can also fail or be degraded by an overload of legitimate users. Limiting the number of concurrent sessions per user is helpful in reducing these risks.

  This requirement addresses concurrent session control for a single account. It does not address concurrent sessions by a single user via multiple system accounts; and it does not deal with the total number of sessions across all accounts.

  The capability to limit the number of concurrent sessions per user must be configured in or added to the DBMS (for example, by use of a logon trigger), when this is technically feasible. Note that it is not sufficient to limit sessions via a web server or application server alone, because legitimate users and adversaries can potentially connect to the DBMS by other means.

  The organization will need to define the maximum number of concurrent sessions by account type, by account, or a combination thereof. In deciding on the appropriate number, it is important to consider the work requirements of the various types of users. For example, 2 might be an acceptable limit for general users accessing the database via an application; but 10 might be too few for a database administrator using a database management GUI tool, where each query tab and navigation pane may count as a separate session.

  (Sessions may also be referred to as connections or logons, which for the purposes of this requirement are synonyms.)</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  If the DBMS is capable of enforcing this restriction, but is not configured to do so, configure it to do so. (This may involve the development of one or more triggers.)

  If it is not technically feasible for the DBMS to enforce this restriction, and the application(s) and supporting software are not configured to do so, configure them to do so.

  If the value for any type of user account is not set, determine the correct value and set it. 

  If a value is set but is not equal to the value specified for the type of user, determine the correct value, set it, and update the documentation, as appropriate.

check_text:
  Determine whether the system documentation specifies limits on the number of concurrent DBMS sessions per account by type of user. If it does not, assume a limit of 10 for database administrators and 2 for all other users.

  Review the concurrent-sessions settings in the DBMS and/or the applications using it, and/or the system software supporting it. 

  If the DBMS is capable of enforcing this restriction but is not configured to do so, this is a finding. This holds even if the restriction is enforced by applications or supporting software.

  If it is not technically feasible for the DBMS to enforce this restriction, but the application(s) or supporting software are configured to do so, this is not a finding. 

  If it is not technically feasible for the DBMS to enforce this restriction, and applications and supporting software are not so configured, this is a finding.

  If the value for any type of user account is not set, this is a finding.

  If a value is set but is not equal to the value specified in the documentation (or the default value defined in this check) for the type of user, this is a finding.


vuln_id: V-206520
rule_id: SV-206520r1043176_rule
severity: CAT I
cci: CCI-000015
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.

description:
  <VulnDiscussion>Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization.

  A comprehensive application account management process that includes automation helps to ensure that accounts designated as requiring attention are consistently and promptly addressed. 

  Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended, or terminated, or by disabling accounts located in non-centralized account stores, such as multiple servers. Account management functions can also include: assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example: using email or text messaging to notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using automated telephone notification to report atypical system account usage.

  The DBMS must be configured to automatically utilize organization-level account management functions, and these functions must immediately enforce the organization's current account policy. 

  Automation may be comprised of differing technologies that when placed together contain an overall mechanism supporting an organization's automated account management requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Integrate DBMS security with an organization-level authentication/access mechanism providing account management for all users, groups, roles, and any other principals.

  For each DBMS-managed account that is not documented and approved, either transfer it to management by the external mechanism, or document the need for it and obtain approval, as appropriate.

check_text:
  If all accounts are authenticated by the organization-level authentication/access mechanism and not by the DBMS, this is not a finding.

  If there are any accounts managed by the DBMS, review the system documentation for justification and approval of these accounts.

  If any DBMS-managed accounts exist that are not documented and approved, this is a finding.


vuln_id: V-206521
rule_id: SV-206521r1137654_rule
severity: CAT I
cci: CCI-000213
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

description:
  <VulnDiscussion>Authentication with a DOD-approved PKI certificate does not necessarily imply authorization to access the DBMS. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems, including databases, must be properly configured to implement access control policies. 

  Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. 

  Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. 

  This requirement is applicable to access control enforcement applications, a category that includes database management systems. If the DBMS does not follow applicable policy when approving access, it may be in conflict with networks or other applications in the information system. This may result in users either gaining or being denied access inappropriately and in conflict with applicable policy.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS settings and access controls to permit user access only to objects and data that the user is authorized to view or interact with, and to prevent access to all other objects and data.

check_text:
  Check DBMS settings to determine whether users are restricted from accessing objects and data they are not authorized to access.

  If appropriate access controls are not implemented to restrict access to authorized users and to restrict the access of those users to objects and data they are authorized to see, this is a finding.


vuln_id: V-206522
rule_id: SV-206522r960864_rule
severity: CAT II
cci: CCI-000166
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must protect against a user falsely repudiating having performed organization-defined actions.

description:
  <VulnDiscussion>Non-repudiation of actions taken is required in order to maintain data integrity. Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. 

  Non-repudiation protects against later claims by a user of not having created, modified, or deleted a particular data item or collection of data in the database.

  In designing a database, the organization must define the types of data and the user actions that must be protected from repudiation. The implementation must then include building audit features into the application data tables and configuring the DBMS's audit tools to capture the necessary audit trail. Design and implementation also must ensure that applications pass individual user identification to the DBMS, even where the application connects to the DBMS with a standard, shared account.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Use accounts assigned to individual users. Where the application connects to the DBMS using a standard, shared account, ensure that it also captures the individual user identification and passes it to the DBMS.

  Modify application database tables and all supporting code to capture the necessary audit data.

  Modify the configuration of audit logs to include details identifying the individual user.

check_text:
  Review system documentation to determine the data and the actions on data that need to be protected from repudiation by means of audit trails.

  Review DBMS settings to determine whether users can be identified as individuals when using shared accounts. If the individual user who is using a shared account cannot be identified, this is a finding.

  Review the design and the contents of the application data tables. If they do not include the necessary audit data, this is a finding.

  Review the configuration of audit logs to determine whether auditing includes details identifying the individual user. If it does not, this is a finding.


vuln_id: V-206523
rule_id: SV-206523r960879_rule
severity: CAT II
cci: CCI-000169
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must provide audit record generation capability for DoD-defined auditable events within all DBMS/database components.

description:
  <VulnDiscussion>Without the capability to generate audit records, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 

  Audit records can be generated from various components within the DBMS (e.g., process, module). Certain specific application functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records.

  DoD has defined the list of events for which the DBMS will provide an audit record generation capability as the following: 

  (i) Successful and unsuccessful attempts to access, modify, or delete privileges, security objects, security levels, or categories of information (e.g., classification levels);

  (ii) Access actions, such as successful and unsuccessful logon attempts, privileged activities, or other system-level access, starting and ending time for user access to the system, concurrent logons from different workstations, successful and unsuccessful accesses to objects, all program initiations, and all direct access to the information system; and

  (iii) All account creation, modification, disabling, and termination actions.

  Organizations may define additional events requiring continuous or ad hoc auditing.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS that supports the DoD minimum set of auditable events.

  Configure the DBMS to generate audit records for at least the DoD minimum set of events.

check_text:
  Check DBMS auditing to determine whether organization-defined auditable events are being audited by the system.

  If organization-defined auditable events are not being audited, this is a finding.


vuln_id: V-206524
rule_id: SV-206524r960882_rule
severity: CAT II
cci: CCI-000171
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.

description:
  <VulnDiscussion>Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent or interfere with the auditing of critical events.

  Suppression of auditing could permit an adversary to evade detection.

  Misconfigured audits can degrade the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS's settings to allow designated personnel to select which auditable events are audited.

check_text:
  Check DBMS settings and documentation to determine whether designated personnel are able to select which auditable events are being audited.

  If designated personnel are not able to configure auditable events, this is a finding.


vuln_id: V-206525
rule_id: SV-206525r960885_rule
severity: CAT II
title: The DBMS must be able to generate audit records when privileges/permissions are retrieved.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically make such information available through views or functions.

  This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are retrieved.

  If currently required, configure the DBMS to produce audit records when privileges/permissions/role memberships are retrieved.

check_text:
  Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are retrieved.

  If the DBMS is not capable of this, this is a finding.

  If the DBMS is currently required to audit the retrieval of privilege/permission/role membership information, review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are retrieved.

  If they are not produced, this is a finding.


vuln_id: V-206526
rule_id: SV-206526r960885_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.

description:
  <VulnDiscussion>Under some circumstances, it may be useful to monitor who/what is reading privilege/permission/role information. Therefore, it must be possible to configure auditing to do this. DBMSs typically make such information available through views or functions.

  This requirement addresses explicit requests for privilege/permission/role membership information. It does not refer to the implicit retrieval of privileges/permissions/role memberships that the DBMS continually performs to determine if any and every action on the database is permitted.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete access to privileges/permissions/role membership.

  If currently required, configure the DBMS to produce audit records when it denies access to privileges/permissions/role membership.

  Configure the DBMS to produce audit records when other errors prevent access to privileges/permissions/role membership.

check_text:
  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to retrieve privileges/permissions/role membership.

  If the DBMS is not capable of this, this is a finding.

  If the DBMS is currently required to audit the retrieval of privilege/permission/role membership information, review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS denies retrieval of privileges/permissions/role memberships.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent retrieval of privileges/permissions/role memberships.

  If they are not produced, this is a finding.


vuln_id: V-206527
rule_id: SV-206527r960888_rule
severity: CAT II
title: The DBMS must initiate session auditing upon startup.
cci: CCI-001464
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session auditing is in use, it needs to be in operation for the whole time the DBMS is running.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of session auditing.

  Configure the DBMS software or third-party product to enable session auditing.

check_text:
  Review DBMS vendor documentation to determine whether the DBMS software is capable of session auditing.

  If the DBMS is not capable of session auditing and a third party product is not being used for session level auditing, this is a finding.

  If the DBMS is capable of session level auditing and specific session audits are currently defined but session auditing is not enabled; or if a third-party product is available for session auditing and specific session audits are currently defined but session auditing is not enabled, this is a finding.


vuln_id: V-206528
rule_id: SV-206528r960891_rule
severity: CAT II
fix_text: Configure DBMS audit settings to include event type as part of the audit record.
cci: CCI-000130
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must produce audit records containing sufficient information to establish what type of events occurred.

description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 

  Audit record content that may be necessary to satisfy the requirement of this policy includes, for example, time stamps, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked.

  Associating event types with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. 

  Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly what actions were performed. This requires specific information regarding the event type an audit record is referring to. If event type information is not recorded and stored with the audit record, the record itself is of very limited use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Check DBMS settings and existing audit records to verify information specific to the audit event type is being captured and stored with the audit records.

  If audit records exist without information regarding what type of event occurred, this is a finding.


vuln_id: V-206529
rule_id: SV-206529r960894_rule
severity: CAT II
title: The DBMS must produce audit records containing time stamps to establish when the events occurred.
cci: CCI-000131
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Without establishing when events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident.

  In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know the date and time when events occurred.

  Associating the date and time with detected events in the application and audit logs provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application. 

  Database software is capable of a range of actions on data stored within the database. It is important, for accurate forensic analysis, to know exactly when specific actions were performed. This requires the date and time an audit record is referring to. If date and time information is not recorded and stored with the audit record, the record itself is of very limited use.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS audit settings to include the date and time of the occurrence of the event as part of the audit record.

check_text:
  Check DBMS settings and existing audit records to verify information specific to the date and time of the event is being captured and stored with the audit records.

  If audit records exist without the date and time of the event, this is a finding.


vuln_id: V-206530
rule_id: SV-206530r960897_rule
severity: CAT II
fix_text: Configure DBMS audit settings to include where the event occurred as part of the audit record.
cci: CCI-000132
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must produce audit records containing sufficient information to establish where the events occurred.

description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Without establishing where events occurred, it is impossible to establish, correlate, and investigate the events relating to an incident.

  In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. 

  Associating information about where the event occurred within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Check DBMS settings and existing audit records to verify information specific to where the event occurred is being captured and stored with the audit records.

  If audit records exist without information regarding where the event occurred, this is a finding.


vuln_id: V-206531
rule_id: SV-206531r960900_rule
severity: CAT II
fix_text: Configure DBMS audit settings to include the source of the event as part of the audit record.
cci: CCI-000133
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events.

description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events relating to an incident.

  In order to compile an accurate risk assessment and provide forensic analysis, it is essential for security personnel to know where events occurred, such as application components, modules, session identifiers, filenames, host names, and functionality. 

  In addition to logging where events occur within the application, the application must also produce audit records that identify the application itself as the source of the event.

  Associating information about the source of the event within the application provides a means of investigating an attack; recognizing resource utilization or capacity thresholds; or identifying an improperly configured application.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Check DBMS settings and existing audit records to verify information specific to the source (origin) of the event is being captured and stored with audit records.

  If audit records exist without information regarding the source of the event, this is a finding.


vuln_id: V-206532
rule_id: SV-206532r960903_rule
severity: CAT II
fix_text: Configure DBMS audit settings to include the outcome of the event as part of the audit record.
cci: CCI-000134
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events.

description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system.

  Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Check DBMS settings and existing audit records to verify information specific to the outcome of the event is being captured and stored with the audit records.

  If audit records exist without the outcome of the event that occurred, this is a finding.


vuln_id: V-206533
rule_id: SV-206533r960906_rule
severity: CAT II
fix_text: Configure DBMS audit settings to include user name as part of the audit record.
cci: CCI-001487
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event.

description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Without information that establishes the identity of the subjects (i.e., users or processes acting on behalf of users) associated with the events, security personnel cannot determine responsibility for the potentially harmful event.

  Identifiers (if authenticated or otherwise known) include, but are not limited to, user database tables, primary key values, user names, or process identifiers.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Check DBMS settings and existing audit records to verify a user name associated with the event is being captured and stored with the audit records. If audit records exist without specific user information, this is a finding.


vuln_id: V-206534
rule_id: SV-206534r960909_rule
severity: CAT II
cci: CCI-000135
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.

description:
  <VulnDiscussion>Information system auditing capability is critical for accurate forensic analysis. Reconstruction of harmful events or forensic analysis is not possible if audit records do not contain enough information. To support analysis, some types of events will need information to be logged that exceeds the basic requirements of event type, time stamps, location, source, outcome, and user identity. If additional information is not available, it could negatively impact forensic investigations into user actions or other malicious events.

  The organization must determine what additional information is required for complete analysis of the audited events. The additional information required is dependent on the type of information (e.g., sensitivity of the data and the environment within which it resides). At a minimum, the organization must employ either full-text recording of privileged commands or the individual identities of users of shared accounts, or both. The organization must maintain audit trails in sufficient detail to reconstruct events to determine the cause and impact of compromise. 

  Examples of detailed information the organization may require in audit records are full-text recording of privileged commands or the individual identities of shared account users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS audit settings to include all organization-defined detailed information in the audit records for audit events identified by type, location, or subject.

check_text:
  Review the system documentation to identify what additional information the organization has determined to be necessary.

  Check DBMS settings and existing audit records to verify that all organization-defined additional, more detailed information is in the audit records for audit events identified by type, location, or subject.

  If any additional information is defined and is not contained in the audit records, this is a finding.


vuln_id: V-206537
rule_id: SV-206537r960927_rule
severity: CAT II
cci: CCI-000159
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must use system clocks to generate time stamps for use in audit records and application data.

description:
  <VulnDiscussion>Internal system clocks are typically a feature of server hardware and are maintained and used by the operating system. They are typically synchronized with an authoritative time server at regular intervals.

  Without an internal system clock used as the reference for the time stored on each event to provide a trusted common reference for the time, forensic analysis would be impeded. Determining the correct time a particular event occurred on a system is critical when conducting forensic analysis and investigating system events. 

  Time stamps generated by the internal system clock and used by the DBMS shall include both date and time. The time may be expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC.

  If time sources other than the system time are used for audit records, the timeline of events can get skewed. This makes forensic analysis of the logs much less reliable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS that can use time stamp values obtained from or synchronized with the internal system clock used by the operating system.

  Configure the DBMS to use time stamp values obtained from or synchronized with the internal system clock used by the operating system.

check_text:
  Using product documentation, verify that the DBMS uses current time stamp values obtained from or synchronized with the internal system clock used by the operating system. 

  If it is not able to, this is a finding.

  If it is able to but is configured so that it does not do so, this is a finding.


vuln_id: V-206538
rule_id: SV-206538r960930_rule
severity: CAT II
title: The audit information produced by the DBMS must be protected from unauthorized read access.
cci: CCI-000162
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult, if not impossible, to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage.

  To ensure the veracity of audit data, the information system and/or the application must protect audit information from any and all unauthorized access. This includes read, write, copy, etc.

  This requirement can be achieved through multiple methods which will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions utilizing file system protections and limiting log data location. 

  Additionally, applications with user interfaces to audit records should not allow for the unfettered manipulation of or access to those records via the application. If the application provides access to the audit data, the application becomes accountable for ensuring that audit information is protected from unauthorized access.

  Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply controls and modify permissions to protect database audit log data from unauthorized access, whether stored in the database itself or at the OS level.

check_text:
  Review locations of audit logs, both internal to the database and database audit logs located at the operating system level.

  Verify there are appropriate controls and permissions to protect the audit information from unauthorized access.

  If appropriate controls and permissions do not exist, this is a finding.


vuln_id: V-206539
rule_id: SV-206539r960933_rule
severity: CAT II
title: The audit information produced by the DBMS must be protected from unauthorized modification.
cci: CCI-000163
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve. 

  To ensure the veracity of audit data the information system and/or the application must protect audit information from unauthorized modification. 

  This requirement can be achieved through multiple methods that will depend upon system architecture and design. Some commonly employed methods include ensuring log files enjoy the proper file system permissions and limiting log data locations. 

  Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights that the user enjoys in order to make access decisions regarding the modification of audit data.

  Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity. 

  Modification of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply controls and modify permissions to protect database audit log data from unauthorized modification, whether stored in the database itself or at the OS level.

check_text:
  Review locations of audit logs, both internal to the database and database audit logs located at the operating system level.

  Verify there are appropriate controls and permissions to protect the audit information from unauthorized modification.

  If appropriate controls and permissions do not exist, this is a finding.


vuln_id: V-206540
rule_id: SV-206540r960936_rule
severity: CAT II
title: The audit information produced by the DBMS must be protected from unauthorized deletion.
cci: CCI-000164
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is impossible to achieve.

  To ensure the veracity of audit data, the information system and/or the application must protect audit information from unauthorized deletion. This requirement can be achieved through multiple methods which will depend upon system architecture and design.

  Some commonly employed methods include: ensuring log files enjoy the proper file system permissions utilizing file system protections; restricting access; and backing up log data to ensure log data is retained.

  Applications providing a user interface to audit data will leverage user permissions and roles identifying the user accessing the data and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit data.

  Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.

  Deletion of database audit data could mask the theft of, or the unauthorized modification of, sensitive data stored in the database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply controls and modify permissions to protect database audit log data from unauthorized deletion, whether stored in the database itself or at the OS level.

check_text:
  Review locations of audit logs, both internal to the database, and database audit logs located at the operating system level.

  Verify there are appropriate controls and permissions to protect the audit information from unauthorized deletion.

  If appropriate controls and permissions do not exist, this is a finding.


vuln_id: V-206541
rule_id: SV-206541r960939_rule
severity: CAT II
title: The DBMS must protect its audit features from unauthorized access.
cci: CCI-001493
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. 

  Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. It is, therefore, imperative that access to audit tools be controlled and protected from unauthorized access. 

  Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the access to audit tools.

  Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records. 

  If an attacker were to gain access to audit tools, he could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply or modify access controls and permissions (both within the DBMS and in the file system/operating system) to tools used to view or modify audit log data. Tools must be accessible by authorized personnel only.

check_text:
  Review the access permissions to tools used to view or modify audit log data. These tools may include features within the DBMS itself or software external to the database.

  If appropriate permissions and access controls to prevent unauthorized access are not applied to these tools, this is a finding.


vuln_id: V-206542
rule_id: SV-206542r960942_rule
severity: CAT II
title: The DBMS must protect its audit configuration from unauthorized modification.
cci: CCI-001494
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data.

  Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the modification of audit tools.

  Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply or modify access controls and permissions (both within the DBMS and in the file system/operating system) to tools used to view or modify audit log data. Tools must be configurable by authorized personnel only.

check_text:
  Review the access permissions to tools used to view or modify audit log data. These tools may include features within the DBMS itself or software external to the database.

  If appropriate permissions and access controls to prevent unauthorized configuration are not applied to these tools, this is a finding.


vuln_id: V-206543
rule_id: SV-206543r960945_rule
severity: CAT II
title: The DBMS must protect its audit features from unauthorized removal.
cci: CCI-001495
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data.

  Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the deletion of audit tools.

  Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply or modify access controls and permissions (both within the DBMS and in the file system/operating system) to tools used to view or modify audit log data. Ensure that tools may be removed by authorized personnel only.

check_text:
  Review the access permissions to tools used to view or modify audit log data. These tools may include features within the DBMS itself or software external to the database.

  If appropriate permissions and access controls to prevent unauthorized removal are not applied to these tools, this is a finding.


vuln_id: V-206544
rule_id: SV-206544r960960_rule
severity: CAT II
cci: CCI-001499
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to the DBMS.

description:
  <VulnDiscussion>If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.

  Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.

  Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Implement procedures to monitor for unauthorized changes to DBMS software libraries, related software application libraries, and configuration files. If a third-party automated tool is not employed, an automated job that reports file information on the directories and files of interest and compares them to the baseline report for the same will meet the requirement.

  Use file hashes or checksums for comparisons, as file dates may be manipulated by malicious users.

check_text:
  Review monitoring procedures and implementation evidence to verify monitoring of changes to database software libraries, related applications, and configuration files is done.

  Verify the list of files, directories, and database application objects (procedures, functions, and triggers) being monitored is complete.

  If monitoring does not occur or is not complete, this is a finding.


vuln_id: V-206545
rule_id: SV-206545r960960_rule
severity: CAT I
title: The DBMS software installation account must be restricted to authorized users.
cci: CCI-001499
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can have significant effects on the overall security of the system. 

  If the system were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.

  Accordingly, only qualified and authorized individuals shall be allowed access to information system components for purposes of initiating changes, including upgrades and modifications.

  DBA and other privileged administrative or application owner accounts are granted privileges that allow actions that can have a great impact on database security and operation. It is especially important to grant privileged access to only those persons who are qualified and authorized to use them.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Develop, document, and implement procedures to restrict and track use of the DBMS software installation account.

check_text:
  Review procedures for controlling, granting access to, and tracking use of the DBMS software installation account.

  If access or use of this account is not restricted to the minimum number of personnel required or if unauthorized access to the account has been granted, this is a finding.


vuln_id: V-206546
rule_id: SV-206546r960960_rule
severity: CAT II
cci: CCI-001499
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.

description:
  <VulnDiscussion>When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system.

  Multiple applications can provide a cumulative negative effect. A vulnerability and subsequent exploit to one application can lead to an exploit of other applications sharing the same security context. For example, an exploit to a web server process that leads to unauthorized administrative access to host system directories can most likely lead to a compromise of all applications hosted by the same system. Database software not installed using dedicated directories both threatens and is threatened by other hosted applications. Access controls defined for one application may by default provide access to the other application's database objects or directories. Any method that provides any level of separation of security context assists in the protection between applications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Install all applications on directories separate from the DBMS software library directory. Relocate any directories or reinstall other application software that currently shares the DBMS software library directory.

  For mainframe-based databases, locate database software and configuration files in separate DASD pools from other mainframe applications.

check_text:
  Review the DBMS software library directory and note other root directories located on the same disk directory or any subdirectories.

  If any non-DBMS software directories exist on the disk directory, examine or investigate their use. If any of the directories are used by other applications, including third-party applications that use the DBMS, this is a finding.

  Only applications that are required for the functioning and administration, not use, of the DBMS should be located in the same disk directory as the DBMS software libraries.

  If other applications are located in the same directory as the DBMS, this is a finding.

  For databases located on mainframes, confirm that the database and its configuration files are isolated in their own DASD pools.

  If database software and database configuration files share DASD with other applications, this is a finding.


vuln_id: V-206547
rule_id: SV-206547r960960_rule
severity: CAT II
fix_text: Assign ownership of authorized objects to authorized object owner accounts.
cci: CCI-001499
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/DBMS principals authorized for ownership.

description:
  <VulnDiscussion>Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access to the owned objects to other subjects. Database functions and procedures can be coded using definer's rights. This allows anyone who utilizes the object to perform the actions if they were the owner. If not properly managed, this can lead to privileged actions being taken by unauthorized individuals.

  Conversely, if critical tables or other objects rely on unauthorized owner accounts, these objects may be lost when an account is removed.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review system documentation to identify accounts authorized to own database objects. Review accounts that own objects in the database(s).

  If any database objects are found to be owned by users not authorized to own database objects, this is a finding.


vuln_id: V-206548
rule_id: SV-206548r960960_rule
severity: CAT II
fix_text: Revoke unauthorized memberships in the DBMS modification group(s)/role(s).
cci: CCI-001499
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  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 the DBMS, etc.) must be restricted to authorized users.

description:
  <VulnDiscussion>If the DBMS were to allow any user to make changes to database structure or logic, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.

  Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.

  Unmanaged changes that occur to the database software libraries or configuration can lead to unauthorized or compromised installations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Identify the group(s)/role(s) established for DBMS modification.

  Obtain the list of users in those group(s)/roles.

  Identify the individuals authorized to modify the DBMS.

  If unauthorized access to the group(s)/role(s) has been granted, this is a finding.


vuln_id: V-206549
rule_id: SV-206549r960963_rule
severity: CAT II
title: Default demonstration and sample databases, database objects, and applications must be removed.
cci: CCI-000381
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).

  It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. Examples include, but are not limited to, installing advertising software, demonstrations, or browser plugins not related to requirements or providing a wide array of functionality, not required for every mission, that cannot be disabled.

  DBMSs must adhere to the principles of least functionality by providing only essential capabilities.

  Demonstration and sample database objects and applications present publicly known attack points for malicious users. These demonstration and sample objects are meant to provide simple examples of coding specific functions and are not developed to prevent vulnerabilities from being introduced to the DBMS and host system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Remove any demonstration and sample databases, database applications, objects, and files from the DBMS.

check_text:
  Review vendor documentation and vendor websites to identify vendor-provided demonstration or sample databases, database applications, objects, and files. 

  Review the DBMS to determine if any of the demonstration and sample databases, database applications, or files are installed in the database or are included with the DBMS application.

  If any are present in the database or are included with the DBMS application, this is a finding.


vuln_id: V-206550
rule_id: SV-206550r960963_rule
severity: CAT II
title: Unused database components, DBMS software, and database objects must be removed.
cci: CCI-000381
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions).

  It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. 

  DBMSs must adhere to the principles of least functionality by providing only essential capabilities.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Uninstall unused components or features that are installed and can be uninstalled. Remove any database objects and applications that are installed to support them.

check_text:
  Review the list of components and features installed with the database.

  Use the DBMS product installation tool if supported and review the product installation documentation.

  If unused components or features are installed and are not documented and authorized, this is a finding.


vuln_id: V-206551
rule_id: SV-206551r960963_rule
severity: CAT II
fix_text: Disable any unused components or features that cannot be uninstalled.
cci: CCI-000381
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.

description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for software products to provide, or install by default, functionality exceeding requirements or mission objectives. 

  DBMSs must adhere to the principles of least functionality by providing only essential capabilities.

  Unused, unnecessary DBMS components increase the attack vector for the DBMS by introducing additional targets for attack. By minimizing the services and applications installed on the system, the number of potential vulnerabilities is reduced. Components of the system that are unused and cannot be uninstalled must be disabled. The techniques available for disabling components will vary by DBMS product, OS, and the nature of the component and may include DBMS configuration settings, OS service settings, OS file access security, and DBMS user/role permissions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review the DBMS for unused components of the system that cannot be uninstalled.

  If unused components or features are present on the system, can be disabled, and are not disabled, this is a finding.


vuln_id: V-206552
rule_id: SV-206552r960963_rule
severity: CAT II
title: Access to external executables must be disabled or restricted.
cci: CCI-000381
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). 

  It is detrimental for applications to provide, or install by default, functionality exceeding requirements or mission objectives. 

  Applications must adhere to the principles of least functionality by providing only essential capabilities.

  DBMSs may spawn additional external processes to execute procedures that are defined in the DBMS but stored in external host files (external procedures). The spawned process used to execute the external procedure may operate within a different OS security context than the DBMS and provide unauthorized access to the host system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Disable use of or remove any external application executable object definitions that are not authorized.

check_text:
  Review the database for definitions of application executable objects stored external to the database.

  Determine if there are methods to disable use or access, or to remove definitions for external executable objects.

  Verify each application executable object listed is authorized by the ISSO. If any are not, this is a finding.


vuln_id: V-206553
rule_id: SV-206553r1043177_rule
severity: CAT II
fix_text: Disable functions, ports, protocols, and services that are not approved.
cci: CCI-000382
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

description:
  <VulnDiscussion>In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols/services on information systems.

  Applications are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. 

  To support the requirements and principles of least functionality, the application must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues.

  Database Management Systems using ports, protocols, and services deemed unsafe are open to attack through those ports, protocols, and services. This can allow unauthorized access to the database and through the database to other components of the information system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review the DBMS settings and local documentation for functions, ports, protocols, and services that are not approved. If any are found, this is a finding.


vuln_id: V-206554
rule_id: SV-206554r1051115_rule
severity: CAT II
cci: CCI-000764
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

description:
  <VulnDiscussion>To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. 

  Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following:

  (i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and 
  (ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals using shared accounts, for detailed accountability of individual activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings to uniquely identify and authenticate all organizational users who log on/connect to the system.

check_text:
  Review DBMS settings to determine whether organizational users are uniquely identified and authenticated when logging on/connecting to the system.

  If organizational users are not uniquely identified and authenticated, this is a finding.


vuln_id: V-206555
rule_id: SV-206555r981946_rule
severity: CAT I
cci: CCI-004066
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  If DBMS authentication, using passwords, is employed, the DBMS must enforce the DOD standards for password complexity and lifetime.

description:
  <VulnDiscussion>OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be used only when circumstances make it unavoidable; and must be documented and AO-approved.

  The DOD standard for authentication is DOD-approved PKI certificates. Authentication based on user ID and password may be used only when it is not possible to employ a PKI certificate, and requires AO approval.

  In such cases, the DOD standards for password complexity and lifetime must be implemented. DBMS products that can inherit the rules for these from the operating system or access control program (e.g., Microsoft Active Directory) must be configured to do so. For other DBMSs, the rules must be enforced using available configuration parameters or custom code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  If the use of passwords is not needed, configure the DBMS to prevent their use if it is capable of this; if it is not, institute policies and procedures to prohibit their use.

  If the DBMS can inherit password complexity rules from the operating system or access control program, configure it to do so.

  Otherwise, use DBMS configuration parameters and/or custom code to enforce the following rules for passwords:
  a. Minimum of 15 characters, including at least one of each of the following character sets:
  - Uppercase.
  - Lowercase.
  - Numerics.
  - Special characters (e.g., ~ ! @ # $ % ^ & * ( ) _ + = - ' [ ] / ? > <).
  b. Minimum number of characters changed from previous password: 50 percent of the minimum password length; that is, eight.
  c. Password lifetime limits for interactive accounts: Minimum 24 hours, maximum 60 days.
  d. Password lifetime limits for non-interactive accounts: Minimum 24 hours, maximum 365 days.
  e. Number of password changes before an old one may be reused: Minimum of five.

check_text:
  If DBMS authentication, using passwords, is not employed, this is not a finding.

  If the DBMS is configured to inherit password complexity and lifetime rules from the operating system or access control program, this is not a finding.

  Review the DBMS settings relating to password complexity. Determine whether the following rules are enforced. If any are not, this is a finding.
  a. minimum of 15 characters, including at least one of each of the following character sets:
  - Uppercase.
  - Lowercase.
  - Numerics.
  - Special characters (e.g., ~ ! @ # $ % ^ & * ( ) _ + = - ' [ ] / ? > <).
  b. Minimum number of characters changed from previous password: 50 percent of the minimum password length; that is, eight.

  Review the DBMS settings relating to password lifetime. Determine whether the following rules are enforced. If any are not, this is a finding.
  a. Password lifetime limits for interactive accounts: Minimum 24 hours, maximum 60 days.
  b. Password lifetime limits for noninteractive accounts: Minimum 24 hours, maximum 365 days.
  c. Number of password changes before an old one may be reused: Minimum of five.


vuln_id: V-206556
rule_id: SV-206556r981949_rule
severity: CAT I
cci: CCI-004062
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash.

description:
  <VulnDiscussion>The DOD standard for authentication is DOD-approved PKI certificates.

  Authentication based on user ID and password may be used only when it is not possible to employ a PKI certificate, and requires AO approval.

  In such cases, database passwords stored in clear text, using reversible encryption, or using unsalted hashes would be vulnerable to unauthorized disclosure. Database passwords must always be in the form of one-way, salted hashes when stored internally or externally to the DBMS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Develop, document, and maintain a list of DBMS database objects, database configuration files, associated scripts, applications defined within or external to the DBMS that access the database, and DBMS/user environment files/settings in the System Security Plan.

  Record whether they do or do not contain DBMS passwords. If passwords are present, ensure they are correctly hashed using one-way, salted hashing functions, and that the hashes are protected by host system security.

check_text:
  Review the list of DBMS database objects, database configuration files, associated scripts, and applications defined within and external to the DBMS that access the database. The list should also include files or settings used to configure the operational environment for the DBMS and for interactive DBMS user accounts.

  Determine whether any DBMS database objects, database configuration files, associated scripts, applications defined within or external to the DBMS that access the database, and DBMS/user environment files/settings contain database passwords. If any do, confirm that DBMS passwords stored internally or externally to the DBMS are hashed using FIPS-approved cryptographic algorithms and include a salt. If any passwords are stored in clear text, this is a finding. If any passwords are stored with reversible encryption, this is a finding.  If any passwords are stored using unsalted hashes, this is a finding.


vuln_id: V-206557
rule_id: SV-206557r961029_rule
severity: CAT I
cci: CCI-000197
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  If passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.

description:
  <VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates.

  Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval.

  In such cases, passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission.

  DBMS passwords sent in clear text format across the network are vulnerable to discovery by unauthorized users. Disclosure of passwords may easily lead to unauthorized access to the database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure encryption for transmission of passwords across the network. If the database does not provide encryption for logon events natively, employ encryption at the OS or network level.

  Ensure passwords remain encrypted from source to destination.

check_text:
  Review configuration settings for encrypting passwords in transit across the network. If passwords are not encrypted, this is a finding. 

  If it is determined that passwords are passed unencrypted at any point along the transmission path between the source and destination, this is a finding.


vuln_id: V-206558
rule_id: SV-206558r961038_rule
severity: CAT II
cci: CCI-000185
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

description:
  <VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates.

  A certificate’s certification path is the path from the end entity certificate to a trusted root certification authority (CA).  Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate.  Certification path validation includes checks such as certificate issuer trust, time validity and revocation status for each certificate in the certification path.  Revocation status information for CA and subject certificates in a certification path is commonly provided via certificate revocation lists (CRLs) or online certificate status protocol (OCSP) responses.

  Database Management Systems that do not validate certificates by performing RFC 5280-compliant certification path validation are in danger of accepting certificates that are invalid and/or counterfeit. This could allow unauthorized access to the database.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to validate certificates by performing RFC 5280-compliant certification path validation.

check_text:
  Review DBMS configuration to verify that certificates being accepted by the DBMS are validated by performing RFC 5280-compliant certification path validation.

  If certificates are not being validated by performing RFC 5280-compliant certification path validation, this is a finding.


vuln_id: V-206559
rule_id: SV-206559r961041_rule
severity: CAT I
title: The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.
cci: CCI-000186
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by requiring the certificate holder to cryptographically prove possession of the corresponding private key.

  If the private key is stolen, an attacker can use the private key(s) to impersonate the certificate holder. In cases where the DBMS-stored private keys are used to authenticate the DBMS to the system’s clients, loss of the corresponding private keys would allow an attacker to successfully perform undetected man in the middle attacks against the DBMS system and its clients.

  Both the holder of a digital certificate and the issuing authority must take careful measures to protect the corresponding private key. Private keys should always be generated and protected in FIPS 140-2 or 140-3 validated cryptographic modules.

  All access to the private key(s) of the DBMS must be restricted to authorized and authenticated users. If unauthorized users have access to one or more of the DBMS's private keys, an attacker could gain access to the key(s) and use them to impersonate the database on the network or otherwise perform unauthorized actions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Store all DBMS PKI private keys in a FIPS 140-2 or 140-3 validated cryptographic module. Ensure access to the DBMS PKI private keys is restricted to only authenticated and authorized users.

check_text:
  Review DBMS configuration to determine whether appropriate access controls exist to protect the DBMS's private key(s). If the DMBS’s private key(s) are not stored in a FIPS 140-2 or 140-3 validated cryptographic module, this is a finding.

  If access to the DBMS’s private key(s) is not restricted to authenticated and authorized users, this is a finding.


vuln_id: V-206560
rule_id: SV-206560r961044_rule
severity: CAT II
title: The DBMS must map the PKI-authenticated identity to an associated user account.
fix_text: Configure the DBMS to map the authenticated identity directly to the DBMS user account.
cci: CCI-000187
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be mapped to a DBMS user account for the authenticated identity to be meaningful to the DBMS and useful for authorization decisions.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review DBMS configuration to verify DBMS user accounts are being mapped directly to unique identifying information within the validated PKI certificate.

  If user accounts are not being mapped to authenticated identities, this is a finding.


vuln_id: V-206561
rule_id: SV-206561r961047_rule
severity: CAT I
cci: CCI-000206
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

description:
  <VulnDiscussion>The DoD standard for authentication is DoD-approved PKI certificates.

  Normally, with PKI authentication, the interaction with the user for authentication will be handled by a software component separate from the DBMS, such as ActivIdentity ActivClient. However, in cases where the DBMS controls the interaction, this requirement applies.

  To prevent the compromise of authentication information such as passwords and PINs during the authentication process, the feedback from the system must not provide any information that would allow an unauthorized user to compromise the authentication mechanism. 

  Obfuscation of user-provided authentication secrets when typed into the system is a method used in addressing this risk. 

  Displaying asterisks when a user types in a password or a smart card PIN is an example of obscuring feedback of authentication secrets.

  This calls for review of applications, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify and configure each non-compliant application, tool, or feature associated with the DBMS/database so that it does not display authentication secrets.

check_text:
  If all interaction with the user for purposes of authentication is handled by a software component separate from the DBMS, this is not a finding.

  If any application, tool or feature associated with the DBMS/database displays any authentication secrets (to include PINs and passwords) during - or after - the authentication process, this is a finding.


vuln_id: V-206562
rule_id: SV-206562r961050_rule
severity: CAT I
fix_text: Utilize NIST FIPS 140-2 or 140-3 validated cryptographic modules for all cryptographic operations.
cci: CCI-000803
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.

description:
  <VulnDiscussion>Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality, or integrity. Weak cryptography could allow an attacker to gain access to and modify data stored in the database as well as the administration settings of the DBMS.

  Applications (including DBMSs) utilizing cryptography are required to use approved NIST FIPS 140-2 or 140-3 validated cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. 

  NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules.

  The standard for validating cryptographic modules will transition to the NIST FIPS 140-3 publication.

  FIPS 140-2 modules can remain active for up to five years after validation or until September 21, 2026, when the FIPS 140-2 validations will be moved to the historical list. Even on the historical list, CMVP supports the purchase and use of these modules for existing systems. While Federal Agencies decide when they move to FIPS 140-3 only modules, purchasers are reminded that for several years there may be a limited selection of FIPS 140-3 modules from which to choose. CMVP recommends purchasers consider all modules that appear on the Validated Modules Search Page:
  https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules

  More information on the FIPS 140-3 transition can be found here: 
  https://csrc.nist.gov/Projects/fips-140-3-transition-effort/</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review DBMS configuration to verify it is using NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.

  If NIST FIPS 140-2 or 140-3 validated modules are not being used for all cryptographic operations, this is a finding.


vuln_id: V-206563
rule_id: SV-206563r961053_rule
severity: CAT II
cci: CCI-000804
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

description:
  <VulnDiscussion>Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations). 

  Non-organizational users shall be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server. 

  Accordingly, a risk assessment is used in determining the authentication needs of the organization. 

  Scalability, practicality, and security are simultaneously considered in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings to uniquely identify and authenticate all non-organizational users who log onto the system.

check_text:
  Review DBMS settings to determine whether non-organizational users are uniquely identified and authenticated when logging onto the system.

  If non-organizational users are not uniquely identified and authenticated, this is a finding.


vuln_id: V-206564
rule_id: SV-206564r1137655_rule
severity: CAT II
fix_text: Configure DBMS to separate database administration and general user functionality.
cci: CCI-001082
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must separate user functionality (including user interface services) from database management functionality.

description:
  <VulnDiscussion>Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. 

  The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. 

  An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. 

  This may include isolating the administrative interface on a different domain and with additional access controls.

  If administrative functionality or information regarding DBMS management is presented on an interface available for users, information on DBMS settings may be inadvertently made available to the user.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Check DBMS settings and vendor documentation to verify that administrative functionality is separate from user functionality.

  If administrator and general user functionality are not separated either physically or logically, this is a finding.


vuln_id: V-206565
rule_id: SV-206565r1043179_rule
severity: CAT II
title: The DBMS must invalidate session identifiers upon user logout or other session termination.
cci: CCI-001185
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and continue to employ previously valid session IDs.

  This requirement focuses on communications protection for the DBMS session rather than for the network packet. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. 

  Session IDs are tokens generated by DBMSs to uniquely identify a user's (or process's) session. DBMSs will make access decisions and execute logic based on the session ID.

  Unique session IDs help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. 

  When a user logs out, or when any other session termination event occurs, the DBMS must terminate the user session(s) to minimize the potential for sessions to be hijacked.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings to terminate sessions, invalidating their session identifiers, upon user logout.

  Configure DBMS settings to terminate sessions, invalidating their session identifiers, upon the occurrence of any organization- or policy-defined session termination event.

check_text:
  Review DBMS settings and vendor documentation to verify user sessions are terminated, and session identifiers invalidated, upon user logout. If they are not, this is a finding.

  Review system documentation and organization policy to identify other events that should result in session terminations.

  If other session termination events are defined, review DBMS settings to verify occurrences of these events would cause session termination, invalidating the session identifiers.

  If occurrences of defined session terminating events do not cause session terminations, invalidating the session identifiers, this is a finding.


vuln_id: V-206566
rule_id: SV-206566r1043180_rule
severity: CAT II
title: The DBMS must recognize only system-generated session identifiers.
fix_text: Utilize a DBMS product that only recognizes session identifiers that are system-generated.
cci: CCI-001664
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>DBMSs utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the session identifier or can inject or manually insert session information, the session may be compromised.

  This requirement focuses on communications protection for the DBMS session rather than for the network packet. The intent of this control is to establish grounds for confidence at each end of a communications session in the ongoing identity of the other party and in the validity of the information being transmitted. 

  The DBMS must recognize only system-generated session identifiers. If an attacker were able to generate a session with a non-system-generated session identifier and have it recognized by the system, the attacker could gain access to the system without passing through access controls designed to limit database sessions to authorized users.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review DBMS settings and vendor documentation to determine whether the DBMS recognizes session identifiers that are not system-generated.

  If the DBMS recognizes session identifiers that are not system generated, this is a finding.


vuln_id: V-206567
rule_id: SV-206567r1043181_rule
severity: CAT II
cci: CCI-001188
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

description:
  <VulnDiscussion>One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known.

  The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 or 140-3 approved random number generator.

  However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Utilize a DBMS product that can provide demonstrably effective protection against man-in-the-middle attacks that guess at session identifier values.

  Configure DBMS settings to enable protections against man-in-the-middle attacks that guess at session identifier values.

check_text:
  Review DBMS vendor documentation and system behavior (and if necessary, consult vendor representatives) to determine whether the DBMS can provide demonstrably effective protection against man-in-the-middle attacks that guess at session identifier values.

  If not, this is a finding.

  Review DBMS settings to determine whether protections against man-in-the-middle attacks that guess at session identifier values are enabled.

  If they are not, this is a finding.


vuln_id: V-206568
rule_id: SV-206568r961122_rule
severity: CAT II
cci: CCI-001190
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

description:
  <VulnDiscussion>Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. 

  Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. 

  Failure to a known safe state helps prevent systems from failing to a state that may cause loss of data or unauthorized access to system resources. Systems that fail suddenly and with no incorporated failure state planning may leave the hosting system available but with a reduced security protection capability. Preserving information system state data also facilitates system restart and return to the operational mode of the organization with less disruption of mission/business processes. 

  Databases must fail to a known consistent state. Transactions must be successfully completed or rolled back.

  In general, security mechanisms should be designed so that a failure will follow the same execution path as disallowing the operation. For example, application security methods, such as isAuthorized(), isAuthenticated(), and validate(), should all return false if there is an exception during processing. If security controls can throw exceptions, they must be very clear about exactly what that condition means. 

  Abort refers to stopping a program or function before it has finished naturally. The term abort refers to both requested and unexpected terminations.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings so that, in the event of a system failure, the DBMS will roll back open transactions to a consistent state, to include a security configuration that is at least as restrictive as before the system failure.

check_text:
  Check DBMS settings and vendor documentation to verify the DBMS properly handles transactions in the event of a system failure.

  If open transactions are not rolled back to a consistent state during system failure, this is a finding.

  The consistent state must include a security configuration that is at least as restrictive as before the system failure. If this is not guaranteed, this is a finding.


vuln_id: V-206569
rule_id: SV-206569r961125_rule
severity: CAT II
cci: CCI-001665
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  In the event of a system failure, the DBMS must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

description:
  <VulnDiscussion>Failure to a known state can address safety or security in accordance with the mission/business needs of the organization.

  Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. 

  Preserving information system state information helps to facilitate system restart and return to the operational mode of the organization with less disruption of mission/business processes. 

  Since it is usually not possible to test this capability in a production environment, systems should either be validated in a testing environment or prior to installation. This requirement is usually a function of the design of the IDPS component. Compliance can be verified by acceptance/validation processes or vendor attestation.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings to preserve any organization-defined system state information in the event of a system failure.

check_text:
  Check DBMS settings to determine whether organization-defined system state information is being preserved in the event of a system failure.

  If organization-defined system state information is not being preserved, this is a finding.


vuln_id: V-206570
rule_id: SV-206570r961128_rule
severity: CAT I
title: The DBMS must protect the confidentiality and integrity of all information at rest.
cci: CCI-001199
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>This control is intended to address the confidentiality and integrity of information at rest in non-mobile devices and covers user information and system information. Information at rest refers to the state of information when it is located on a secondary storage device (e.g., disk drive, tape drive) within an organizational information system. Applications and application users generate information throughout the course of their application use. 

  User data generated, as well as application-specific configuration data, needs to be protected. Organizations may choose to employ different mechanisms to achieve confidentiality and integrity protections, as appropriate. 

  If the confidentiality and integrity of application data is not protected, the data will be open to compromise and unauthorized modification.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Apply appropriate controls to protect the confidentiality and integrity of data at rest in the database.

check_text:
  If the application owner and Authorizing Official have determined that encryption of data at rest is NOT required, this is not a finding.

  Review DBMS settings to determine whether controls exist to protect the confidentiality and integrity of data at rest in the database.

  If controls do not exist or are not enabled, this is a finding.


vuln_id: V-206571
rule_id: SV-206571r961131_rule
severity: CAT II
title: The DBMS must isolate security functions from non-security functions.
cci: CCI-001084
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>An isolation boundary provides access control and protects the integrity of the hardware, software, and firmware that perform security functions. 

  Security functions are the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based.

  Developers and implementers can increase the assurance in security functions by employing well-defined security policy models; structured, disciplined, and rigorous hardware and software development techniques; and sound system/security engineering principles. 

  Database Management Systems typically separate security functionality from non-security functionality via separate databases or schemas. Database objects or code implementing security functionality should not be commingled with objects or code implementing application logic. When security and non-security functionality are commingled, users who have access to non-security functionality may be able to access security functionality.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Locate security-related database objects and code in a separate database, schema, or other separate security domain from database objects and code implementing application logic.

check_text:
  Check DBMS settings to determine whether objects or code implementing security functionality are located in a separate security domain, such as a separate database or schema created specifically for security functionality.

  If security-related database objects or code are not kept separate, this is a finding.


vuln_id: V-206572
rule_id: SV-206572r1137656_rule
severity: CAT II
cci: CCI-001090
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.

description:
  <VulnDiscussion>Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. 

  Data used for the development and testing of applications often involves copying data from production. It is important that specific procedures exist for this process, to include the conditions under which such transfer may take place, where the copies may reside, and the rules for ensuring sensitive data are not exposed.

  Copies of sensitive data must not be misplaced or left in a temporary location without the proper controls.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify any code used for moving data from production to development/test systems to comply with the organization-defined data transfer policy, and to ensure copies of production data are not left in unsecured locations.

check_text:
  Review the procedures for the refreshing of development/test data from production.

  Review any scripts or code that exists for the movement of production data to development/test systems, or to any other location or for any other purpose.

  Verify that copies of production data are not left in unprotected locations. 

  If the code that exists for data movement does not comply with the organization-defined data transfer policy and/or fails to remove any copies of production data from unprotected locations, this is a finding.


vuln_id: V-206573
rule_id: SV-206573r1137657_rule
severity: CAT II
title: The DBMS must prevent unauthorized and unintended information transfer via shared system resources.
cci: CCI-001090
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>The purpose of this control is to prevent information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after the resource has been released back to the information system. Control of information in shared resources is also referred to as object reuse.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of effectively protecting the private resources of one process or user from unauthorized access by another user or process.

  Configure the DBMS to effectively protect the private resources of one process or user from unauthorized access by another user or process.

check_text:
  Review the DBMS architecture to find out if and how it protects the private resources of one process or user (such as working memory, temporary tables, uncommitted data) from unauthorized access by another user or process.

  If it does not effectively do so, this is a finding.


vuln_id: V-206574
rule_id: SV-206574r1137658_rule
severity: CAT II
cci: CCI-001090
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Access to database files must be limited to relevant processes and to authorized, administrative users.

description:
  <VulnDiscussion>Applications, including DBMSs, must prevent unauthorized and unintended information transfer via shared system resources. Permitting only DBMS processes and authorized, administrative users to have access to the files where the database resides helps ensure that those files are not shared inappropriately and are not open to backdoor access and manipulation.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the permissions granted by the operating system/file system on the database files, database log files, and database backup files so that only relevant system accounts and authorized system administrators and database administrators with a need to know are permitted to read/view these files.

check_text:
  Review the permissions granted to users by the operating system/file system on the database files, database log files and database backup files. 

  If any user/role who is not an authorized system administrator with a need to know or database administrator with a need to know, or a system account for running DBMS processes, is permitted to read/view any of these files, this is a finding.


vuln_id: V-206575
rule_id: SV-206575r961158_rule
severity: CAT II
cci: CCI-001310
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must check the validity of all data inputs except those specifically identified by the organization.

description:
  <VulnDiscussion>Invalid user input occurs when a user inserts data or characters into an application's data entry fields and the application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application or information system compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application.

  With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database.

  Even when no such hijacking takes place, invalid input that gets recorded in the database, whether accidental or malicious, reduces the reliability and usability of the system. Available protections include data types, referential constraints, uniqueness constraints, range checking, and application-specific logic. Application-specific logic can be implemented within the database in stored procedures and triggers, where appropriate.

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify database code to properly validate data before it is put into the database or acted upon by the database.

  Modify the database to contain column/field definitions for each column/field in the database.

  Modify the database to contain constraints and validity checking on database columns and tables that require them for data integrity.

check_text:
  Review DBMS code (stored procedures, functions, and triggers), application code, settings, column and field definitions, and constraints to determine whether the database is protected against invalid input.

  If code exists that allows invalid data to be acted upon or input into the database, this is a finding.

  If column/field definitions do not exist in the database, this is a finding.

  If columns/fields do not contain constraints and validity checking where required, this is a finding.

  Where a column/field is noted in the system documentation as necessarily free-form, even though its name and context suggest that it should be strongly typed and constrained, the absence of these protections is not a finding.

  Where a column/field is clearly identified by name, caption or context as Notes, Comments, Description, Text, etc., the absence of these protections is not a finding.


vuln_id: V-206576
rule_id: SV-206576r961158_rule
severity: CAT II
cci: CCI-001310
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS and associated applications must reserve the use of dynamic code execution for situations that require it.

description:
  <VulnDiscussion>With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database.

  The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers).

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Where dynamic code execution is employed in circumstances where the objective could practically be satisfied by static execution with strongly typed parameters, modify the code to do so.

check_text:
  Review DBMS source code (stored procedures, functions, triggers) and application source code, to identify cases of dynamic code execution.

  If dynamic code execution is employed in circumstances where the objective could practically be satisfied by static execution with strongly typed parameters, this is a finding.


vuln_id: V-206577
rule_id: SV-206577r961158_rule
severity: CAT II
cci: CCI-001310
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  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.

description:
  <VulnDiscussion>With respect to database management systems, one class of threat is known as SQL Injection, or more generally, code injection. It takes advantage of the dynamic execution capabilities of various programming languages, including dialects of SQL. In such cases, the attacker deduces the manner in which SQL statements are being processed, either from inside knowledge or by observing system behavior in response to invalid inputs. When the attacker identifies scenarios where SQL queries are being assembled by application code (which may be within the database or separate from it) and executed dynamically, the attacker is then able to craft input strings that subvert the intent of the query. Potentially, the attacker can gain unauthorized access to data, including security settings, and severely corrupt or destroy the database.

  The principal protection against code injection is not to use dynamic execution except where it provides necessary functionality that cannot be utilized otherwise. Use strongly typed data items rather than general-purpose strings as input parameters to task-specific, pre-compiled stored procedures and functions (and triggers).

  When dynamic execution is necessary, ways to mitigate the risk include the following, which should be implemented both in the on-screen application and at the database level, in the stored procedures:
  -- Allow strings as input only when necessary. 
  -- Rely on data typing to validate numbers, dates, etc. Do not accept invalid values. If substituting other values for them, think carefully about whether this could be subverted.
  -- Limit the size of input strings to what is truly necessary.
  -- If single quotes/apostrophes, double quotes, semicolons, equals signs, angle brackets, or square brackets will never be valid as input, reject them.
  -- If comment markers will never be valid as input, reject them. In SQL, these are -- or /* */ 
  -- If HTML and XML tags, entities, comments, etc., will never be valid, reject them.
  -- If wildcards are present, reject them unless truly necessary. In SQL these are the underscore and the percentage sign, and the word ESCAPE is also a clue that wildcards are in use.
  -- If SQL key words, such as SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, ESCAPE, UNION, GRANT, REVOKE, DENY, MODIFY will never be valid, reject them. Use case-insensitive comparisons when searching for these. Bear in mind that some of these words, particularly Grant (as a person's name), could also be valid input. 
  -- If there are range limits on the values that may be entered, enforce those limits.
  -- Institute procedures for inspection of programs for correct use of dynamic coding, by a party other than the developer.
  -- Conduct rigorous testing of program modules that use dynamic coding, searching for ways to subvert the intended use.
  -- Record the inspection and testing in the system documentation.
  -- Bear in mind that all this applies not only to screen input, but also to the values in an incoming message to a web service or to a stored procedure called by a software component that has not itself been hardened in these ways. Not only can the caller be subject to such vulnerabilities; it may itself be the attacker.

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Where dynamic code execution is used, modify the code to implement protections against code injection.

check_text:
  Review DBMS source code (stored procedures, functions, triggers) and application source code to identify cases of dynamic code execution.

  If dynamic code execution is employed without protective measures against code injection, this is a finding.


vuln_id: V-206578
rule_id: SV-206578r961167_rule
severity: CAT II
cci: CCI-001312
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.

description:
  <VulnDiscussion>Any DBMS or associated application providing too much information in error messages on the screen or printout risks compromising the data and security of the system. The structure and content of error messages need to be carefully considered by the organization and development team.

  Databases can inadvertently provide a wealth of information to an attacker through improperly handled error messages. In addition to sensitive business or personal information, database errors can provide host names, IP addresses, user names, and other system information not required for troubleshooting but very useful to someone targeting the system.

  Carefully consider the structure/content of error messages. The extent to which information systems are able to identify and handle error conditions is guided by organizational policy and operational requirements. Information that could be exploited by adversaries includes, for example, logon attempts with passwords entered by mistake as the username, mission/business information that can be derived from (if not stated explicitly by) information recorded, and personal information, such as account numbers, social security numbers, and credit card numbers.

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings, custom database code, and associated application code not to divulge sensitive information or information useful for system identification in error messages.

check_text:
  Check DBMS settings and custom database code to verify that error messages do not contain information beyond what is needed for troubleshooting the issue.

  If database errors contain PII data, sensitive business data, or information useful for identifying the host system or database structure, this is a finding.


vuln_id: V-206579
rule_id: SV-206579r961170_rule
severity: CAT II
title: The DBMS must reveal detailed error messages only to the ISSO, ISSM, SA and DBA.
cci: CCI-001314
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>If the DBMS provides too much information in error logs and administrative messages to the screen, this could lead to compromise. The structure and content of error messages need to be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements. 

  Some default DBMS error messages can contain information that could aid an attacker in, among others things, identifying the database type, host address, or state of the database. Custom errors may contain sensitive customer information. 

  It is important that detailed error messages be visible only to those who are authorized to view them; that general users receive only generalized acknowledgment that errors have occurred; and that these generalized messages appear only when relevant to the user's task. For example, a message along the lines of, "An error has occurred. Unable to save your changes. If this problem persists, please contact your help desk" would be relevant. A message such as "Warning: your transaction generated a large number of page splits" would likely not be relevant. 

  Administrative users authorized to review detailed error messages typically are the ISSO, ISSM, SA, and DBA. Other individuals or roles may be specified according to organization-specific needs, with appropriate approval.

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS settings, custom database code, and associated application code not to display detailed error messages to those not authorized to view them.

check_text:
  Check DBMS settings and custom database code to determine if detailed error messages are ever displayed to unauthorized individuals.

  If detailed error messages are displayed to individuals not authorized to view them, this is a finding.


vuln_id: V-206580
rule_id: SV-206580r1043182_rule
severity: CAT II
cci: CCI-002361
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.

description:
  <VulnDiscussion>This addresses the termination of user-initiated logical sessions in contrast to the termination of network connections that are associated with communications sessions (i.e., network disconnect). A logical session (for local, network, and remote access) is initiated whenever a user (or process acting on behalf of a user) accesses an organizational information system. Such user sessions can be terminated (and thus terminate user access) without terminating network sessions. 

  Session termination ends all processes associated with a user's logical session except those batch processes/jobs that are specifically created by the user (i.e., session owner) to continue after the session is terminated. 

  Conditions or trigger events requiring automatic session termination can include, for example, organization-defined periods of user inactivity, targeted responses to certain types of incidents, and time-of-day restrictions on information system use.

  This capability is typically reserved for specific cases where the system owner, data owner, or organization requires additional assurance.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to automatically terminate a user session after organization-defined conditions or trigger events requiring session termination.

check_text:
  Review system documentation to obtain the organization's definition of circumstances requiring automatic session termination. If the documentation explicitly states that such termination is not required or is prohibited, this is not a finding.

  If the documentation requires automatic session termination, but the DBMS is not configured accordingly, this is a finding.


vuln_id: V-206581
rule_id: SV-206581r961224_rule
severity: CAT II
cci: CCI-002363
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must provide logout functionality to allow the user to manually terminate a session initiated by that user.

description:
  <VulnDiscussion>If a user cannot explicitly end a DBMS session, the session may remain open and be exploited by an attacker; this is referred to as a zombie session.

  Such logout may be explicit or implicit. Examples of explicit are: clicking on a "Log Out" link or button in the application window; clicking the Windows Start button and selecting "Log Out" or "Shut Down." Examples of implicit logout are: closing the application's (main) window; powering off the workstation without invoking the OS shutdown. 

  Both the explicit and implicit logouts must be detected by the DBMS.

  In all cases, the DBMS must ensure that the user's DBMS session and all processes owned by the session are terminated. 

  This should not, however, interfere with batch processes/jobs initiated by the user during his/her online session: these should be permitted to run to completion.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Where relevant, modify the configuration to allow the user to manually terminate a session initiated by that user.

check_text:
  Determine, by reviewing DBMS documentation and/or inquiring of the vendor's technical support staff, whether the DBMS satisfies this requirement; and, if it does, determine whether this is inherent, unchangeable behavior, or a configurable feature.

  If the DBMS does not satisfy the requirement, this is a permanent finding.

  If the behavior is inherent, this is permanently not a finding.

  If the behavior is configurable, and the current configuration does not enforce it, this is a finding.


vuln_id: V-206582
rule_id: SV-206582r1138540_rule
severity: CAT II
cci: CCI-002262
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in storage.

description:
  <VulnDiscussion>Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions.

  Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. 

  These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. 

  One example includes marking data as classified or CUI. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise.

  The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Enable DBMS features, deploy third-party software, or add custom data structures, data elements and application code, to provide reliable security labeling of information in storage.

check_text:
  If security labeling is not required, this is not a finding.

  If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in storage, this is a finding.


vuln_id: V-206583
rule_id: SV-206583r1138541_rule
severity: CAT II
cci: CCI-002263
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in process.

description:
  <VulnDiscussion>Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions.

  Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. 

  These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. 

  One example includes marking data as classified or CUI. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise.

  The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Enable DBMS features, deploy third-party software, or add custom data structures, data elements and application code, to provide reliable security labeling of information in process.

check_text:
  If security labeling is not required, this is not a finding.

  If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in process, this is a finding.


vuln_id: V-206584
rule_id: SV-206584r1138542_rule
severity: CAT II
cci: CCI-002264
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must associate organization-defined types of security labels having organization-defined security label values with information in transmission.

description:
  <VulnDiscussion>Without the association of security labels to information, there is no basis for the DBMS to make security-related access-control decisions.

  Security labels are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information. 

  These labels are typically associated with internal data structures (e.g., tables, rows) within the database and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy. 

  One example includes marking data as classified or CUI. These security labels may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security labels are lost when the data is stored, there is the risk of a data compromise.

  The mechanism used to support security labeling may be a feature of the DBMS product, a third-party product, or custom application code.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Enable DBMS features, deploy third-party software, or add custom data structures, data elements and application code, to provide reliable security labeling of information in transmission.

check_text:
  If security labeling is not required, this is not a finding.

  If security labeling requirements have been specified, but the security labeling is not implemented or does not reliably maintain labels on information in transmission, this is a finding.


vuln_id: V-206585
rule_id: SV-206585r961317_rule
severity: CAT II
cci: CCI-002165
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.

description:
  <VulnDiscussion>Discretionary Access Control (DAC) is based on the notion that individual users are "owners" of objects and therefore have discretion over who should be authorized to access the object and in which mode (e.g., read or write). Ownership is usually acquired as a consequence of creating the object or via specified ownership assignment. DAC allows the owner to determine who will have access to objects they control. An example of DAC includes user-controlled table permissions.

  When discretionary access control policies are implemented, subjects are not constrained with regard to what actions they can take with information for which they have already been granted access. Thus, subjects that have been granted access to information are not prevented from passing (i.e., the subjects have the discretion to pass) the information to other subjects or objects. 

  A subject that is constrained in its operation by Mandatory Access Control policies is still able to operate under the less rigorous constraints of this requirement. Thus, while Mandatory Access Control imposes constraints preventing a subject from passing information to another subject operating at a different sensitivity level, this requirement permits the subject to pass the information to any subject at the same sensitivity level. 

  The policy is bounded by the information system boundary. Once the information is passed outside of the control of the information system, additional means may be required to ensure the constraints remain in effect. While the older, more traditional definitions of discretionary access control require identity-based access control, that limitation is not required for this use of discretionary access control.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Implement the organization's DAC policy in the security configuration of the database and DBMS, and, if applicable, the security configuration of the application(s) using the database.

check_text:
  Review system documentation to identify the required discretionary access control (DAC).

  Review the security configuration of the database and DBMS. If applicable, review the security configuration of the application(s) using the database.

  If the discretionary access control defined in the documentation is not implemented in the security configuration, this is a finding.


vuln_id: V-206586
rule_id: SV-206586r961353_rule
severity: CAT II
fix_text: Configure DBMS security to protect all privileged functionality.
cci: CCI-002235
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must prevent non-privileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.

description:
  <VulnDiscussion>Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges. 

  System documentation should include a definition of the functionality considered privileged.

  Depending on circumstances, privileged functions can include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.

  A privileged function in the DBMS/database context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to: 
  CREATE
  ALTER
  DROP
  GRANT
  REVOKE
  DENY

  There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples include:

  TRUNCATE TABLE;
  DELETE, or
  DELETE affecting more than n rows, for some n, or
  DELETE without a WHERE clause;

  UPDATE or
  UPDATE affecting more than n rows, for some n, or
  UPDATE without a WHERE clause;

  any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal.

  Depending on the capabilities of the DBMS and the design of the database and associated applications, the prevention of unauthorized use of privileged functions may be achieved by means of DBMS security features, database triggers, other mechanisms, or a combination of these.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Review the system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question.

  Review the DBMS security configuration and/or other means used to protect privileged functionality from unauthorized use.

  If the configuration does not protect all of the actions defined as privileged, this is a finding.


vuln_id: V-206587
rule_id: SV-206587r961359_rule
severity: CAT II
cci: CCI-002233
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Execution of software modules (to include stored procedures, functions, and triggers) with elevated privileges must be restricted to necessary cases only.

description:
  <VulnDiscussion>In certain situations, to provide required functionality, a DBMS needs to execute internal logic (stored procedures, functions, triggers, etc.) and/or external code modules with elevated privileges. However, if the privileges required for execution are at a higher level than the privileges assigned to organizational users invoking the functionality applications/programs, those users are indirectly provided with greater privileges than assigned by organizations.

  Privilege elevation must be utilized only where necessary and protected from misuse.

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Determine where, when, how, and by what principals/subjects elevated privilege is needed. 

  Modify the database and DBMS security configuration, DBMS internal logic, external modules invoked by the DBMS, and the application(s) using the database, to ensure privilege elevation is used only as required.

check_text:
  Review the system documentation, database and DBMS security configuration, source code for DBMS internal logic, source code of external modules invoked by the DBMS, and source code of the application(s) using the database.

  If elevation of DBMS privileges is utilized but not documented, this is a finding.

  If elevation of DBMS privileges is documented, but not implemented as described in the documentation, this is a finding.

  If the privilege-elevation logic can be invoked in ways other than intended, or in contexts other than intended, or by subjects/principals other than intended, this is a finding.


vuln_id: V-206591
rule_id: SV-206591r961392_rule
severity: CAT II
fix_text: Allocate sufficient audit file/table space to support peak demand.
cci: CCI-001849
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.

description:
  <VulnDiscussion>In order to ensure sufficient storage capacity for the audit logs, the DBMS must be able to allocate audit record storage capacity. Although another requirement (SRG-APP-000515-DB-000318) mandates that audit data be off-loaded to a centralized log management system, it remains necessary to provide space on the database server to serve as a buffer against outages and capacity limits of the off-loading mechanism.

  The task of allocating audit record storage capacity is usually performed during initial installation of the DBMS and is closely associated with the DBA and system administrator roles. The DBA or system administrator will usually coordinate the allocation of physical drive space with the application owner/installer and the application will prompt the installer to provide the capacity information, the physical location of the disk, or both.

  In determining the capacity requirements, consider such factors as: total number of users; expected number of concurrent users during busy periods; number and type of events being monitored; types and amounts of data being captured; the frequency/speed with which audit records are off-loaded to the central log management system; and any limitations that exist on the DBMS's ability to reuse the space formerly occupied by off-loaded records.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Investigate whether there have been any incidents where the DBMS ran out of audit log space since the last time the space was allocated or other corrective measures were taken.

  If there have been, this is a finding.


vuln_id: V-206592
rule_id: SV-206592r961398_rule
severity: CAT II
cci: CCI-001855
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.

description:
  <VulnDiscussion>Organizations are required to use a central log management system, so, under normal conditions, the audit space allocated to the DBMS on its own server will not be an issue. However, space will still be required on the DBMS server for audit records in transit, and, under abnormal conditions, this could fill up. Since a requirement exists to halt processing upon audit failure, a service outage would result.

  If support personnel are not notified immediately upon storage volume utilization reaching 75%, they are unable to plan for storage capacity expansion. 

  The appropriate support staff include, at a minimum, the ISSO and the DBA/SA.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the system to notify appropriate support staff immediately upon storage volume utilization reaching 75%.

check_text:
  Review system configuration.

  If appropriate support staff are not notified immediately upon storage volume utilization reaching 75%, this is a finding.


vuln_id: V-206593
rule_id: SV-206593r961401_rule
severity: CAT II
cci: CCI-001858
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must provide an immediate real-time alert to appropriate support staff of all audit log failures.

description:
  <VulnDiscussion>It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an impending failure of the audit capability, and system operation may be adversely affected. 

  The appropriate support staff include, at a minimum, the ISSO and the DBA/SA.

  A failure of database auditing will result in either the database continuing to function without auditing or in a complete halt to database operations. When audit processing fails, appropriate personnel must be alerted immediately to avoid further downtime or unaudited transactions.

  Alerts provide organizations with urgent messages. Real-time alerts provide these messages immediately (i.e., the time from event detection to alert occurs in seconds or less).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the system to provide immediate real-time alerts to appropriate support staff when an audit log failure occurs.

check_text:
  Review DBMS settings, OS, or third-party logging software settings to determine whether a real-time alert will be sent to the appropriate personnel when auditing fails for any reason.

  If real-time alerts are not sent upon auditing failure, this is a finding.


vuln_id: V-206594
rule_id: SV-206594r961443_rule
severity: CAT II
fix_text: Ensure the DBMS generates time stamps, in audit records and application data, that maps to UTC.
cci: CCI-001890
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must record time stamps, in audit records and application data, that can be mapped to Coordinated Universal Time (UTC, formerly GMT).

description:
  <VulnDiscussion>If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis.

  Time stamps generated by the DBMS must include date and time. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. 

  Some DBMS products offer a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Verify that the DBMS generates time stamps, in audit records and application data, that maps to UTC.

  If it does not, this is a finding.


vuln_id: V-206595
rule_id: SV-206595r961446_rule
severity: CAT II
cci: CCI-001889
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate time stamps, for audit records and application data, with a minimum granularity of one second.

description:
  <VulnDiscussion>Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. 

  Time stamps generated by the DBMS must include date and time. Granularity of time measurements refers to the precision available in time stamp values. Granularity coarser than one second is not sufficient for audit trail purposes. Time stamp values are typically presented with three or more decimal places of seconds; however, the actual granularity may be coarser than the apparent precision. For example, SQL Server's GETDATE()/CURRENT_TMESTAMP values are presented to three decimal places, but the granularity is not one millisecond: it is about 1/300 of a second.

  Some DBMS products offer a data type called TIMESTAMP that is not a representation of date and time. Rather, it is a database state counter and does not correspond to calendar and clock time. This requirement does not refer to that meaning of TIMESTAMP.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS that can generate and record time stamps with a granularity of one second or finer.

  Configure auditing so that the time stamps are recorded to a precision of one second or finer.

  Modify applications and/or column/field definitions so that the time stamps in audit trail columns/fields in application data are recorded to a precision of one second or finer.

check_text:
  Review product documentation to verify that the DBMS can generate time stamps with a granularity of one second or finer. If it cannot, this is a finding.

  Review audit log records produced by the DBMS for confirmation that time stamps are recorded to a precision of one second or finer. If not, this is a finding.

  Review time stamp values in audit trail columns/fields in application data in the database. If the time stamps are not recorded to a precision of one second or finer, this is a finding.


vuln_id: V-206596
rule_id: SV-206596r981956_rule
severity: CAT II
cci: CCI-003980
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.

description:
  <VulnDiscussion>Allowing regular users to install software, without explicit privileges, creates the risk that untested or potentially malicious software will be installed on the system. Explicit privileges (escalated or administrative privileges) provide the regular user with explicit capabilities and control that exceed the rights of a regular user.

  DBMS functionality and the nature and requirements of databases will vary; so while users are not permitted to install unapproved software, there may be instances where the organization allows the user to install approved software packages such as from an approved software repository. The requirements for production servers will be more restrictive than those used for development and research.

  The DBMS must enforce software installation by users based upon what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software whose pedigree with regard to being potentially malicious is unknown or suspect) by the organization). 

  In the case of a database management system, this requirement covers stored procedures, functions, triggers, views, etc.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Document and obtain approval for any nonadministrative users who require the ability to create, alter or replace logic modules.

  Implement the approved permissions. Revoke any unapproved permissions.

check_text:
  If the DBMS supports only software development, experimentation and/or developer-level testing (that is, excluding production systems, integration testing, stress testing, and user acceptance testing), this is not a finding.

  Review the DBMS and database security settings with respect to nonadministrative users' ability to create, alter, or replace logic modules, to include but not necessarily only stored procedures, functions, triggers, and views.

  If any such permissions exist and are not documented and approved, this is a finding.


vuln_id: V-206597
rule_id: SV-206597r961461_rule
severity: CAT II
cci: CCI-001813
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must enforce access restrictions associated with changes to the configuration of the DBMS or database(s).

description:
  <VulnDiscussion>Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system. 

  When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can potentially have significant effects on the overall security of the system. 

  Accordingly, only qualified and authorized individuals should be allowed to obtain access to system components for the purposes of initiating changes, including upgrades and modifications.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of enforcing access restrictions associated with changes to the configuration of the DBMS or database(s).

  Configure the DBMS to enforce access restrictions associated with changes to the configuration of the DBMS or database(s).

check_text:
  Review DBMS vendor documentation with respect to its ability to enforce access restrictions associated with changes to the configuration of the DBMS or database(s).

  If it is not able to do this, this is a finding.

  Review the security configuration of the DBMS and database(s).

  If it does not enforce access restrictions associated with changes to the configuration of the DBMS or database(s), this is a finding.


vuln_id: V-206598
rule_id: SV-206598r981958_rule
severity: CAT II
cci: CCI-003938
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must produce audit records of its enforcement of access restrictions associated with changes to the configuration of the DBMS or database(s).

description:
  <VulnDiscussion>Without auditing the enforcement of access restrictions against changes to configuration, it would be difficult to identify attempted attacks and an audit trail would not be available for forensic investigation for after-the-fact actions. 

  Enforcement actions are the methods or mechanisms used to prevent unauthorized changes to configuration settings. Enforcement action methods may be as simple as denying access to a file based on the application of file permissions (access restriction). Audit items may consist of lists of actions blocked by access restrictions or changes identified after the fact.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to change the configuration of the DBMS or database(s).

  Configure the DBMS to produce audit records when it denies attempts to change the configuration of the DBMS or database(s).

  Configure the DBMS to produce audit records when other errors prevent attempts to change the configuration of the DBMS or database(s).

check_text:
  Review DBMS documentation to verify audit records can be produced when the system denies or fails to complete attempts to change the configuration of the DBMS or database(s).

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to change the configuration of the DBMS or database(s).

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to change the configuration of the DBMS or database(s).

  If they are not produced, this is a finding.


vuln_id: V-206599
rule_id: SV-206599r961470_rule
severity: CAT II
cci: CCI-001762
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.

description:
  <VulnDiscussion>Use of nonsecure network functions, ports, protocols, and services exposes the system to avoidable threats.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of disabling a network function, port, protocol, or service prohibited by the PPSM guidance.

  Disable each prohibited network function, port, protocol, or service.

check_text:
  Review the network functions, ports, protocols, and services supported by the DBMS.

  If any protocol is prohibited by the PPSM guidance and is enabled, this is a finding.


vuln_id: V-206600
rule_id: SV-206600r1050788_rule
severity: CAT II
cci: CCI-002038
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.

description:
  <VulnDiscussion>The DOD standard for authentication of an interactive user is the presentation of a Common Access Card (CAC) or other physical token bearing a valid, current, DOD-issued Public Key Infrastructure (PKI) certificate, coupled with a Personal Identification Number (PIN) to be entered by the user at the beginning of each session and whenever reauthentication is required.

  Without reauthentication, users may access resources or perform tasks for which they do not have authorization. 

  When applications provide the capability to change security roles or escalate the functional capability of the application, it is critical the user reauthenticate.

  In addition to the reauthentication requirements associated with session locks, organizations may require reauthentication of individuals and/or devices in other situations, including (but not limited to) the following circumstances:

  (i) When authenticators change; 
  (ii) When roles change; 
  (iii) When security categories of information systems change; 
  (iv) When the execution of privileged functions occurs; 
  (v) After a fixed period of time; or
  (vi) Periodically.

  Within the DOD, the minimum circumstances requiring reauthentication are privilege escalation and role changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify and/or configure the DBMS and related applications and tools so that users are always required to reauthenticate when changing role or escalating privileges.

  Modify and/or configure the DBMS and related applications and tools so that users are always required to reauthenticate when the specified cases needing reauthorization occur.

check_text:
  Review the system documentation and the configuration of the DBMS and related applications and tools.

  If there are any circumstances under which a user is not required to reauthenticate when changing role or escalating privileges, this is a finding.

  If the information owner has identified additional cases where reauthentication is needed, but there are circumstances where the system does not ask the user to reauthenticate when those cases occur, this is a finding.


vuln_id: V-206601
rule_id: SV-206601r961521_rule
severity: CAT II
title: The DBMS must prohibit the use of cached authenticators after an organization-defined time period.
cci: CCI-002007
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>If cached authentication information is out-of-date, the validity of the authentication information may be questionable.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Modify system settings to implement the organization-defined limit on the lifetime of cached authenticators.

check_text:
  Review system settings to determine whether the organization-defined limit for cached authentication is implemented.

  If it is not implemented, this is a finding.


vuln_id: V-206603
rule_id: SV-206603r961596_rule
severity: CAT II
check_text: If the DBMS will accept non-DoD approved PKI end-entity certificates, this is a finding.
cci: CCI-002470
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.

description:
  <VulnDiscussion>Only DoD-approved external PKIs have been evaluated to ensure that they have security controls and identity vetting procedures in place which are sufficient for DoD systems to rely on the identity asserted in the certificate.  PKIs lacking sufficient security controls and identity vetting procedures risk being compromised and issuing certificates that enable adversaries to impersonate legitimate users. 

  The authoritative list of DoD-approved PKIs is published at http://iase.disa.mil/pki-pke/interoperability.

  This requirement focuses on communications protection for the DBMS session rather than for the network packet.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Revoke trust in any certificates not issued by a DoD-approved certificate authority.   Configure the DBMS to accept only DoD and DoD-approved PKI end-entity certificates.


vuln_id: V-206604
rule_id: SV-206604r1018552_rule
severity: CAT I
cci: CCI-002475
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS 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.

description:
  <VulnDiscussion>DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation.

  Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). 

  The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS, operating system/file system, and additional software as relevant, to provide the required level of cryptographic protection.

check_text:
  Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from modification, which must include, at a minimum, PII and classified information.

  If no information is identified as requiring such protection, this is not a finding.

  Review the configuration of the DBMS, operating system/file system, and additional software as relevant.

  If any of the information defined as requiring cryptographic protection from modification is not encrypted in a manner that provides the required level of protection, this is a finding.


vuln_id: V-206605
rule_id: SV-206605r1018553_rule
severity: CAT I
cci: CCI-002476
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.

description:
  <VulnDiscussion>DBMSs handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. These cryptographic mechanisms may be native to the DBMS or implemented via additional software or operating system/file system settings, as appropriate to the situation.

  Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). 

  The decision whether and what to encrypt rests with the data owner and is also influenced by the physical measures taken to secure the equipment and media on which the information resides.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS, operating system/file system, and additional software as relevant, to provide the required level of cryptographic protection for information requiring cryptographic protection against disclosure.

  Secure the premises, equipment, and media to provide the required level of physical protection.

check_text:
  Review the system documentation to determine whether the organization has defined the information at rest that is to be protected from disclosure, which must include, at a minimum, PII and classified information.

  If the documentation indicates no information requires such protections, this is not a finding.

  Review the configuration of the DBMS, operating system/file system, and additional software as relevant.

  If any of the information defined as requiring protection is not encrypted in a manner that provides the required level of protection and is not physically secured to the required level, this is a finding.


vuln_id: V-206606
rule_id: SV-206606r1137659_rule
severity: CAT II
title: The DBMS must maintain a separate execution domain for each executing process.
cci: CCI-002530
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Database management systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each process has a distinct address space so that communication between processes is controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of maintaining a separate execution domain for each executing process.

  If this is a configurable feature, configure the DBMS to implement it.

check_text:
  Review the DBMS architecture to find out if and how it protects the private resources of one process (such as working memory, temporary tables, uncommitted data and, especially, executable code) from unauthorized access or modification by another user or process.

  If it is not capable of maintaining a separate execution domain for each executing process, this is a finding.

  If the DBMS is capable of maintaining a separate execution domain for each executing process, but is configured not to do so, this is a finding.


vuln_id: V-206607
rule_id: SV-206607r961638_rule
severity: CAT II
cci: CCI-002420
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must maintain the confidentiality and integrity of information during preparation for transmission.

description:
  <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.

  Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. 

  When transmitting data, the DBMS, associated applications, and infrastructure must leverage transmission protection mechanisms.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Implement protective measures against unauthorized disclosure and modification during preparation for transmission.

check_text:
  If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, this is not a finding.

  If the DBMS does not employ protective measures against unauthorized disclosure and modification during preparation for transmission, this is a finding.


vuln_id: V-206608
rule_id: SV-206608r961641_rule
severity: CAT II
title: The DBMS must maintain the confidentiality and integrity of information during reception.
fix_text: Implement protective measures against unauthorized disclosure and modification during reception.
cci: CCI-002422
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information.

  This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. 

  When receiving data, the DBMS, associated applications, and infrastructure must leverage protection mechanisms.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, this is not a finding.

  If the DBMS, associated applications, and infrastructure do not employ protective measures against unauthorized disclosure and modification during reception, this is a finding.


vuln_id: V-206609
rule_id: SV-206609r961656_rule
severity: CAT II
cci: CCI-002754
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  When invalid inputs are received, the DBMS must behave in a predictable and documented manner that reflects organizational and system objectives.

description:
  <VulnDiscussion>A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.

  The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.

  This calls for inspection of application source code, which will require collaboration with the application developers. It is recognized that in many cases, the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue has been addressed, and must document what has been discovered.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Revise and deploy the source code for database program objects (stored procedures, functions, triggers) and application source code, to implement the documented behavior.

check_text:
  Review system documentation to determine how input errors are to be handled in general and if any special handling is defined for specific circumstances.

  Review the source code for database program objects (stored procedures, functions, triggers) and application source code to identify how the system responds to invalid input.

  If it does not implement the documented behavior, this is a finding.


vuln_id: V-206610
rule_id: SV-206610r961677_rule
severity: CAT II
fix_text: Identify and remove software components that have been replaced or made unnecessary.
cci: CCI-002617
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  When updates are applied to the DBMS software, any software components that have been replaced or made unnecessary must be removed.

description:
  <VulnDiscussion>Previous versions of DBMS components that are not removed from the information system after updates have been installed may be exploited by adversaries. 

  Some DBMSs' installation tools may remove older versions of software automatically from the information system. In other cases, manual review and removal will be required. In planning installations and upgrades, organizations must include steps (automated, manual, or both) to identify and remove the outdated modules.

  A transition period may be necessary when both the old and the new software are required. This should be taken into account in the planning.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  If software components that have been replaced or made unnecessary are not removed, this is a finding.


vuln_id: V-206611
rule_id: SV-206611r1137667_rule
severity: CAT II
cci: CCI-002605
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  Security-relevant software updates to the DBMS must be installed within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

description:
  <VulnDiscussion>Security flaws with software applications, including database management systems, are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. 

  Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). 

  This requirement will apply to software patch management solutions used to install patches across the enclave and to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality, will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period utilized must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process.

  The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Install security-relevant software updates to the DBMS within 30 days unless the time period is directed by an authoritative source.

check_text:
  Verify security-relevant software updates to the DBMS are installed within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

  If security-relevant software updates to the DBMS are not installed within 30 days unless the time period is directed by an authoritative source, this is a finding.


vuln_id: V-206612
rule_id: SV-206612r961791_rule
severity: CAT II
title: The DBMS must be able to generate audit records when security objects are accessed.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes to the security configuration must be tracked.

  This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality.

  In an SQL environment, types of access include, but are not necessarily limited to:
  SELECT
  INSERT
  UPDATE
  DELETE
  EXECUTE</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when security objects, such as tables, views, procedures, and functions, are accessed.

  Configure the DBMS to produce audit records when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.

check_text:
  If the DBMS architecture makes it impossible for any user, even with the highest privileges, to directly view or directly modify the contents of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.

  If they are not produced, this is a finding.


vuln_id: V-206613
rule_id: SV-206613r961791_rule
severity: CAT II
title: The DBMS must generate audit records when unsuccessful attempts to access security objects occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes to the security configuration must be tracked.

  This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality.

  In an SQL environment, types of access include, but are not necessarily limited to:
  SELECT
  INSERT
  UPDATE
  DELETE
  EXECUTE

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete access to security objects, such as tables, views, procedures, and functions.

  Configure the DBMS to produce audit records when it denies access to security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic.

  Configure the DBMS to produce audit records when other errors prevent access to security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic.

check_text:
  If the DBMS architecture makes it impossible for any user, even with the highest privileges, to directly view or directly modify the contents of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to access security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to access security objects, such as tables, views, procedures, and functions, such access to include reads, creations, modifications and deletions of data, and execution of logic.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to access security object.

  If they are not produced, this is a finding.


vuln_id: V-206614
rule_id: SV-206614r961797_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.

description:
  <VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when categories of information are accessed.

  Configure the DBMS to produce audit records when categories of information are accessed, to include reads, creations, modifications, and deletions.

check_text:
  Review DBMS documentation to verify that audit records can be produced when categories of information are accessed, to include reads, creations, modifications, and deletions.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are accessed, to include reads, creations, modifications, and deletions.

  If they are not produced, this is a finding.


vuln_id: V-206615
rule_id: SV-206615r961797_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.

description:
  <VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete access to categories of information.

  Configure the DBMS to produce audit records when it denies access to categories of information, such access to include reads, creations, modifications and deletions.

  Configure the DBMS to produce audit records when other errors prevent access to categories of information, such access to include reads, creations, modifications and deletions.

check_text:
  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to access categories of information, such access to include reads, creations, modifications and deletions.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to access categories of information, such access to include reads, creations, modifications and deletions.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to access categories of information, such access to include reads, creations, modifications and deletions.

  If they are not produced, this is a finding.


vuln_id: V-206616
rule_id: SV-206616r961800_rule
severity: CAT II
title: The DBMS must generate audit records when privileges/permissions are added.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users.

  In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are added.

  Configure the DBMS to produce audit records when privileges/permissions/role memberships are added.

check_text:
  Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are added.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are added.

  If they are not produced, this is a finding.


vuln_id: V-206617
rule_id: SV-206617r961800_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to add privileges/permissions occur.

description:
  <VulnDiscussion>Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go undetected. 

  In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. 

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to add privileges/permissions/role membership.

  Configure the DBMS to produce audit records when it denies attempts to add privileges/permissions/role membership.

  Configure the DBMS to produce audit records when other errors prevent attempts to add privileges/permissions/role membership.

check_text:
  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to add privileges/permissions/role membership.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS denies the addition of privileges/permissions/role membership.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent the addition of privileges/permissions/role membership.

  If they are not produced, this is a finding.


vuln_id: V-206618
rule_id: SV-206618r961800_rule
severity: CAT II
title: The DBMS must generate audit records when privileges/permissions are modified.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users.

  In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are modified.

  Configure the DBMS to produce audit records when privileges/permissions/role memberships are modified.

check_text:
  If there is no distinction in the DBMS's security architecture between modifying permissions on the one hand, and adding and deleting permissions on the other hand, this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are modified.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are modified.

  If they are not produced, this is a finding.


vuln_id: V-206619
rule_id: SV-206619r961800_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to modify privileges/permissions occur.

description:
  <VulnDiscussion>Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go undetected. 

  In an SQL environment, modifying permissions is typically done via the GRANT, REVOKE, and DENY commands. 

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to modify privileges/permissions/role membership.

  Configure the DBMS to produce audit records when it denies attempts to modify privileges/permissions/role membership.

  Configure the DBMS to produce audit records when other errors prevent attempts to modify privileges/permissions/role membership.

check_text:
  If there is no distinction in the DBMS's security architecture between modifying permissions on the one hand, and adding and deleting permissions on the other hand, this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to modify privileges/permissions/role membership.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to modify privileges/permissions/role membership.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to modify privileges/permissions/role membership.

  If they are not produced, this is a finding.


vuln_id: V-206620
rule_id: SV-206620r961803_rule
severity: CAT II
title: The DBMS must generate audit records when security objects are modified.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when security objects, such as tables, views, procedures, and functions, are modified.

  Configure the DBMS to produce audit records when security objects, such as tables, views, procedures, and functions, are modified.

check_text:
  If the DBMS architecture makes it impossible for any user, even with the highest privileges, to modify the structure and logic of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when security objects are modified.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects are modified.

  If they are not produced, this is a finding.


vuln_id: V-206621
rule_id: SV-206621r961803_rule
severity: CAT II
title: The DBMS must generate audit records when unsuccessful attempts to modify security objects occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to modify security objects, such as tables, views, procedures, and functions.

  Configure the DBMS to produce audit records when it denies attempts to modify security objects, to include reads, creations, modifications, and deletions.

  Configure the DBMS to produce audit records when other errors prevent attempts to modify security objects, to include reads, creations, modifications, and deletions.

check_text:
  If the DBMS architecture makes it impossible for any user, even with the highest privileges, to modify the structure and logic of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to modify security objects.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to modify security objects.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to modify security objects.

  If they are not produced, this is a finding.


vuln_id: V-206622
rule_id: SV-206622r961809_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are modified.

description:
  <VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when categories of information are modified.

  Configure the DBMS to produce audit records when categories of information are modified.

check_text:
  Review DBMS documentation to verify that audit records can be produced when categories of information are modified.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are modified.

  If they are not produced, this is a finding.


vuln_id: V-206623
rule_id: SV-206623r961809_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to modify categories of information (e.g., classification levels/security levels) occur.

description:
  <VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete modification of categories of information.

  Configure the DBMS to produce audit records when it denies modification of categories of information.

  Configure the DBMS to produce audit records when other errors prevent modification of categories of information.

check_text:
  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to modify categories of information.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to modify categories of information.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to modify categories of information.

  If they are not produced, this is a finding.


vuln_id: V-206624
rule_id: SV-206624r961812_rule
severity: CAT II
title: The DBMS must generate audit records when privileges/permissions are deleted.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users.

  In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when privileges/permissions/role memberships are removed, revoked, or denied to any user or role.

  Configure DBMS audit settings to generate an audit record when privileges/permissions/role memberships are removed, revoked, or denied to any user or role.

check_text:
  Review DBMS documentation to verify that audit records can be produced when privileges/permissions/role memberships are removed, revoked, or denied to any user or role.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when privileges/permissions/role memberships are removed, revoked, or denied to any user or role.

  If they are not produced, this is a finding.


vuln_id: V-206625
rule_id: SV-206625r961812_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to delete privileges/permissions occur.

description:
  <VulnDiscussion>Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go undetected. 

  In an SQL environment, deleting permissions is typically done via the REVOKE or DENY command. 

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role.

  Configure the DBMS to produce audit records when it denies attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role.

  Configure the DBMS to produce audit records when other errors prevent attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role.

check_text:
  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts remove, revoke, or deny privileges/permissions/role membership to any user or role.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to remove, revoke, or deny privileges/permissions/role membership to any user or role.

  If they are not produced, this is a finding.


vuln_id: V-206626
rule_id: SV-206626r961818_rule
severity: CAT II
title: The DBMS must generate audit records when security objects are deleted.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an event occurs, it must be logged.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when security objects are deleted.

  Configure the DBMS to produce audit records when security objects are deleted.

check_text:
  If the DBMS architecture makes it impossible for any user, even with the highest privileges, to drop its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when security objects are drop.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects are drop.

  If they are not produced, this is a finding.


vuln_id: V-206627
rule_id: SV-206627r961818_rule
severity: CAT II
title: The DBMS must generate audit records when unsuccessful attempts to delete security objects occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete attempts to delete security objects.

  Configure the DBMS to produce audit records when it denies attempts to delete security objects.

  Configure the DBMS to produce audit records when other errors prevent attempts to delete security objects.

check_text:
  If the DBMS architecture makes it impossible for any user, even with the highest privileges, to drop its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.

  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to drop security objects.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to drop security objects.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to drop security objects.

  If they are not produced, this is a finding.


vuln_id: V-206628
rule_id: SV-206628r961821_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.

description:
  <VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when categories of information are deleted.

  Configure the DBMS to produce audit records when categories of information are deleted.

check_text:
  Review DBMS documentation to verify that audit records can be produced when categories of information are deleted.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when categories of information are deleted.

  If they are not produced, this is a finding.


vuln_id: V-206629
rule_id: SV-206629r961821_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.

description:
  <VulnDiscussion>Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

  For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when it denies or fails to complete deletion of categories of information.

  Configure the DBMS to produce audit records when it denies deletion of categories of information.

  Configure the DBMS to produce audit records when other errors prevent deletion of categories of information.

check_text:
  Review DBMS documentation to verify that audit records can be produced when the system denies or fails to complete attempts to delete categories of information.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the system denies attempts to delete categories of information.

  If they are not produced, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when other errors prevent attempts to delete categories of information.

  If they are not produced, this is a finding.


vuln_id: V-206630
rule_id: SV-206630r961824_rule
severity: CAT II
title: The DBMS must generate audit records when successful logons or connections occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to track who/what (a user or other principal) logs on to the DBMS.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS audit settings to generate an audit record each time a user (or other principal) logs on or connects to the DBMS. Ensure that the audit record contains the time of the event, the user ID, and session identifier.

check_text:
  Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) logs on or connects to the DBMS, this is a finding.


vuln_id: V-206631
rule_id: SV-206631r961824_rule
severity: CAT II
title: The DBMS must generate audit records when unsuccessful logons or connection attempts occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to track failed attempts to log on to the DBMS. While positive identification may not be possible in a case of failed authentication, as much information as possible about the incident must be captured.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS audit settings to generate an audit record each time a user (or other principal) attempts but fails to log on or connect to the DBMS.

  Include attempts where the user ID is invalid/unknown. Ensure that the audit record contains the time of the event and the user ID that was entered (if any).

check_text:
  Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) attempts but fails to log on or connect to the DBMS (including attempts where the user ID is invalid/unknown), this is a finding.


vuln_id: V-206632
rule_id: SV-206632r961827_rule
severity: CAT II
title: The DBMS must generate audit records for all privileged activities or other system-level access.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 

  System documentation should include a definition of the functionality considered privileged.

  A privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to:
  CREATE
  ALTER
  DROP
  GRANT
  REVOKE
  DENY

  There may also be Data Manipulation Language (DML) statements that, subject to context, should be regarded as privileged. Possible examples in SQL include:

  TRUNCATE TABLE;
  DELETE, or
  DELETE affecting more than n rows, for some n, or
  DELETE without a WHERE clause;

  UPDATE or
  UPDATE affecting more than n rows, for some n, or
  UPDATE without a WHERE clause;

  any SELECT, INSERT, UPDATE, or DELETE to an application-defined security table executed by other than a security principal.

  Depending on the capabilities of the DBMS and the design of the database and associated applications, audit logging may be achieved by means of DBMS auditing features, database triggers, other mechanisms, or a combination of these.

  Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when privileged actions occur.

  Configure the DBMS to produce audit records when privileged actions occur.

check_text:
  Review DBMS documentation to verify that authorized administrative users can designate actions as privileged and that audit records can be produced when privileged actions occur.

  If the DBMS is not capable of this, this is a finding.

  Review the system documentation to obtain the definition of the database/DBMS functionality considered privileged in the context of the system in question. 

  Review the DBMS/database security and audit configurations and/or other means used to implement audit logging.

  If audit logging covers at least all of the actions defined as privileged, this is not a finding; otherwise, this is a finding.


vuln_id: V-206633
rule_id: SV-206633r961827_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when unsuccessful attempts to execute privileged activities or other system-level access occur.

description:
  <VulnDiscussion>Without tracking privileged activity, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 

  System documentation should include a definition of the functionality considered privileged.

  A privileged function in this context is any operation that modifies the structure of the database, its built-in logic, or its security settings. This would include all Data Definition Language (DDL) statements and all security-related statements. In an SQL environment, it encompasses, but is not necessarily limited to:
  CREATE
  ALTER
  DROP
  GRANT
  REVOKE
  DENY

  Note that it is particularly important to audit, and tightly control, any action that weakens the implementation of this requirement itself, since the objective is to have a complete audit trail of all administrative activity.

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when the DBMS prevents attempted privileged action.

  Configure the DBMS to produce audit records when the DBMS prevents attempted privileged actions.

check_text:
  Review DBMS documentation to verify that authorized administrative users can designate actions as privileged and that audit records can be produced when the DBMS prevents attempted privileged actions.

  If the DBMS is not capable of this, this is a finding.

  Review the DBMS/database security and audit configurations to verify that audit records are produced when the DBMS prevents attempted privileged actions.

  If they are not produced, this is a finding.


vuln_id: V-206634
rule_id: SV-206634r961830_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records showing starting and ending time for user access to the database(s).

description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to the DBMS lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs. 

  Disconnection may be initiated by the user or forced by the system (as in a timeout) or result from a system or network failure. To the greatest extent possible, all disconnections must be logged.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS audit settings to generate an audit record each time a user (or other principal) logs off or disconnects, whether voluntarily or forced by the system, or because of connection or other failure, from the DBMS.

  Ensure that the audit record contains the time of the event, the user ID, and session identifier.

check_text:
  Review the DBMS audit settings. If an audit record is not generated each time a user (or other principal) logs off or disconnects from the DBMS voluntarily, or forced by the system, or because of connection or other failure, this is a finding.


vuln_id: V-206635
rule_id: SV-206635r961833_rule
severity: CAT II
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must generate audit records when concurrent logons/connections by the same user from different workstations occur.

description:
  <VulnDiscussion>For completeness of forensic analysis, it is necessary to track who logs on to the DBMS.

  Concurrent connections by the same user from multiple workstations may be valid use of the system; or such connections may be due to improper circumvention of the requirement to use the CAC for authentication; or they may indicate unauthorized account sharing; or they may be because an account has been compromised.

  (If the fact of multiple, concurrent logons by a given user can be reliably reconstructed from the log entries for other events (logons/connections; voluntary and involuntary disconnections), then it is not mandatory to create additional log entries specifically for this.)</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure DBMS audit settings to generate an audit record each time a user (or other principal) who is already connected to the DBMS logs on or connects to the DBMS from a different workstation.

check_text:
  Review the DBMS audit settings. 

  If the fact of multiple, concurrent logons by a given user (or other principal) can be reliably reconstructed from the log entries for other events, then this is not a finding.

  If an audit record is not generated each time a user (or other principal) who is already connected to the DBMS logs on or connects to the DBMS from a different workstation, this is a finding.


vuln_id: V-206636
rule_id: SV-206636r961836_rule
severity: CAT II
title: The DBMS must be able to generate audit records when successful accesses to objects occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. 

  In an SQL environment, types of access include, but are not necessarily limited to:
  SELECT
  INSERT
  UPDATE
  DELETE
  EXECUTE</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when object access occurs.

  Configure audit settings to create audit records when the specified access to the specified objects occurs.

check_text:
  Review DBMS documentation to verify that administrative users can specify database objects for which access must be audited and can specify which kinds of access must be audited.

  If the DBMS is not capable of this, this is a finding.

  Review system documentation to determine whether the application owner has specified database objects (tables, views, procedures, functions, etc.) for which access must be audited. Review the DBMS/database security and audit settings to verify that the specified access to the specified objects is audited.

  If not, this is a finding.


vuln_id: V-206637
rule_id: SV-206637r961836_rule
severity: CAT II
title: The DBMS must generate audit records when unsuccessful accesses to objects occur.
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Without tracking all or selected types of access to all or selected objects (tables, views, procedures, functions, etc.), it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. 

  In an SQL environment, types of access include, but are not necessarily limited to:
  SELECT
  INSERT
  UPDATE
  DELETE
  EXECUTE

  To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS capable of producing the required audit records when object access occurs.

  Configure audit settings to create audit records when the specified access to the specified objects is unsuccessfully attempted.

check_text:
  Review DBMS documentation to verify that administrative users can specify database objects for which access must be audited, and can specify which kinds of access must be audited.

  If the DBMS is not capable of this, this is a finding.

  Review DBMS documentation to determine whether the application owner has specified database objects (tables, views, procedures, functions, etc.) for which access must be audited.

  Review the DBMS/database security and audit settings to verify that audit records are created for unsuccessful attempts at the specified access to the specified objects.

  If not, this is a finding.


vuln_id: V-206638
rule_id: SV-206638r961839_rule
severity: CAT II
title: The DBMS must generate audit records for all direct access to the database(s).
fix_text: Configure the DBMS to generate audit records for all direct access to the database(s).
cci: CCI-000172
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>In this context, direct access is any query, command, or call to the DBMS that comes from any source other than the application(s) that it supports. Examples would be the command line or a database management utility program. The intent is to capture all activity from administrative and non-standard sources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  If the DBMS does not generate audit records for all direct access to the database(s), this is a finding.


vuln_id: V-206639
rule_id: SV-206639r1137660_rule
severity: CAT II
fix_text: Implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.
cci: CCI-002450
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.

  For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  If the DBMS does not employ NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures, this is a finding.


vuln_id: V-206640
rule_id: SV-206640r1137661_rule
severity: CAT II
cci: CCI-002450
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and validate cryptographic hashes.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.

  For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Implement a NIST FIPS 140-2 or 140-3 validated cryptographic module in the DBMS for generation and verification of cryptographic hashes.

check_text:
  If the DBMS does not employ NIST FIPS 140-2 or 140-3 validated cryptographic modules to generate and verify cryptographic hashes, this is a finding.


vuln_id: V-206641
rule_id: SV-206641r1137664_rule
severity: CAT II
cci: CCI-002450
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.

  It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

  For detailed information, refer to NIST FIPS Publication 140-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

  This requirement also applies to Zero Trust initiatives.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.

check_text:
  Verify the DBMS implements NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements.

  If the DBMS does not implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to protect unclassified information requiring confidentiality and cryptographic protection, in accordance with the data owners requirements, this is a finding.


vuln_id: V-206642
rule_id: SV-206642r961860_rule
severity: CAT II
cci: CCI-001851
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must off-load audit data to a separate log management facility; this shall be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.

description:
  <VulnDiscussion>Information stored in one location is vulnerable to accidental or incidental deletion or alteration.

  Off-loading is a common process in information systems with limited audit storage capacity. 

  The DBMS may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS or deploy and configure software tools to transfer audit records to a centralized log management system, continuously and in near-real time where a continuous network connection to the log management system exists, or at least weekly in the absence of such a connection.

check_text:
  Review the system documentation for a description of how audit records are off-loaded.

  If the DBMS has a continuous network connection to the centralized log management system, but the DBMS audit records are not written directly to the centralized log management system or transferred in near-real-time, this is a finding.

  If the DBMS does not have a continuous network connection to the centralized log management system, and the DBMS audit records are not transferred to the centralized log management system weekly or more often, this is a finding.


vuln_id: V-206643
rule_id: SV-206643r961863_rule
severity: CAT II
cci: CCI-000366
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.

description:
  <VulnDiscussion>Configuring the DBMS to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. 

  In addition to this SRG, sources of guidance on security and information assurance exist. These include NSA configuration guides, CTOs, DTMs, and IAVMs. The DBMS must be configured in compliance with guidance from all such relevant sources.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS in accordance with DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs and IAVMs.

check_text:
  Review the DBMS documentation and configuration to determine if the DBMS is configured in accordance with DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs and IAVMs.

  If the DBMS is not configured in accordance with security configuration settings, this is a finding.


vuln_id: V-233495
rule_id: SV-233495r1117186_rule
severity: CAT I
cci: CCI-002450
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements.

description:
  <VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated.

  It is the responsibility of the data owner to assess the cryptography requirements in light of applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

  NSA-approved cryptography for classified networks is hardware based. This requirement addresses the compatibility of a DBMS with the encryption devices.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Deploy a DBMS compatible with the use of NSA-approved cryptography.

  Configure the DBMS and related system components to use NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards.

check_text:
  If the DBMS is deployed in an unclassified environment, this is not applicable (NA).

  If the DBMS is not configured to use NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards, this is a finding.


vuln_id: V-263602
rule_id: SV-263602r982479_rule
severity: CAT II
title: The DBMS must disable accounts when the accounts have expired.
fix_text: Configure the DBMS to disable accounts when the accounts have expired.
cci: CCI-003627
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality, which reduce the attack surface of the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Verify the DBMS is configured to disable accounts when the accounts have expired.

  If the DBMS is not configured to disable accounts when the accounts have expired, this is a finding.


vuln_id: V-263603
rule_id: SV-263603r982481_rule
severity: CAT II
title: The DBMS must disable accounts when the accounts are no longer associated to a user.
fix_text: Configure the DBMS to disable accounts when the accounts are no longer associated to a user.
cci: CCI-003628
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
description:
  <VulnDiscussion>Disabling expired, inactive, or otherwise anomalous accounts supports the concepts of least privilege and least functionality, which reduce the attack surface of the system.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

check_text:
  Verify the DBMS is configured to disable accounts when the accounts are no longer associated to a user.

  If the DBMS is not configured to disable accounts when the accounts are no longer associated to a user, this is a finding.


vuln_id: V-263604
rule_id: SV-263604r982483_rule
severity: CAT II
cci: CCI-003821
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must implement the capability to centrally review and analyze audit records from multiple components within the system.

description:
  <VulnDiscussion>Automated mechanisms for centralized reviews and analyses include Security Information and Event Management products.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to implement the capability to centrally review and analyze audit records from multiple components within the system.

check_text:
  Verify the DBMS is configured to implement the capability to centrally review and analyze audit records from multiple components within the system.

  If the DBMS is not configured to implement the capability to centrally review and analyze audit records from multiple components within the system, this is a finding.


vuln_id: V-263605
rule_id: SV-263605r982485_rule
severity: CAT II
cci: CCI-003831
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.

description:
  <VulnDiscussion>Audit information includes all information needed to successfully audit system activity, such as audit records, audit log settings, audit reports, and personally identifiable information. Audit logging tools are those programs and devices used to conduct system audit and logging activities. Protection of audit information focuses on technical protection and limits the ability to access and execute audit logging tools to authorized individuals. Physical protection of audit information is addressed by both media protection controls and physical and environmental protection controls.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.

check_text:
  Verify the DBMS is configured to alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.

  If the DBMS is not configured to alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information, this is a finding.


vuln_id: V-263606
rule_id: SV-263606r981976_rule
severity: CAT II
cci: CCI-003992
created_at: 2026-03-06 17:52:29
updated_at: 2026-03-06 20:49:06
title:
  The DBMS must prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate recognized and approved by the organization.

description:
  <VulnDiscussion>Software and firmware components prevented from installation unless signed with recognized and approved certificates include software and firmware version updates, patches, service packs, device drivers, and basic input/output system updates. Organizations can identify applicable software and firmware components by type, by specific items, or a combination of both. Digital signatures and organizational verification of such signatures is a method of code authentication.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

fix_text:
  Configure the DBMS to prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization.

check_text:
  Verify the DBMS is configured to prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate recognized and approved by the organization.

  If the DBMS is not configured to prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate that is recognized and approved by the organization, this is a finding.


