Azure SQL Database must enforce approved authorizations for logical access to server information and system resources in accordance with applicable access control policies.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-255302 | ASQL-00-000200 | SV-255302r1112451_rule | High |
| Description |
| 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 noncentralized 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. Azure SQL Database 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. |
| STIG | Date |
| Microsoft Azure SQL Database Security Technical Implementation Guide | 2025-06-11 |
Details
| Check Text (C-58975r1112449_chk) |
| Review the system documentation to determine the required levels of protection for securables in the database, by type of login. Review the permissions actually in place on the server. Execute the supplemental script, "ASQL-00-000200-SERVER.sql" to find permissions assigned. If the actual permissions do not match the documented requirements, this is a finding. |
| Fix Text (F-58919r1112450_fix) |
| Use GRANT, REVOKE, DENY, ALTER SERVER ROLE … ADD MEMBER … and/or ALTER SERVER ROLE …. DROP MEMBER statements to add and remove permissions on server-level securables, bringing them in line with the documented requirements. References: Revoke: https://docs.microsoft.com/en-us/sql/t-sql/statements/revoke-transact-sql?view=azuresqldb-current Deny: https://docs.microsoft.com/en-us/sql/t-sql/statements/deny-transact-sql?view=azuresqldb-current DROP MEMBER: https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-droprolemember-transact-sql?view=azuresqldb-current |