Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossaryContacting Support and Reporting Bugs
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidance
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: GCPAuto Checks: AzureEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
Verify that Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database ServerVerify that server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_connections' is set to 'ON' for PostgreSQL Database ServerVerify that 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database ServerVerify that Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database ServerVerify that Activity Log Alert exists for Create Policy AssignmentVerify that Activity Log Alert exists for Create or Update Public IP Address ruleVerify that no Azure SQL Databases allow ingress from 0.0.0.0/0 (ANY IP)Verify that Activity Log Alert exists for Delete SQL Server Firewall RuleVerify that Activity Log Alert exists for Create or Update SQL Server Firewall RuleVerify that Activity Log Alert exists for Delete Network Security GroupVerify that the storage account containing the container with activity logs is encrypted with Customer Managed KeyVerify that Activity Log Alert exists for Delete Policy AssignmentVerify that Activity Log Alert exists for Create or Update Network Security GroupVerify that Diagnostic Setting captures appropriate categoriesVerify that Activity Log Alert exists for Create or Update Security SolutionVerify that Activity Log Alert exists for Delete Public IP Address ruleVerify that logging for Azure AppService 'HTTP logs' is enabledVerify that logging for Azure Key Vault is 'Enabled'Verify that the Expiration Date is set for all Keys in RBAC Key VaultsEnable Role Based Access Control for Azure Key VaultVerify that Private Endpoints are Used for Azure Key VaultVerify that the Key Vault is RecoverableVerify that HTTP(S) access from the Internet is evaluated and restrictedVerify that SSH access from the Internet is evaluated and restrictedVerify that Network Security Group Flow Log retention period is 'greater than 90 days'Verify that Network Watcher is 'Enabled' for all locations in the Azure subscriptionVerify that RDP access from the Internet is evaluated and restrictedVerify that That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All NetworksVerify that That Private Endpoints Are Used Where PossibleVerify that 'Enforce SSL connection' is set to 'Enabled' for Standard MySQL Database ServerVerify that 'TLS Version' is set to 'TLSV1.2' for MySQL flexible Database ServerVerify that SQL server's Transparent Data Encryption (TDE) protector is encryptedVerify that 'Auditing' Retention is 'greater than 90 days'Verify that Application Insights are Configured.Verify that 'Restrict non-admin users from creating tenants' is set to 'Yes'Verify that 'Guest invite restrictions' is set to 'Only users assigned to specific admin roles can invite guest users'Verify that That 'Guest users access restrictions' is set to 'Guest user access is restricted to properties and memberships of their own directory objects'Ensure Microsoft Defender for open-source relational databases is enabledVerify that That Microsoft Defender for App Services Is Set To 'On' Verify that That 'Notify about alerts with the following severity' is Set to 'High'Verify that 'Additional email addresses' is Configured with a Security Contact EmailVerify that That Microsoft Defender for SQL Servers on Machines Is Set To 'On' Verify that That 'All users with the following roles' is set to 'Owner'Verify that That Microsoft Defender for Storage Is Set To 'On'

Verify that no Azure SQL Databases allow ingress from 0.0.0.0/0 (ANY IP)

Framework Reference: A.8.23 Integration: Azure – SQL Server

Why this matters

Allowing public ingress from 0.0.0.0/0 (any IP) exposes your SQL database to the entire internet, drastically increasing the attack surface and risk of unauthorized access. Tightening firewall rules to restrict access to known IP ranges is essential to maintain a secure network perimeter and meet compliance requirements.

What this check does

This Auto Check verifies that no firewall rule is configured to allow traffic from 0.0.0.0/0, 255.255.255.255, or named AllowAllWindowsAzureIps.

Check Logic

Passes if:

  • No firewall rule allows StartIpAddress = 0.0.0.0
  • No rule ends at EndIpAddress = 255.255.255.255
  • Rule name is not AllowAllWindowsAzureIps

Fails if:

  • Any rule allows full public ingress (e.g. 0.0.0.0/0)

Applies to:

  • Azure SQL Server
  • Azure SQL Database

How to fix it

Azure Portal

Go to SQL servers

Select the server

Navigate to Networking

Uncheck Allow Azure services and resources to access this server

Delete any firewall rule where:

Start IP = 0.0.0.0

End IP = 255.255.255.255

Rule name is AllowAllWindowsAzureIps

Azure CLI

# Delete the default open access rule az sql server firewall-rule delete \  --resource-group <resourceGroupName> \  --server <sqlServerName> \  --name "AllowAllWindowsAzureIps" # Delete any custom wide-open rules az sql server firewall-rule delete \  --resource-group <resourceGroupName> \  --server <sqlServerName> \  --name <customRuleName> # Create more restrictive firewall rule az sql server firewall-rule create \  --resource-group <resourceGroupName> \  --server <sqlServerName> \  --name <secureRuleName> \  --start-ip-address "<allowedStartIP>" \  --end-ip-address "<allowedEndIP>" 

PowerShell

# Remove insecure rules Remove-AzSqlServerFirewallRule `  -FirewallRuleName "AllowAllWindowsAzureIps" `  -ResourceGroupName <resourceGroupName> `  -ServerName <sqlServerName> Remove-AzSqlServerFirewallRule `  -FirewallRuleName "<customRuleName>" `  -ResourceGroupName <resourceGroupName> `  -ServerName <sqlServerName> # Add secure rule Set-AzSqlServerFirewallRule `  -ResourceGroupName <resourceGroupName> `  -ServerName <sqlServerName> `  -FirewallRuleName "<secureRuleName>" `  -StartIpAddress "<allowedStartIP>" `  -EndIpAddress "<allowedEndIP>"

Exceptions

No technical exceptions. In rare Dev/Test scenarios, public access may be temporarily allowed but must be removed before production. All exceptions must be time-boxed and documented.

Further resources

Was this article helpful?

Powered by Product Fruits