Microsoft AzureOverview
Enable Diagnostic settings for exporting activity logs.
Diagnostic settings are available for each individual resource within a subscription. You should configure settings for all appropriate resources in your environment.
Rationale
A diagnostic setting controls how a diagnostic log is exported. By default, logs are retained only for 90 days. Diagnostic settings should be defined so that logs can be exported and stored longer to analyze security activities within an Azure subscription.
Remediation guidance
Remediate from Azure Portal
To enable Diagnostic Settings on a subscription:
- Go to
Monitor - Click on
Activity log - Click on
Export Activity Logs - Click
+ Add diagnostic setting - Enter a
Diagnostic setting name - Select
Categoriesfor the diagnostic setting - Select the appropriate
Destination details(this may be Log Analytics, Storage Account, Event Hub, or Partner solution) - Click
Save
Remediate from Azure CLI
To configure Diagnostic Settings on a subscription:
az monitor diagnostic-settings subscription create --subscription <subscription id> --name <diagnostic settings name> --location <location> <[--event-hub <event hub ID> --event-hub-auth-rule <event hub auth rule ID>] [--storage-account <storage account ID>] [--workspace <log analytics workspace ID>] --logs "" (e.g. [{category:Security,enabled:true},{category:Administrative,enabled:true},{category:Alert,enabled:true},{category:Policy,enabled:true}])
Remediate from PowerShell
To configure Diagnostic Settings on a subscription:
$logCategories = @();
$logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Administrative -Enabled $true
$logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Security -Enabled $true
$logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Alert -Enabled $true
$logCategories += New-AzDiagnosticSettingSubscriptionLogSettingsObject -Category Policy -Enabled $true
New-AzSubscriptionDiagnosticSetting -SubscriptionId <subscription ID> -Name <[-EventHubAuthorizationRule <event hub auth rule ID> -EventHubName <event hub name>] [-StorageAccountId <storage account ID>] [-WorkSpaceId <log analytics workspace ID>] [-MarketplacePartner ID <full ARM Marketplace resource ID>]> -Log $logCategories
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 subscriptions without diagnostic settings
Connectors
Covered asset types
Expected check: eq []
{
subscriptionDiagnosticSettings(
where: {
OR: [
{ logSettings_SOME: null }
{
logSettings_SOME: {
category_IN: ["Administrative", "Alert", "Policy", "Security"]
enabled: false
}
}
]
}
) {
...AssetFragment
}
}
