Ensure that AuditActionGroups in auditing is set properly

Using Console

To remediate the misconfiguration related to AuditActionGroups in Azure, please follow the below steps:

Login to the Azure portal (https://portal.azure.com/).
Go to the Azure Active Directory service.
Select the “Audit logs” option under the Monitoring section.
In the Audit logs blade, click on the “Diagnostic settings” option.
Select the diagnostic setting that needs to be remediated.
In the “Diagnostic settings” blade, scroll down to the “Categories” section.
In the “Categories” section, ensure that the “AuditLogs” option is selected.
Under the “AuditLogs” option, select the “Select specific actions” radio button.
In the “Select specific actions” section, ensure that all the required AuditActionGroups are selected.
Click on the “Save” button to save the changes.

By following the above steps, the misconfiguration related to AuditActionGroups in Azure can be remediated.

Using CLI

To remediate the misconfiguration of AuditActionGroups in auditing for AZURE using AZURE CLI, follow these steps:

Open the AZURE CLI on your local machine or use the AZURE Cloud Shell.
Run the following command to get the current configuration of AuditActionGroups:
az monitor activity-log list --query [].categories.actionGroups
Check the output of the above command to see if AuditActionGroups are set properly. If not, proceed to the next step.
Run the following command to set the AuditActionGroups:
az monitor activity-log update --set categories.actionGroups=<comma separated list of action groups>
Replace <comma separated list of action groups> with the appropriate list of action groups. For example, if you want to set the AuditActionGroups to “Write”, “Delete”, and “Action”, the command would be:
az monitor activity-log update --set categories.actionGroups=Write,Delete,Action
Verify the configuration by running the first command again:
az monitor activity-log list --query [].categories.actionGroups
The output should now show the updated list of AuditActionGroups.

By following these steps, you can remediate the misconfiguration of AuditActionGroups in auditing for AZURE using AZURE CLI.

Using Python

To remediate the misconfiguration of AuditActionGroups in Azure using Python, follow the below steps:

Import the necessary libraries:

from azure.identity import DefaultAzureCredential
from azure.mgmt.monitor import MonitorManagementClient

Set the credentials:

credential = DefaultAzureCredential()
subscription_id = '<Your Subscription ID>'

Initialize the MonitorManagementClient:

monitor_client = MonitorManagementClient(credential, subscription_id)

Get the existing AuditActionGroups:

audit_action_groups = monitor_client.activity_log_alerts.list_action_groups(resource_group_name='<Your Resource Group Name>', action_group_name='<Your Action Group Name>')

Update the AuditActionGroups:

updated_audit_action_groups = [
    {
        "id": "/subscriptions/<Your Subscription ID>/resourceGroups/<Your Resource Group Name>/providers/microsoft.insights/actionGroups/<Your Action Group Name>",
        "action_group_type": "CustomEmail/SMS/Push/Voice",
        "short_name": "<Your Short Name>",
        "email_receivers": [
            {
                "name": "<Your Email Name>",
                "email_address": "<Your Email Address>",
                "use_common_alert_schema": True
            }
        ]
    }
]

monitor_client.action_groups.create_or_update(resource_group_name='<Your Resource Group Name>', action_group_name='<Your Action Group Name>', parameters=updated_audit_action_groups)

Verify the updated AuditActionGroups:

updated_audit_action_groups = monitor_client.activity_log_alerts.list_action_groups(resource_group_name='<Your Resource Group Name>', action_group_name='<Your Action Group Name>')

By following these steps, you can remediate the misconfiguration of AuditActionGroups in Azure using Python.

Using Terraform

resource "azurerm_mssql_server" "sql_server" {
  name                         = "SQL_SERVER_NAME"          # substitute your server name
  resource_group_name          = "RESOURCE_GROUP_NAME"      # substitute your RG
  location                     = "AZURE_REGION"             # substitute your region
  version                      = "12.0"
  administrator_login          = "SQL_ADMIN_LOGIN"
  administrator_login_password = "SQL_ADMIN_PASSWORD"
}

resource "azurerm_mssql_database" "sql_db" {
  name           = "SQL_DATABASE_NAME"   # substitute your DB name
  server_id      = azurerm_mssql_server.sql_server.id
  sku_name       = "S0"
  max_size_gb    = 10
  zone_redundant = false
}

# Database-level auditing with explicit AuditActionGroups (audit_actions_and_groups)
resource "azurerm_mssql_database_extended_auditing_policy" "sql_db_audit" {
  database_id = azurerm_mssql_database.sql_db.id

  # Storage for audit logs
  storage_endpoint                        = azurerm_storage_account.audit_sa.primary_blob_endpoint
  storage_account_access_key              = azurerm_storage_account.audit_sa.primary_access_key
  storage_account_access_key_is_secondary = false
  retention_in_days                       = 90

  # Configure AuditActionGroups to capture critical activities
  audit_actions_and_groups = [
    "DATABASE_LOGOUT_GROUP",
    "DATABASE_ROLE_MEMBER_CHANGE_GROUP",
    "DATABASE_OBJECT_CHANGE_GROUP",
    "DATABASE_OBJECT_PERMISSION_CHANGE_GROUP",
    "FAILED_DATABASE_AUTHENTICATION_GROUP",
    "SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP",
    "BATCH_COMPLETED_GROUP",
    "BATCH_STARTED_GROUP",
    "APPLICATION_ROLE_CHANGE_PASSWORD_GROUP"
  ]
}

# Example storage account for audit logs (required by the auditing policy)
resource "azurerm_storage_account" "audit_sa" {
  name                     = "AUDIT_STORAGE_ACCOUNT_NAME"  # globally unique
  resource_group_name      = "RESOURCE_GROUP_NAME"         # substitute your RG
  location                 = "AZURE_REGION"                # substitute your region
  account_tier             = "Standard"
  account_replication_type = "LRS"
}

This change does not force replacement of the SQL database or server; it updates the database auditing policy in place.To verify, terraform plan should show an update to azurerm_mssql_database_extended_auditing_policy.sql_db_audit with the audit_actions_and_groups argument being added or changed to the list you configured.

Azure Introduction

Azure Pricing

Azure Threats

Azure Misconfigurations

Ensure that AuditActionGroups in auditing is set properly

More Info:

Risk Level

Address

Compliance Standards

Triage and Remediation

Remediation

​More Info:

​Risk Level

​Address

​Compliance Standards

​Triage and Remediation

​Remediation

​