STIGQter STIGQter: STIG Summary: Microsoft Azure SQL Managed Instance Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 23 Sep 2025:

Azure SQL Managed Instance must generate audit records when logon or connection attempts occur.

DISA Rule

SV-276259r1150012_rule

Vulnerability Number

V-276259

Group Title

SRG-APP-000503-DB-000351

Rule Version

MSQL-00-014800

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

Deploy an Azure SQL Managed Instance audit.

Refer to the supplemental file "AzureSQLMIAudit.txt" script.

Reference: https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/auditing-configure?view=azuresql

Check Contents

Review Azure SQL Managed Instance configuration to verify audit records are produced when unsuccessful logons or connection attempts occur.

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 WHERE name NOT IN ('admin_audit','SqlDbThreatDetection_ServerAudit')

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 not in the active audit, this is a finding.

Vulnerability Number

V-276259

Documentable

False

Rule Version

MSQL-00-014800

Severity Override Guidance

Review Azure SQL Managed Instance configuration to verify audit records are produced when unsuccessful logons or connection attempts occur.

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 WHERE name NOT IN ('admin_audit','SqlDbThreatDetection_ServerAudit')

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 not in the active audit, this is a finding.

Check Content Reference

M

Target Key

5711