Azure SQL Security

Azure SQL Security, Compliance and Monitoring

Secure Azure SQL Database and Managed Instance. Meet GDPR, PCI DSS, and ISO 27001 requirements.

Azure SQL Database and Azure SQL Managed Instance are the two most widely deployed Microsoft cloud database services in European enterprises. Their integration with Azure Active Directory, Microsoft Defender for Cloud, and Azure Key Vault makes them feature-rich, but proper security configuration requires understanding and applying controls across multiple Azure services. DBsafe provides unified Azure SQL security assessment, PII discovery, and compliance reporting.

AAD
Azure Active Directory authentication is preferred but often not configured
TDE
Transparent Data Encryption enabled by default but CMK configuration often absent
ADS
Advanced Data Security subscription often not activated on Azure SQL
GDPR
Azure SQL in European data centres does not automatically ensure GDPR compliance
The Challenge

Azure SQL's features are only effective when correctly configured

Azure SQL Database has some of the most advanced security features of any managed database service: Always Encrypted, Dynamic Data Masking, Row-Level Security, Advanced Threat Protection, and Microsoft Defender for SQL. These features are genuinely powerful — but they require deliberate configuration, and many Azure SQL deployments use only a fraction of the available security capabilities.

Organisations assuming that Azure SQL's native features are sufficient for compliance find that assessors and regulators expect specific configuration evidence, not just the capability to enable features.

The cost of inaction

Azure SQL without Advanced Threat Protection: no alerting on SQL injection or anomalous queries

Public network access enabled on Azure SQL: internet-accessible database endpoint

SQL authentication without AAD: password-based credentials without MFA or conditional access

Azure SQL without Vulnerability Assessment: no baseline scan for known configuration risks

The DBsafe Approach

How DBsafe secures Azure SQL deployments

01
01

Assess Azure SQL configuration comprehensively

DBsafe evaluates Azure SQL configuration across authentication, network access, encryption, backup, audit, and advanced protection settings, cross-referencing with Azure security best practices and compliance framework requirements.

02
02

Discover and classify sensitive data

Complement Azure SQL's built-in data classification with DBsafe's discovery engine, providing higher coverage and integration with your organisation's classification framework and compliance reporting.

03
03

Monitor beyond Azure SQL audit logs

Supplement Azure SQL audit logs with DBsafe's query-level monitoring, providing anomaly detection, forensic search, and tamper-evident log storage that extends beyond the capabilities of Azure SQL's native auditing.

Azure SQL authentication and access control

Azure SQL supports both SQL authentication (username and password) and Azure Active Directory authentication. AAD authentication is strongly preferred for enterprise deployments: it enables Multi-Factor Authentication, Conditional Access policies, and Privileged Identity Management for database access. SQL authentication credentials, by contrast, are long-lived and cannot be protected by the same controls as AAD identities.

DBsafe's Azure SQL assessment checks whether AAD authentication is configured, whether the AAD administrator account is set, and whether SQL authentication is required for compatibility with legacy applications or has been left enabled unnecessarily.

Azure SQL network security configuration

Azure SQL network security involves multiple layers: the server-level firewall, virtual network service endpoints, Private Endpoint, and Public Network Access settings. The security goal is to ensure that Azure SQL is not accessible from the internet and that access is restricted to authorised network segments.

DBsafe's assessment evaluates the full network configuration: whether public network access is enabled, which IP ranges are permitted in the server firewall, whether Private Endpoint or VNet service endpoints are used, and whether the configuration aligns with the database's sensitivity level.

Azure SQL Transparent Data Encryption and encryption keys

Azure SQL TDE is enabled by default, encrypting database files at rest using service-managed keys. For sensitive workloads requiring customer-managed key control, Bring Your Own Key (BYOK) via Azure Key Vault enables organisations to manage their own encryption keys.

DBsafe verifies TDE status and key management configuration for all Azure SQL databases. For deployments requiring BYOK, DBsafe checks Key Vault access policy, key rotation configuration, and the integrity of the key hierarchy.

Azure SQL Advanced Data Security features

Azure SQL's Advanced Data Security subscription includes Vulnerability Assessment (periodic scans for known security issues), Advanced Threat Protection (anomaly detection and threat alerting), and Data Discovery and Classification (automated sensitive data identification).

DBsafe assesses whether ADS is enabled and whether its components are configured to provide meaningful coverage. Vulnerability Assessment results are compared against DBsafe's independent configuration assessment. Data Classification results are supplemented with DBsafe's more comprehensive PII detection.

Azure SQL auditing and log integration

Azure SQL provides server-level and database-level auditing to Azure Blob Storage, Log Analytics, or Event Hub. Audit logs capture authentication, schema changes, and data access events. However, Azure SQL auditing does not capture full query text by default — an important gap for forensic investigation and detailed compliance evidence.

DBsafe supplements Azure SQL auditing with full query capture, including query text, execution plans, and row-level access counts. Logs are stored in DBsafe's tamper-evident archive alongside Azure SQL audit events, providing a complete, unified audit record.

Azure SQL compliance with GDPR, PCI DSS, and ISO 27001

Azure SQL is hosted in Microsoft data centres with extensive compliance certifications. However, these certifications apply to the infrastructure; compliance obligations for data stored in Azure SQL remain with the customer. GDPR compliance requires that personal data in Azure SQL is appropriately protected, access-controlled, and documented.

DBsafe's Azure SQL compliance module maps its controls to GDPR, PCI DSS, ISO 27001, and SOC 2 requirements, providing compliance evidence specific to your Azure SQL deployment. Microsoft's compliance certifications are referenced where applicable to the shared responsibility model.

Platform Capabilities

Everything you need to address Azure SQL security — in one integrated platform.

Azure SQL Configuration Assessment

Comprehensive evaluation of authentication, network, encryption, and advanced security settings.

Enhanced Data Classification

Supplement Azure SQL built-in classification with DBsafe's advanced PII detection engine.

AAD Integration Verification

Verify AAD authentication configuration, conditional access, and MFA enforcement.

Full Query Monitoring

Capture complete query text and execution context beyond Azure SQL's native audit scope.

BYOK Assessment

Verify Bring Your Own Key configuration via Azure Key Vault for sensitive workloads.

Azure SQL Compliance Reports

GDPR, PCI DSS, ISO 27001, and SOC 2 evidence reports for Azure SQL environments.

Frequently Asked Questions

Answers to the most common questions about Azure SQL security.

What are the most important security settings to configure in Azure SQL?

The most important Azure SQL security settings are: enabling Azure AD authentication and setting the AAD administrator, disabling public network access and configuring Private Endpoint, enabling server-level TDE with CMK where required, enabling Advanced Data Security (Vulnerability Assessment and Advanced Threat Protection), configuring audit logs to Log Analytics, and enabling Just-in-Time access for administrative connections.

Does Microsoft's Azure compliance certification mean my Azure SQL is compliant?

No. Microsoft's compliance certifications cover the Azure infrastructure, not the data stored in Azure SQL. GDPR, PCI DSS, HIPAA, and other regulatory obligations for your data remain entirely with your organisation. You are responsible for data classification, access control, encryption configuration, and audit logging for the data you store in Azure SQL.

Can DBsafe monitor Azure SQL in real time?

Yes. DBsafe connects to Azure SQL and provides real-time query monitoring via a proxy architecture. Queries are captured with full text, user identity, source IP, and row counts. Anomaly detection identifies unusual access patterns in real time, with alerts sent to your SIEM and notification channels.

Does DBsafe support Azure SQL Managed Instance?

Yes. DBsafe fully supports Azure SQL Managed Instance, with assessment checks specific to Managed Instance's network configuration (VNet injection, mandatory subnet requirements), authentication model, and feature set differences from Azure SQL Database.

How does DBsafe complement Azure SQL's built-in data discovery and classification?

Azure SQL's built-in data discovery provides a useful baseline but has limited coverage of complex data types and custom PII patterns specific to your industry. DBsafe provides more comprehensive coverage, including JSONB-style text parsing, industry-specific identifiers (NHS numbers, IBAN numbers, national insurance numbers), and confidence scoring that enables prioritised remediation.

Ready in 5 minutes

Fully secure and evidence your Azure SQL deployments

DBsafe provides the comprehensive configuration assessment, monitoring, and compliance reporting that Azure SQL environments require.