Overview
The Azure Kubernetes Service (AKS) integration ingests AKS control plane diagnostic logs:kube-apiserver: API server requestskube-auditandkube-audit-admin: audit decisionskube-controller-managerandkube-schedulercluster-autoscalereventsguard(AAD authorization) decisions
Prerequisites
- An AKS cluster with diagnostic settings routing the desired log categories to a Log Analytics workspace.
- An Azure AD app registration with permission to read those logs (
Readeron the resource group orLog Analytics Readeron the workspace).
Step 1: Enable AKS diagnostic settings
- In the Azure portal, open your AKS cluster.
- Go to Monitoring → Diagnostic settings → Add diagnostic setting.
- Select log categories such as
kube-apiserver,kube-audit,kube-audit-admin,kube-controller-manager,kube-scheduler,cluster-autoscaler,guard. - Choose Send to Log Analytics workspace and select your workspace.
- Click Save.
Step 2: Register an app in Azure AD
- Open Microsoft Entra ID → App registrations → New registration.
- Name it
atatus-aks-readerand click Register. - Copy the Application (client) ID and Directory (tenant) ID.
- Under Certificates & secrets, create a new client secret and copy its Value.
Step 3: Grant the app access to the cluster
- Open the AKS cluster’s Resource group → Access control (IAM) → Add role assignment.
- Assign the role Log Analytics Reader (or Reader if you also want resource metadata) to the app from Step 2.
Step 4: Connect Azure AKS in Atatus
- In Atatus, go to Security → Cloud SIEM → Integrations.
- Locate the Azure Kubernetes Service (AKS) card and click Connect.
- Fill in the form:
- Click Connect.
Verification
- The AKS card shows Configured.
- Control plane events appear in Security → Cloud SIEM → Audit Logs → Events with source
azure_aks.