Azure

How to harden security of Azure Kubernetes Service (AKS)

AKS Security Spans the Entire Stack

Azure Kubernetes Service (AKS) runs your containerized workloads on managed Kubernetes. Security responsibility is shared — Microsoft manages the control plane, but you own the nodes, pods, network policies, RBAC, and workload security. This guide covers hardening from cluster creation to runtime protection.

Threat Landscape and Attack Surface

Hardening Azure Kubernetes Service (AKS) requires understanding the threat landscape specific to this service. Azure services are attractive targets because they often store, process, or transmit sensitive data and provide control-plane access to cloud infrastructure. Attackers probe for misconfigured services using automated scanners that continuously sweep Azure IP ranges for exposed endpoints, weak authentication, and default configurations.

The attack surface for Azure Kubernetes Service (AKS) includes several dimensions. The network perimeter determines who can reach the service endpoints. The identity and access layer controls what authenticated principals can do. The data plane governs how data is protected at rest and in transit. The management plane controls who can modify the service configuration itself. A comprehensive hardening strategy addresses all four dimensions because a weakness in any single layer can be exploited to bypass the controls in other layers.

Microsoft’s shared responsibility model means that while Azure secures the physical infrastructure, network fabric, and hypervisor, you are responsible for configuring the service securely. Default configurations prioritize ease of setup over security. Every Azure service ships with settings that must be tightened for production use, and this guide walks through the critical configurations that should be changed from their defaults.

The MITRE ATT&CK framework for cloud environments provides a structured taxonomy of attack techniques that adversaries use against Azure services. Common techniques relevant to Azure Kubernetes Service (AKS) include initial access through exposed credentials or misconfigured endpoints, lateral movement through overly permissive RBAC assignments, and data exfiltration through unmonitored data plane operations. Each hardening control in this guide maps to one or more of these attack techniques.

Compliance and Regulatory Context

Security hardening is not just a technical exercise. It is a compliance requirement for virtually every regulatory framework that applies to cloud workloads. SOC 2 Type II requires evidence of security controls for cloud services. PCI DSS mandates network segmentation and encryption for payment data. HIPAA requires access controls and audit logging for health information. ISO 27001 demands a systematic approach to information security management. FedRAMP requires specific configurations for government workloads.

Azure Policy and Microsoft Defender for Cloud provide built-in compliance assessments against these frameworks. After applying the hardening configurations in this guide, run a compliance scan to verify your security posture against your applicable regulatory standards. Address any remaining findings to achieve and maintain compliance. Export compliance reports on a scheduled basis to satisfy audit requirements and demonstrate continuous adherence.

The Microsoft cloud security benchmark provides a comprehensive set of security controls mapped to common regulatory frameworks. Use this benchmark as a checklist to verify that your hardening effort covers all required areas. Each control includes Azure-specific implementation guidance and links to the relevant Azure service documentation.

Step 1: Create a Hardened Cluster

# Create AKS with security best practices
az aks create --name aks-prod --resource-group rg-k8s \
  --location eastus --node-count 3 --node-vm-size Standard_D4s_v5 \
  --enable-managed-identity --enable-aad --enable-azure-rbac \
  --network-plugin azure --network-policy calico \
  --enable-defender --enable-oidc-issuer --enable-workload-identity \
  --disable-local-accounts --enable-private-cluster \
  --zones 1 2 3 --auto-upgrade-channel stable \
  --tier standard

Key parameters explained:

  • --disable-local-accounts — forces Azure AD authentication for cluster access
  • --enable-private-cluster — API server only accessible via VNet
  • --network-policy calico — enables pod-level network segmentation
  • --enable-defender — runtime threat protection
  • --enable-workload-identity — pod-level Azure AD identity

Step 2: Implement Azure RBAC for Kubernetes

# Grant cluster admin to break-glass only
az role assignment create \
  --assignee "admin-group-id" \
  --role "Azure Kubernetes Service RBAC Cluster Admin" \
  --scope $(az aks show --name aks-prod --resource-group rg-k8s --query id -o tsv)

# Grant namespace-scoped access for dev teams
az role assignment create \
  --assignee "dev-team-id" \
  --role "Azure Kubernetes Service RBAC Writer" \
  --scope "$(az aks show --name aks-prod --resource-group rg-k8s --query id -o tsv)/namespaces/app-namespace"

Step 3: Enable Network Policies

# Default deny all ingress in a namespace
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: default-deny-ingress
  namespace: production
spec:
  podSelector: {}
  policyTypes:
    - Ingress

---
# Allow specific traffic
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-frontend-to-api
  namespace: production
spec:
  podSelector:
    matchLabels:
      app: api
  ingress:
    - from:
        - podSelector:
            matchLabels:
              app: frontend
      ports:
        - port: 8080
          protocol: TCP

Step 4: Configure Pod Security Standards

# Enforce restricted pod security standard
apiVersion: v1
kind: Namespace
metadata:
  name: production
  labels:
    pod-security.kubernetes.io/enforce: restricted
    pod-security.kubernetes.io/audit: restricted
    pod-security.kubernetes.io/warn: restricted
# Secure pod template
apiVersion: apps/v1
kind: Deployment
metadata:
  name: myapp
spec:
  template:
    spec:
      securityContext:
        runAsNonRoot: true
        runAsUser: 1000
        fsGroup: 2000
        seccompProfile:
          type: RuntimeDefault
      containers:
        - name: app
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            capabilities:
              drop: ["ALL"]
          resources:
            limits:
              cpu: "500m"
              memory: "256Mi"
            requests:
              cpu: "100m"
              memory: "128Mi"

Step 5: Use Workload Identity for Pod Authentication

# Create user-assigned managed identity
az identity create --name id-myapp --resource-group rg-k8s

# Create Kubernetes service account with federated credential
az identity federated-credential create \
  --name fc-myapp --identity-name id-myapp --resource-group rg-k8s \
  --issuer $(az aks show --name aks-prod --resource-group rg-k8s --query oidcIssuerProfile.issuerUrl -o tsv) \
  --subject system:serviceaccount:production:sa-myapp

# Grant identity access to Key Vault
az keyvault set-policy --name kv-prod \
  --object-id $(az identity show --name id-myapp --resource-group rg-k8s --query principalId -o tsv) \
  --secret-permissions get

Identity and Access Management Deep Dive

Identity is the primary security perimeter in cloud environments. For Azure Kubernetes Service (AKS), implement a robust identity and access management strategy that follows the principle of least privilege.

Managed Identities: Use system-assigned or user-assigned managed identities for service-to-service authentication. Managed identities eliminate the need for stored credentials (connection strings, API keys, or service principal secrets) that can be leaked, stolen, or forgotten in configuration files. Azure automatically rotates the underlying certificates, removing the operational burden of credential rotation.

Custom RBAC Roles: When built-in roles grant more permissions than required, create custom roles that include only the specific actions needed. For example, if a monitoring service only needs to read metrics and logs from Azure Kubernetes Service (AKS), create a custom role with only the Microsoft.Insights/metrics/read and Microsoft.Insights/logs/read actions rather than assigning the broader Reader or Contributor roles.

Conditional Access: For human administrators accessing Azure Kubernetes Service (AKS) through the portal or CLI, enforce Conditional Access policies that require multi-factor authentication, compliant devices, and approved locations. Set session lifetime limits so that administrative sessions expire after a reasonable period, forcing re-authentication.

Just-In-Time Access: Use Azure AD Privileged Identity Management (PIM) to provide time-limited, approval-required elevation for administrative actions. Instead of permanently assigning Contributor or Owner roles, require administrators to activate their role assignment for a specific duration with a business justification. This reduces the window of exposure if an administrator’s account is compromised.

Service Principal Hygiene: If managed identities cannot be used (for example, for external services or CI/CD pipelines), use certificate-based authentication for service principals rather than client secrets. Certificates are harder to accidentally expose than text secrets, and Azure Key Vault can automate their rotation. Set short expiration periods for any client secrets and monitor for secrets that are approaching expiration.

Step 6: Secure the Container Supply Chain

# Attach ACR to AKS (managed identity-based pull)
az aks update --name aks-prod --resource-group rg-k8s \
  --attach-acr acrprod

# Enable image integrity (verify signatures)
az aks update --name aks-prod --resource-group rg-k8s \
  --enable-image-integrity
# Use Azure Policy to restrict image sources
# Built-in policy: "Kubernetes cluster containers should only use allowed images"
# Allowed pattern: acrprod.azurecr.io/*

Step 7: Enable Monitoring and Defender

# Enable Container Insights
az aks enable-addons --name aks-prod --resource-group rg-k8s \
  --addons monitoring --workspace-resource-id law-prod-id

# Enable Defender for Containers
az security pricing create --name Containers --tier Standard

Step 8: Configure Auto-Upgrade and Node Security

# Enable automatic node OS updates
az aks update --name aks-prod --resource-group rg-k8s \
  --node-os-upgrade-channel NodeImage

# Enable automatic cluster upgrades
az aks update --name aks-prod --resource-group rg-k8s \
  --auto-upgrade-channel stable

Security Monitoring and Threat Detection

Hardening configurations are only effective if you can detect when they are bypassed, misconfigured, or degraded. Implement comprehensive security monitoring for Azure Kubernetes Service (AKS) that covers authentication events, authorization decisions, configuration changes, and data access patterns.

Enable Microsoft Defender for Cloud and activate the relevant protection plan for this service type. Defender provides threat detection powered by Microsoft’s global threat intelligence, behavioral analytics that identify suspicious patterns, and just-in-time alerts when potential security incidents are detected. Review and triage Defender alerts daily, and integrate them into your security incident response workflow.

Configure Microsoft Sentinel to ingest logs from Azure Kubernetes Service (AKS) and apply analytics rules that detect attack indicators. Common detection scenarios include brute force authentication attempts, access from unusual geographic locations, privilege escalation through role assignment changes, and data exfiltration through unusual data transfer patterns. Create custom analytics rules for scenarios specific to your environment, such as access outside of maintenance windows or modifications by unauthorized automation accounts.

Implement Azure Policy assignments that continuously monitor your resources for configuration drift from your hardened baseline. Use the audit effect to detect non-compliant resources and the deny effect to prevent the creation of resources that do not meet your security standards. Review policy compliance reports weekly and remediate any drift immediately, as configuration changes that weaken security controls may indicate either accidental misconfiguration or deliberate tampering.

Conduct tabletop exercises that simulate security incidents involving Azure Kubernetes Service (AKS). Walk through scenarios such as compromised credentials, data breach notification, ransomware attack, and insider threat. These exercises test your team’s ability to detect, contain, and recover from security incidents using the hardening controls and monitoring capabilities you have implemented. Document lessons learned and improve your security controls based on the gaps identified during the exercise.

Step 9: Implement Secrets Management

# Enable Secrets Store CSI driver with Key Vault provider
az aks enable-addons --name aks-prod --resource-group rg-k8s \
  --addons azure-keyvault-secrets-provider \
  --enable-secret-rotation --rotation-poll-interval 2m
# SecretProviderClass for Key Vault
apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
  name: kv-secrets
  namespace: production
spec:
  provider: azure
  parameters:
    usePodIdentity: "false"
    useVMManagedIdentity: "false"
    clientID: "managed-identity-client-id"
    keyvaultName: "kv-prod"
    objects: |
      array:
        - |
          objectName: db-password
          objectType: secret
    tenantId: "tenant-id"

Step 10: Audit and Compliance

# Enable Azure Policy for AKS
az aks enable-addons --name aks-prod --resource-group rg-k8s --addons azure-policy

# Key policies to enforce:
# - No privileged containers
# - No root containers
# - Only allowed registries
# - Required resource limits
# - Required liveness probes

Defense in Depth Strategy

No single security control is sufficient. Apply a defense-in-depth strategy that layers multiple controls so that the failure of any single layer does not expose the service to attack. For Azure Kubernetes Service (AKS), this means combining network isolation, identity verification, encryption, monitoring, and incident response capabilities.

At the network layer, restrict access to only the networks that legitimately need to reach the service. Use Private Endpoints to eliminate public internet exposure entirely. Where public access is required, use IP allowlists, service tags, and Web Application Firewall (WAF) rules to limit the attack surface. Configure network security groups (NSGs) with deny-by-default rules and explicit allow rules only for required traffic flows.

At the identity layer, enforce least-privilege access using Azure RBAC with custom roles when built-in roles are too broad. Use Managed Identities for service-to-service authentication to eliminate stored credentials. Enable Conditional Access policies to require multi-factor authentication and compliant devices for administrative access.

At the data layer, enable encryption at rest using customer-managed keys (CMK) in Azure Key Vault when the default Microsoft-managed keys do not meet your compliance requirements. Enforce TLS 1.2 or higher for data in transit. Enable purge protection on any service that supports soft delete to prevent malicious or accidental data destruction.

At the monitoring layer, enable diagnostic logging and route logs to a centralized Log Analytics workspace. Configure Microsoft Sentinel analytics rules to detect suspicious access patterns, privilege escalation attempts, and data exfiltration indicators. Set up automated response playbooks that can isolate compromised resources without human intervention during off-hours.

Continuous Security Assessment

Security hardening is not a one-time activity. Azure services evolve continuously, introducing new features, deprecating old configurations, and changing default behaviors. Schedule quarterly security reviews to reassess your hardening posture against the latest Microsoft security baselines.

Use Microsoft Defender for Cloud’s Secure Score as a quantitative measure of your security posture. Track your score over time and investigate any score decreases, which may indicate configuration drift or new recommendations from updated security baselines. Set a target Secure Score and hold teams accountable for maintaining it.

Subscribe to Azure update announcements and security advisories to stay informed about changes that affect your security controls. When Microsoft introduces a new security feature or changes a default behavior, assess the impact on your environment and update your hardening configuration accordingly. Automate this assessment where possible using Azure Policy to continuously evaluate your resources against your security standards.

Conduct periodic penetration testing against your Azure environment. Azure’s penetration testing rules of engagement allow testing without prior notification to Microsoft for most services. Engage a qualified security testing firm to assess your Azure Kubernetes Service (AKS) deployment using the same techniques that real attackers would employ. The findings from these tests often reveal gaps that automated compliance scans miss.

Hardening Checklist

  1. Private cluster with local accounts disabled
  2. Azure RBAC with namespace-scoped access
  3. Network policies with default deny
  4. Pod security standards (restricted)
  5. Workload identity for pod-to-Azure authentication
  6. Secure supply chain (ACR, image integrity)
  7. Defender for Containers and Container Insights
  8. Auto-upgrade for cluster and node OS
  9. Secrets Store CSI driver with Key Vault
  10. Azure Policy enforcement

For more details, refer to the official documentation: Best practices for cluster security in AKS, Troubleshoot common issues with Azure Kubernetes Service.

Leave a Reply