Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossarySupport and Bug Reporting
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 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 restricted

Verify that Activity Log Alert exists for Delete SQL Server Firewall Rule

Framework Reference: A.8.16 Integration: Azure – Activity Log Alerts

Why this matters

Firewall rules in Azure SQL Servers control which IP addresses can access your databases. Deleting a firewall rule can immediately expose a SQL Server instance to unauthorized access or disrupt access for legitimate users.

Monitoring for Microsoft.Sql/servers/firewallRules/delete operations allows your team to detect and respond to unauthorized or accidental configuration changes. It also supports audit trails for change management and regulatory reporting.

What this check does

This Auto Check verifies whether an Activity Log Alert exists for the operation:

Microsoft.Sql/servers/firewallRules/delete

Check Logic:
Passes if:

At least one enabled alert rule exists with the following:

  • Category set to Administrative
  • Operation name equal to Microsoft.Sql/servers/firewallRules/delete
  • No filters on Level, Status, or Caller
  • An Action Group assigned for notifications

Fails if:

  • No matching rule is found or if the rule is disabled or improperly scoped.
  • This check evaluates the current alert rules using Azure Monitor’s API and validates each condition explicitly.

How to fix it

You can create the required alert using Azure Portal, CLI, or PowerShell.

Azure Portal:

  1. Go to Monitor > Alerts > Alert rules.
  2. Click Create > Alert rule.
  3. Set the scope to your subscription.
  4. Under Condition, choose:
  5. Signal: Delete server firewall rule
  6. Operation: Microsoft.Sql/servers/firewallRules/delete
  7. Category: Administrative
  8. Under Actions, assign or create an Action Group to notify your team.
  9. Under Details, enter an alert name and select a resource group.
  10. Click Review + create, then Create.

Azure CLI:

az monitor activity-log alert create \  --name "<activity log rule name>" \  --resource-group "<resource group name>" \  --scope "/subscriptions/<subscription ID>" \  --condition category=Administrative and operationName=Microsoft.Sql/servers/firewallRules/delete \  --action-group <action group ID> \  --enabled true 

PowerShell:

$conditions = @() $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal "Administrative" -Field "category" $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal "Microsoft.Sql/servers/firewallRules/delete" -Field "operationName" $conditions += New-AzActivityLogAlertAlertRuleAnyOfOrLeafConditionObject -Equal "Verbose" -Field "level" $actionGroup = Get-AzActionGroup -ResourceGroupName "<resource group name>" -Name "<action group name>" $actionObject = New-AzActivityLogAlertActionGroupObject -Id $actionGroup.Id $scope = "/subscriptions/<subscription ID>" New-AzActivityLogAlert -Name "<activity log alert rule name>" `  -ResourceGroupName "<resource group name>" `  -Condition $conditions `  -Scope $scope `  -Location "global" `  -Action $actionObject `  -Subscription "<subscription ID>" `  -Enabled $true

Update all placeholders with values from your Azure setup.

Exceptions

There are no valid exceptions. SQL Server firewall changes are sensitive and must be monitored. If an external monitoring solution is used in place of Azure Monitor, document the equivalency and ensure alerting is functionally equivalent.

Further resources

Was this article helpful?

Powered by Product Fruits