L14. VM & Container Security
Course outlineLesson 14 of 18
Review JIT access, disk encryption lifecycle, registry identity and image trust, then apply AKS admission and network controls.
Course context: AZ-500 retired on August 31, 2026. Use these Azure security concepts for operational practice and continue with the current SC-500 course for certification preparation.
Just-in-Time VM Access
Defender for Servers Plan 2 provides JIT VM access. It restricts selected management ports through NSGs and Azure Firewall, then checks Azure RBAC before temporarily opening the requested ports for the authorized source and duration. This is authorization, not a separate human approval workflow.
Review existing rules: pre-existing rules for selected ports can take precedence over JIT deny rules. JIT does not create a network path or require every VM to have a public IP. Test effective rules and connectivity from the intended administrative network.
VM Disk Encryption
| Option | Protection | Key management |
|---|---|---|
| Server-side encryption | Persisted OS and data disks; always enabled | Microsoft-managed keys or CMK through a disk encryption set |
| Encryption at host | Extends protection to temporary disks and caches, with encrypted flow to storage | Disk/cache CMK options; temporary disks use platform keys |
| Azure Disk Encryption | Guest OS BitLocker or DM-Crypt encryption | Key Vault integration |
Container Registry and Image Trust
- Keep the ACR admin account disabled; use scoped workload identities for image access.
- Use Defender for Containers vulnerability assessment for supported registry and running images, with its required registry and cluster access configured.
- Docker Content Trust is a legacy path: it cannot be newly enabled from May 31, 2026, and is removed on March 31, 2028. Follow Microsoft's transition guidance to Notary Project tooling for new signing designs.
- Image signing verifies provenance and integrity, not freedom from vulnerabilities. Enforce deployment policy separately.
AKS Controls
Use Microsoft Entra authentication with Kubernetes RBAC or Azure RBAC for Kubernetes authorization, disable local accounts where supported, and maintain node and cluster updates. Network policies constrain pod traffic; admission policies can restrict allowed image registries. A registry allowlist alone does not verify signatures or image safety.
References
- JIT access and rule precedence
- Disk encryption and ADE retirement
- Host encryption key scope
- ACR authentication
- Docker Content Trust transition
- Container vulnerability assessment
- AKS cluster security
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓JIT VM access requires Defender for Servers Plan 2 and Azure RBAC authorization for the request
- ✓JIT uses NSGs and Azure Firewall; pre-existing management-port rules can take precedence
- ✓SSE protects persisted disks; host encryption extends coverage; ADE is guest-based and retires September 15, 2028
- ✓Keep ACR admin disabled, use scoped identities, and configure vulnerability assessment and image admission separately
- ✓Docker Content Trust cannot be newly enabled from May 31, 2026; migrate before removal March 31, 2028
- ✓AKS combines authentication, authorization, admission controls, network policy and supported updates
1. With JIT configured and no pre-existing higher-priority allow rules, what happens to selected inbound management ports?
2. What is the purpose of Azure Disk Encryption on a VM?
3. Which AKS security feature restricts which container images can be deployed to the cluster?