STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Microsoft Azure SQL Managed Instance Security Technical Implementation Guide

V-276228

CAT II (Medium)

The role(s)/group(s) used to modify database structure and logic modules inside Azure SQL Server Managed Instance must be restricted to authorized users.

Rule ID

SV-276228r1149593_rule

STIG

Microsoft Azure SQL Managed Instance Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001499

Discussion

If the Azure SQL Managed Instance 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 will 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.

Check Content

Obtain a listing of users and roles who are authorized to modify database structure and logic modules from the server documentation.
  
Execute the following query to obtain a list of database principals:

SELECT 
P.type_desc AS principal_type, 
P.name AS principal_name, 
CASE DP.class
WHEN 0 THEN DP.class_desc
ELSE O.type_desc
END AS type_desc,CASE DP.class
WHEN 0 THEN DB_NAME()
WHEN 1 THEN OBJECT_SCHEMA_NAME(DP.major_id) + '.' + OBJECT_NAME(DP.major_id)
WHEN 3 THEN SCHEMA_NAME(DP.major_id)
ELSE DP.class_desc + '(' + CAST(DP.major_id AS nvarchar) + ')'
END AS securable_name, 
DP.state_desc, 
DP.permission_name
FROM sys.database_permissions DP
JOIN sys.database_principals P ON DP.grantee_principal_id = P.principal_id
LEFT OUTER JOIN sys.all_objects O ON O.object_id = DP.major_id AND O.type IN ('TR','TA','P','X','RF','PC','IF','FN','TF','U')
WHERE DP.type IN ('AL','ALTG') AND DP.class IN (0, 1, 53);
GO

Execute the following query to obtain a list of role memberships:

SELECT R.name AS role_name, M.type_desc AS principal_type, M.name AS principal_name
FROM sys.database_principals R
JOIN sys.database_role_members DRM ON R.principal_id = DRM.role_principal_id
JOIN sys.database_principals M ON DRM.member_principal_id = M.principal_id
WHERE R.name IN ('db_ddladmin','db_owner')
AND M.name <> 'dbo';
GO
 
If unauthorized access to the principal(s)/role(s) has been granted, this is a finding.

Fix Text

Document and obtain approval for any nonadministrative user(s) who require the ability to modify database structure and logic modules.
 
If necessary, use the ALTER ROLE and/or REVOKE commands to remove unauthorized users access to modify database structure. Examples provided below:

ALTER ROLE ddladmin DROP MEMBER UnauthorizedUser;  

REVOKE SELECT ON OBJECT::test.table FROM UnauthorizedUser;

Refer to: https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-role-transact-sql?view=azuresqldb-mi-current