Microsoft AzureOverview
Set audit_log_events to include CONNECTION on MySQL flexible servers.
Rationale
Enabling CONNECTION helps MySQL Database to log items such as successful and failed connection attempts to the server. Log data can be used to identify, troubleshoot, and repair configuration errors and suboptimal performance.
Impact
Further costs are incurred for storing logs, which will be significant for high-traffic databases. Determine your organization's needs before enabling.
Default Value
By default, audit_log_events is set to CONNECTION.
Remediation guidance
Remediate from Azure Portal
- Login to Azure Portal using https://portal.azure.com.
- Go to
Azure Database for MySQL flexible servers. - For each database, under
Settings, clickServer parameters. - In the filter bar, type
audit_log. - Set
audit_log_enabledtoON. - In the drop-down next to
audit_log_events, checkCONNECTION. - Click
Save. - Under
Monitoring, selectDiagnostic settings. - Select
+ Add diagnostic setting. - Provide a diagnostic setting name.
- Under
Categories, selectMySQL Audit Logs. - Specify destination details.
- Click
Save.
It may take up to 10 minutes for the logs to appear in the configured destination.
Remediate from Azure CLI
Use the below command to set audit_log_events to CONNECTION:
az mysql flexible-server parameter set --resource-group <resourceGroup> --server-name <serverName> --name audit_log_events --value CONNECTION
Remediate from PowerShell
Use the below command to set audit_log_events to CONNECTION:
Update-AzMySqlFlexibleServerConfiguration -ResourceGroupName <resourceGroup> -ServerName <serverName> -Name audit_log_events -Value CONNECTION
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Azure
Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Azure MySQL Flex Servers not logging connections
Connectors
Covered asset types
Expected check: eq []
{
mySqlFlexibleServers(
where: {
configurations_SOME: {
name: "audit_log_events"
NOT: { value_CONTAINS: "CONNECTION" }
}
}
) {
...AssetFragment
}
}
