|
1 | | -In this module, you learned how to plan and implement advanced security measures for Azure compute resources, including enabling secure remote access using Azure Bastion and just-in-time (JIT) VM access, configuring network isolation for Azure Kubernetes Service (AKS), securing and monitoring AKS clusters, configuring authentication and security monitoring for container instances and apps, managing access to Azure Container Registry (ACR), implementing disk encryption strategies such as Azure Disk Encryption (ADE) and confidential disk encryption, and providing recommendations for securing Azure API Management. |
| 1 | +In this module, you learned how to plan and implement advanced security measures for Azure compute resources to protect against vulnerabilities and evolving security threats. |
| 2 | + |
| 3 | +## Key learnings |
| 4 | + |
| 5 | +You explored comprehensive security strategies across multiple Azure compute services: |
| 6 | + |
| 7 | +### Secure remote access |
| 8 | +- **Azure Bastion** provides secure RDP/SSH access without exposing virtual machines to the public internet, with four SKU tiers: |
| 9 | + - **Developer SKU**: Cost-effective option for dev/test scenarios (two concurrent connections) |
| 10 | + - **Basic SKU**: Standard secure remote access (no native client support) |
| 11 | + - **Standard SKU**: Enhanced features including native client support and shareable links |
| 12 | + - **Premium SKU**: Advanced capabilities including session recording, private-only deployment, and custom port support |
| 13 | +- **Just-in-time (JIT) VM access** reduces attack surfaces by providing time-limited access to virtual machines |
| 14 | + |
| 15 | +### Azure Kubernetes Service (AKS) security |
| 16 | +- **Workload identity** with OIDC federation provides secure authentication to Azure resources (replaces deprecated pod-managed identity) |
| 17 | +- **Network isolation** through network policies controls pod-to-pod communication |
| 18 | +- **Pod Security Standards** enforce security policies at the pod level |
| 19 | +- **AKS Automatic** offers simplified, production-ready cluster configuration |
| 20 | +- **Azure Linux 3** should be used as Azure Linux 2.0 support ends November 30, 2025 |
| 21 | + |
| 22 | +### Container security and monitoring |
| 23 | +- **Microsoft Defender for Containers** provides comprehensive threat protection across five core domains: |
| 24 | + - Cloud security posture management |
| 25 | + - Vulnerability assessment powered by Microsoft Defender Vulnerability Management (MDVM) |
| 26 | + - Run-time threat detection |
| 27 | + - Kubernetes environment hardening |
| 28 | + - Software supply chain protection |
| 29 | +- **Container insights** (a feature of Azure Monitor) provides performance and health monitoring for container workloads |
| 30 | +- **Gated deployment** (GA) prevents vulnerable images from being deployed to production |
| 31 | +- **Runtime container scanning** (GA) provides continuous vulnerability assessment |
| 32 | + |
| 33 | +### Container registry security |
| 34 | +- **Azure Container Registry (ACR)** supports seven built-in RBAC roles for granular access control |
| 35 | +- **Authentication methods** include Microsoft Entra identities, repository-scoped permissions, and admin accounts |
| 36 | +- **Integration with Microsoft Entra ID** enables centralized identity management |
| 37 | + |
| 38 | +### Data protection |
| 39 | +- **Azure Disk Encryption (ADE)** uses BitLocker (Windows) and dm-crypt (Linux) to encrypt VM disks |
| 40 | +- **Encryption at host** provides end-to-end encryption for VM data |
| 41 | +- **Confidential disk encryption** protects sensitive workloads with hardware-based security |
| 42 | +- **Azure Key Vault** serves as centralized key and certificate management |
| 43 | +- **Envelope encryption** with DEK/KEK hierarchy provides layered data protection |
| 44 | + |
| 45 | +### API security |
| 46 | +- **Azure API Management** security baseline aligns with Microsoft Cloud Security Benchmark (v2 preview available) |
| 47 | +- **Virtual Network integration** enables internal or external network configurations |
| 48 | +- **Private endpoints** provide secure access without public exposure |
| 49 | +- **Microsoft Entra ID integration** enables OAuth 2.0 authentication for APIs |
| 50 | +- **Managed identities** simplify secure access to Azure resources like Key Vault |
| 51 | + |
| 52 | +## Best practices applied |
| 53 | + |
| 54 | +Throughout this module, you learned to apply security best practices: |
| 55 | + |
| 56 | +- Use **workload identity** instead of deprecated pod-managed identity for AKS authentication |
| 57 | +- Enable **Microsoft Entra ID** authentication over local authentication methods wherever possible |
| 58 | +- Implement **least privilege access** using Azure RBAC for granular permission control |
| 59 | +- Use **managed identities** to avoid storing credentials in code or configuration |
| 60 | +- Enable **encryption at rest** and **encryption in transit** for all sensitive data |
| 61 | +- Deploy **private endpoints** to keep traffic off the public internet |
| 62 | +- Monitor with **Microsoft Defender for Containers** and **Container insights** for comprehensive visibility |
| 63 | +- Apply **network policies** to enforce micro-segmentation in AKS clusters |
| 64 | +- Store **secrets and keys in Azure Key Vault** rather than in application code |
| 65 | +- Use **Azure Policy** to enforce security configurations across resources |
| 66 | + |
| 67 | +## Next steps |
| 68 | + |
| 69 | +To continue strengthening your Azure security expertise: |
| 70 | + |
| 71 | +- Explore [Microsoft Defender for Cloud](/azure/defender-for-cloud/) for unified security management |
| 72 | +- Review [Azure security baselines](/security/benchmark/azure/security-baselines-overview) for service-specific guidance |
| 73 | +- Implement [Microsoft Cloud Security Benchmark](/security/benchmark/azure/overview) controls in your environment |
| 74 | +- Learn about [Azure confidential computing](/azure/confidential-computing/) for protecting data in use |
| 75 | +- Configure [Azure Policy](/azure/governance/policy/) to enforce organizational security standards |
0 commit comments