STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

Microsoft Azure SQL Database Security Technical Implementation Guide

Version

V2R3

Benchmark ID

MS_Azure_SQL_DB_STIG

Total Checks

76

Tags

databasecloud
CAT I: 7CAT II: 69CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSON

Checks (76)

V-255301HIGHAzure SQL Databases must integrate with Azure Active Directory for providing account management and automation for all users, groups, roles, and any other principals.V-255302HIGHAzure SQL Database must enforce approved authorizations for logical access to server information and system resources in accordance with applicable access control policies.V-255303HIGHAzure SQL Database must enforce approved authorizations for logical access to database information and system resources in accordance with applicable access control policies.V-255304MEDIUMAzure SQL Database must protect against a user falsely repudiating by ensuring only clearly unique Active Directory user accounts can connect to the database.V-255305MEDIUMAzure SQL Database must protect against a user falsely repudiating by use of system-versioned tables (Temporal Tables).V-255306MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to Azure SQL Database, etc.) must be owned by database/Azure SQL Database principals authorized for ownership.V-255307MEDIUMThe 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 Azure SQL Database, etc.) must be restricted to authorized users.V-255308MEDIUMThe Azure SQL Database must isolate security functions from nonsecurity functions.V-255309MEDIUMAzure SQL Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-255310MEDIUMAzure SQL Database must check the validity of all data inputs except those specifically identified by the organization.V-255311MEDIUMThe Azure SQL Database and associated applications must reserve the use of dynamic code execution for situations that require it.V-255312MEDIUMThe Azure SQL Database and associated applications, when making use of dynamic code execution, must scan input data for invalid values that may indicate a code injection attack.V-255313MEDIUMAzure SQL Database must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-255314MEDIUMAzure SQL Database must associate organization-defined types of security labels having organization-defined security label values with information in process.V-255315MEDIUMAzure SQL Database must associate organization-defined types of security labels having organization-defined security label values with information in transmission.V-255316MEDIUMAzure SQL Database must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.V-255317MEDIUMAzure SQL Database must restrict execution of stored procedures and functions that utilize [execute as] to necessary cases only.V-255318MEDIUMAzure SQL Database must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-255319MEDIUMAzure SQL Database must enforce access restrictions associated with changes to the configuration of the Azure SQL Database server or database(s).V-255320HIGHAzure SQL Database must use NSA-approved cryptography to protect classified information in accordance with the data owners requirements.V-255321HIGHAzure SQL Database 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.V-255322HIGHAzure SQL Database must implement cryptographic mechanisms preventing the unauthorized disclosure of organization-defined information at rest on organization-defined information system components.V-255323MEDIUMWhen invalid inputs are received, the Azure SQL Database must behave in a predictable and documented manner that reflects organizational and system objectives.V-255324MEDIUMThe Azure SQL Database must be configured to generate audit records for DOD-defined auditable events within all DBMS/database components.V-255325MEDIUMAzure SQL Database must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited.V-255326MEDIUMThe Azure SQL Database must be able to generate audit records when privileges/permissions are retrieved.V-255327MEDIUMThe Azure SQL Database must be able to generate audit records when unsuccessful attempts to retrieve privileges/permissions occur.V-255328MEDIUMAzure SQL Database must initiate session auditing upon startup.V-255329MEDIUMAzure SQL Database must include additional, more detailed, organization-defined information in the audit records for audit events identified by type, location, or subject.V-255330MEDIUMThe audit information produced by Azure SQL Database must be protected from unauthorized read access.V-255331MEDIUMThe audit information produced by Azure SQL Database must be protected from unauthorized modification.V-255332MEDIUMThe audit information produced by Azure SQL Database must be protected from unauthorized deletion.V-255333MEDIUMAzure SQL Database default demonstration and sample databases, database objects, and applications must be removed.V-255334MEDIUMThe Azure SQL Database 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.V-255335MEDIUMAzure SQL Database must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-255336MEDIUMAzure SQL Database must map the PKI-authenticated identity to an associated user account.V-255337MEDIUMAzure SQL Database must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users).V-255338MEDIUMAzure SQL Database must separate user functionality (including user interface services) from database management functionality.V-255339HIGHAzure SQL Database must protect the confidentiality and integrity of all information at rest.V-255340MEDIUMAzure SQL Database must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.V-255341MEDIUMAzure SQL Database must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-255343MEDIUMAzure SQL Database must be able to allocate audit record storage capacity in accordance with organization-defined audit record storage requirements.V-255344MEDIUMAzure SQL Database must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.V-255345MEDIUMAzure SQL Database must produce audit records of its enforcement of access restrictions associated with changes to the configuration of Azure SQL Database(s).V-255346MEDIUMAzure SQL Database must only use approved firewall settings deemed by the organization to be secure, including denying public network access.V-255347MEDIUMAzure SQL Database must only use approved firewall settings deemed by the organization to be secure, including denying azure services access to the server.V-255348MEDIUMAzure SQL Database must maintain the confidentiality and integrity of information during preparation for transmission.V-255349MEDIUMAzure SQL Database must maintain the confidentiality and integrity of information during reception.V-255350MEDIUMAzure SQL DB must be able to generate audit records when security objects are accessed.V-255351MEDIUMAzure SQL DB must generate audit records when unsuccessful attempts to access security objects occur.V-255352MEDIUMAzure SQL DB must generate audit records when categorized information (e.g., classification levels/security levels) is accessed.V-255353MEDIUMAzure SQL DB must generate audit records when unsuccessful attempts to access categories of information (e.g., classification levels/security levels) occur.V-255354MEDIUMAzure SQL DB must generate audit records when privileges/permissions are added.V-255355MEDIUMAzure SQL DB must generate audit records when unsuccessful attempts to add privileges/permissions occur.V-255356MEDIUMAzure SQL DB must generate audit records when privileges/permissions are modified.V-255357MEDIUMAzure SQL DB must generate audit records when unsuccessful attempts to modify privileges/permissions occur.V-255358MEDIUMAzure SQL Database must generate audit records when security objects are modified.V-255359MEDIUMAzure SQL DB must generate audit records when unsuccessful attempts to modify security objects occur.V-255360MEDIUMAzure SQL Database must generate audit records when categorized information (e.g., classification levels/security levels) is modified.V-255361MEDIUMAzure SQL Database must generate audit records when unsuccessful attempts to modify categorized information (e.g., classification levels/security levels) occur.V-255362MEDIUMAzure SQL Database must generate audit records when privileges/permissions are deleted.V-255363MEDIUMAzure SQL Database must generate audit records when unsuccessful attempts to delete privileges/permissions occur.V-255364MEDIUMAzure SQL Database must generate audit records when security objects are deleted.V-255365MEDIUMAzure SQL Database must generate audit records when unsuccessful attempts to delete security objects occur.V-255366MEDIUMAzure SQL Database must generate audit records when categories of information (e.g., classification levels/security levels) are deleted.V-255367MEDIUMAzure SQL Database must generate audit records when unsuccessful attempts to delete categories of information (e.g., classification levels/security levels) occur.V-255368MEDIUMAzure SQL Database must generate audit records when successful logons or connections occur.V-255369MEDIUMAzure SQL Database must generate audit records when unsuccessful logons or connection attempts occur.V-255370MEDIUMAzure SQL Database must generate audit records for all privileged activities or other system-level access.V-255371MEDIUMAzure SQL Database must generate audit records for all unsuccessful attempts to execute privileged activities or other system-level access.V-255372MEDIUMAzure SQL Database must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-255373MEDIUMAzure SQL Database must generate audit records when concurrent logons/connections by the same user from different workstations occur.V-255374MEDIUMAzure SQL Database must be able to generate audit records when successful accesses to objects occur.V-255375MEDIUMAzure SQL Database must generate audit records when unsuccessful accesses to objects occur.V-255376MEDIUMAzure SQL Database must generate audit records for all direct access to the database(s).V-255377MEDIUMAzure SQL Database must offload 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.