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 Diagnostic Setting captures appropriate categories

Subtitle: Framework Reference: A.8.15 Integration: Azure Monitor Activity Logs

Why this matters

Without logging control/management plane activities (like policy changes, administrative operations, and security alerts), you're blind to many critical changes in your Azure environment. Capturing these categories is a foundational step for monitoring, alerting, and investigations during incidents or audits.

What this check does

This check verifies that a Diagnostic Setting is in place for the Azure Subscription and that the following log categories are actively enabled:

  • Administrative
  • Alert
  • Policy
  • Security

Check Logic:

IF DiagnosticSetting EXISTS AND   ALL categories ['Administrative', 'Alert', 'Policy', 'Security'] are enabled THEN PASS ELSE FAIL

The check reviews the diagnostic settings configuration at the subscription level via the Azure Monitor API or CLI.

How to fix it

Remediate via Azure Portal

  1. Navigate to Monitor → Activity Log → Export Activity Logs
  2. Choose the Subscription
  3. Click Edit setting next to your diagnostic setting
  4. Enable the following categories:
    • Administrative
    • Alert
    • Policy
    • Security
  5. Select the appropriate destination (Storage Account, Event Hub, or Log Analytics)
  6. Click Save
  7. Remediate via Azure CLI

az monitor diagnostic-settings subscription create \  --subscription <subscription-id> \  --name "<diagnostic-setting-name>" \  --location <region> \  --logs '[{"category":"Administrative","enabled":true},           {"category":"Alert","enabled":true},           {"category":"Policy","enabled":true},           {"category":"Security","enabled":true}]' \  --workspace <log-analytics-workspace-id>

Remediate via PowerShell

$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 "<diagnostic-setting-name>" `  -Log $logCategories `  -WorkSpaceId <log analytics workspace ID>

Exceptions

None. This is a baseline logging requirement applicable to all production environments.

Further resources

Was this article helpful?

Powered by Product Fruits