Skip to main content
Compliance · Medium severity

AKS Cluster Diagnostic Logging Not Enabled

Control-plane logs are not retained, so an incident in the cluster cannot be reconstructed.

Free to start. No card. The playground just needs your work email.

Azureprovider
Mediumseverity
Compliancewhere it shows up
Manualfix, steps written out

AzureKubernetes

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across Azure, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Enable diagnostic logging on the AKS cluster.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
AKS Clusters on Azure
The fix, by hand
  1. AKS → the resource → Monitoring → Diagnostic settings → Add diagnostic setting.
  2. Enable category groups: kube-apiserver, kube-audit (or kube-audit-admin for lower volume), kube-controller-manager, kube-scheduler, cluster-autoscaler.
  3. Send to a Log Analytics workspace (preferred for KQL) and optionally archive to a Storage Account for long-term retention.
  4. Save; AKS streams control-plane logs within ~5 minutes.
  5. In Log Analytics, validate by running AzureDiagnostics | where Category startswith "kube-" | take 10.
  6. Set a Monitor alert on suspicious audit verbs (e.g. exec into kube-system pods) once you have a baseline.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-1355
Full reference

AKS Cluster Diagnostic Logging Not Enabled

Related checks

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·