For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

Azure SQL Server allow access to any Azure internal resources misconfiguration detected in code

Rule Details

Cortex AppSec Rule ID

APPSEC2_AZURE_34

Category - Subcategory

Public Exposure - Database Endpoints

Provider

AZURE

Severity

LOW

Framework

Terraform, Terraform Plan

Mapped CSPM/KSPM Rule

7f47b618-4e96-459e-bfe3-9e6f48fec533

Impact

This rule pertains to Azure SQL server firewall settings and it checks to ensure the firewall is not set in an overly permissive way. This means that the firewall settings should not allow unrestricted access from any IP address to your SQL server. Allowing such wide-reaching access is bad because it significantly increases the security risk by offering potential hackers numerous opportunities to exploit your system. Instead, access should be limited to specific, trusted IP addresses to maintain a robust security posture.

How to Fix

Resource: azurerm_sql_firewall_rule

  • Arguments: start_ip_address, end_ip_address

To fix this rule issue, you should define firewall rules to restrict source IP ranges of Azure SQL server. The start and end IP address in the firewall rule should not be from 0.0.0.0 to 255.255.255.255 except when the access type is AzureServices.

The provided code now follows security best practices by employing input validation for the IP range. It restricts the IP range to a single IP instead of allowing all, thus reducing the risk of unauthorized access. A smaller IP range minimizes the surface area for attacks and decreases the chance that traffic comes from undesirable locations. [source,go]

resource "azurerm_sql_firewall_rule" "example" { name = "firewall_rule" resource_group_name = azurerm_resource_group.example.name server_name = azurerm_sql_server.example.name start_ip_address = "40.112.8.12" end_ip_address = "40.112.8.12" }

Last updated

Was this helpful?