Study guide
9.3 Container & Azure Kubernetes Service (AKS) Security
Microsoft Azure Security Technologies AZ-500
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Azure Security Architecture Foundation
1.1 Azure Security Engineer Role & Exam Logistics 1.2 Microsoft Cybersecurity Reference Architecture & Zero Trust Principles
2 Chapter 2: Secure Identity and Access - Authentication, MFA & PIM
2.1 Microsoft Entra ID Security, Users, and Groups 2.2 Authentication Methods, MFA, and Conditional Access Policy Design 2.3 Microsoft Entra Privileged Identity Management (PIM)
3 Chapter 3: Secure Identity and Access - RBAC & Workload Identity
3.1 Azure RBAC, Custom Roles, and Governance 3.2 Workload Identities and Managed Identities 3.3 External Identities and Cross-Tenant Collaboration
4 Chapter 4: Microsoft Entra Application Access & Consent Governance
4.1 Enterprise Applications, OAuth Permission Grants & Consent Governance 4.2 App Registrations, Permission Scopes & Service Principal Credentials
5 Chapter 5: Secure Azure Networking - Boundary & Perimeter Protection
5.1 Virtual Network Security & Micro-segmentation 5.2 Azure Firewall and Firewall Manager 5.3 Web Application Firewall (WAF) & Azure Front Door
6 Chapter 6: Secure Azure Networking - Private Access & Monitoring
6.1 Private Connectivity with Private Endpoints & Private Link 6.2 Azure Bastion & Remote Management Security 6.3 Network Perimeter Protection & Flow Monitoring
7 Chapter 7: Network Architecture, Routing & Hybrid Connectivity
7.1 Azure Virtual Network Manager, Network Groups & User-Defined Routes 7.2 VPN Gateway, ExpressRoute Encryption & Virtual WAN Secured Hub 7.3 Network Integration for App Service, Functions, App Service Environment & SQL Managed Instance
8 Chapter 8: Public and Edge Access Protection
8.1 Azure Application Gateway Security, TLS Policy & Mutual Authentication 8.2 Azure Front Door, CDN Caching & TLS for App Service and API Management
9 Chapter 9: Compute, Container & Registry Security
9.1 Azure Virtual Machine Hardening & Host Security 9.2 Azure Key Vault Deep Dive & Secrets Lifecycle 9.3 Container & Azure Kubernetes Service (AKS) Security 9.4 Azure Container Instances, Container Apps & Registry Access Control
10 Chapter 10: Storage Security, Access Methods & Data Protection
10.1 Storage Account Security & Access Controls 10.2 Selecting and Configuring Access to Azure Files 10.3 Selecting and Configuring Access to Azure Blob Storage 10.4 Storage Data Protection: Soft Delete, Versioning, Point-in-Time Restore & Backup
11 Chapter 11: Data Platform & Database Security
11.1 Azure SQL Database Security & Always Encrypted 11.2 Database Auditing & Vulnerability Assessment 11.3 Data Discovery, Classification, & Microsoft Purview Integration
12 Chapter 12: Cloud Governance, Key Lifecycle & Asset Protection
12.1 Azure Policy for Security Governance: Definitions, Initiatives, Effects & Remediation 12.2 Key Vault Backup, Recovery & Automated Key Rotation 12.3 Implementing Security Controls to Protect Backups 12.4 Security Controls for Asset Management: Locks, Tags, Resource Graph & Azure Arc
13 Chapter 13: Microsoft Defender for Cloud - Posture & Workload Protection
13.1 Microsoft Defender for Cloud & Secure Score 13.2 Defender Cloud Workload Protection (CWP) Plans 13.3 Defender for Cloud Inventory, Compliance Standards & Custom Standards 13.4 Connecting AWS and GCP Environments to Microsoft Defender for Cloud
14 Chapter 14: External Attack Surface & Vulnerability Management
14.1 Microsoft Defender External Attack Surface Management (EASM) 14.2 Agentless Scanning & Microsoft Defender Vulnerability Management for Azure VMs 14.3 Defender for Cloud DevOps Security: GitHub, Azure DevOps & GitLab
15 Chapter 15: Security Monitoring, Microsoft Sentinel & Automation
15.1 Azure Monitor Data Collection Rules & Network Security Event Monitoring 15.2 Microsoft Sentinel Data Connectors, Content Hub & Normalization 15.3 Microsoft Sentinel Workspace & KQL Threat Hunting 15.4 Sentinel Incident Management & SOAR Automation
9.3 Container & Azure Kubernetes Service (AKS) Security
Key Takeaways Explain This Topic AI
Private AKS Clusters isolate the API server control plane by providing a private IP address via Azure Private Link, restricting API management traffic to peered VNets or VPN/ExpressRoute endpoints.
Microsoft Entra ID integration with Kubernetes RBAC enables centralized cloud identity governance, mapping Entra ID security groups to Kubernetes ClusterRoleBindings and eliminating local cluster admin accounts.
Pod Security Standards (Privileged, Baseline, Restricted) enforced via Azure Policy for AKS prevent pods from running as root, mounting host paths, or escalating privileges at admission control.
The Azure Key Vault Provider for Secrets Store CSI Driver mounts Key Vault objects directly into pod file systems using Entra Workload Identity, eliminating the exposure of plaintext credentials in etcd.
Azure Container Registry (ACR) security encompasses Private Endpoints, Dedicated Data Endpoints, Content Trust image signing (Notary/ORAS), and Defender for Containers vulnerability scanning.
Last updated: August 2026
6.3 Container & Azure Kubernetes Service (AKS) Security
Containerized application deployments in Azure Kubernetes Service (AKS) demand defense-in-depth across multiple abstraction layers: the Kubernetes API control plane, node infrastructure, container network communication, workload identity, and image registry pipelines. Securing AKS involves protecting both cluster-level infrastructure and in-cluster workload runtimes.
AKS Cluster Security & Control Plane Isolation
Securing an Azure Kubernetes Service deployment requires isolating management endpoints and managing administrative identity boundaries.
Public vs. Private AKS Clusters
Public AKS Clusters: The Kubernetes API server control plane is assigned a public FQDN ( *.hcp.<region>.azmk8s.io ). Although protected by TLS and Kubernetes RBAC, the API server endpoint remains accessible over the public internet.
Private AKS Clusters: The Kubernetes API server is assigned a private IP address within the cluster's virtual network via Azure Private Link. All API management network traffic is isolated from the public internet. Administrative access requires routing through a peered virtual network, an Azure VPN Gateway, ExpressRoute, or an internal Azure Bastion host. +-----------------------------------------------------------------------------------+
- | PRIVATE AKS CLUSTER TOPOLOGY |
- +-----------------------------------------------------------------------------------+
- | Peered Admin VNet / VPN ---> [Private Link] ---> Private API Server (10.0.0.5) |
- | | |
- | v |
- | Internal VNet Subnet (10.240.0.0/16) ---------> AKS Worker Nodes & Pods |
- +-----------------------------------------------------------------------------------+
- Microsoft Entra ID Integration & Kubernetes RBAC
Integrating Microsoft Entra ID with AKS replaces static, shared cluster administrator credentials ( kubeconfig local admin tokens) with enterprise identity governance:
Entra Group Binding: Kubernetes RoleBinding and ClusterRoleBinding manifests map Kubernetes roles directly to Microsoft Entra ID Object IDs (security groups).
Disabling Local Accounts: Administrators can explicitly disable local cluster admin accounts using --disable-local-accounts . This mandates Entra ID authentication for every kubectl request.
Conditional Access Integration: API server logins enforce Entra ID Conditional Access policies, including phishing-resistant MFA and device compliance checks.
Pod Network Policies: Azure CNI Policy vs. Calico
By default, all pods within an AKS cluster can communicate with all other pods across namespaces. Network policies establish micro-segmentation boundaries:
Azure CNI Network Policy: Microsoft's native network policy implementation. Integrates directly with Azure Virtual Network controls; rules are processed efficiently at the Linux kernel layer via iptables or eBPF.
Calico Network Policy: A widely adopted open-source network policy engine. Supports advanced features including global network policies, application-layer HTTP rules, and cross-platform policy enforcement across both Linux and Windows node pools.
Pod Security Standards & Azure Policy for AKS
Preventing compromised container workloads from escaping host namespaces or compromising worker nodes requires strict runtime privilege restriction.
Kubernetes Pod Security Standards Tiers
Kubernetes defines three progressive security levels for pod workloads:
Privileged: Unrestricted permissions. Intended only for system-level infrastructure pods (e.g., CNI plugins, storage drivers).
Baseline: Default minimal restriction. Prevents known privilege escalations (e.g., host network sharing, host PID namespace access).
Restricted: Highly hardened configuration. Enforces strict best practices:
- Disallows root execution ( runAsNonRoot: true )
- Restricts volume types (disallows hostPath mounts)
- Drops all Linux capabilities except explicitly allowed ones ( drop: ["ALL"] )
- Forces read-only root filesystems
- Azure Policy Add-on for AKS
The Azure Policy Add-on for AKS integrates Open Policy Agent (OPA) Gatekeeper with the Kubernetes API server admission controller. Security administrators assign built-in Azure Policy definitions that evaluate pod manifests before creation, automatically auditing or denying non-compliant workloads.
Secrets Store CSI Driver Integration with Key Vault
Storing sensitive credentials as native Kubernetes Secrets presents operational security risks: native secrets are merely base64-encoded strings stored in etcd , vulnerable to unauthorized access if etcd or cluster RBAC is compromised. +-----------------------------------------------------------------------------------+
- | SECRETS STORE CSI DRIVER WITH WORKLOAD IDENTITY |
- +-----------------------------------------------------------------------------------+
- | Application Pod (Pod Spec Mounts Volume) |
- | | |
- | v |
- | Secrets Store CSI Driver <---> Entra Workload Identity (Federated Credential) |
- | | |
- | v (Private Endpoint) |
- | Azure Key Vault (Secret retrieved directly into memory volume mount) |
- +-----------------------------------------------------------------------------------+
- Secrets Store CSI Driver Architecture
The Secrets Store CSI Driver allows AKS to mount secrets, keys, and certificates stored in Azure Key Vault directly as file system volume mounts inside application pods:
No Stored Credentials: Uses Microsoft Entra Workload Identity to establish a federated identity relationship between the Kubernetes service account and a Managed Identity authorized in Key Vault.
In-Memory Volume Mounts: Secret payloads exist only as temporary in-memory volume files ( tmpfs ) attached to the running container lifecycle.
Auto-Rotation: Automatically synchronizes updated secret versions from Key Vault into the mounted pod volume without requiring pod restarts.
Azure Container Registry (ACR) Security
Azure Container Registry (ACR) acts as the central supply-chain repository for container images. Securing ACR requires enforcing network isolation, image integrity, and vulnerability scanning.
ACR Network Hardening & Dedicated Data Endpoints
Disable Public Access: Set publicNetworkAccess = "Disabled" on the ACR instance.
Private Endpoints: Route registry login ( <registry-name>.azurecr.io ) over Azure Private Link.
Dedicated Data Endpoints: Container images consist of manifest files and underlying data storage blobs. Enabling Dedicated Data Endpoints creates regional data endpoints ( <registry-name>.<region>.data.azurecr.io ), allowing network firewalls to restrict traffic strictly to container storage blobs without allowing wide regional storage ranges.
Content Trust & Image Signing
Content Trust enables digital signature verification for container images using Docker Notary or ORAS (OCI Registry as Storage):
Developers or CI/CD pipelines sign container images using a private key during docker push .
AKS policy enforcement engines verify signatures prior to image pull, preventing unsigned or tampered images from executing in cluster environments.
Vulnerability Scanning with Defender for Containers
Microsoft Defender for Containers performs automated, agentless scanning of container images pushed to ACR:
On-Push Scanning: Scans container OS packages and language libraries (Python, Node, Go) for known CVEs immediately upon upload.
Continuous Rescanning: Continuously rescans published images when new CVE databases are released to identify newly discovered zero-day vulnerabilities.