Our new goMISP service offers fully managed, cloud-based and secure MISP instances – ready to use from day one.
TL;DR
Azure landing zones (formerly Enterprise-Scale), the core of Microsoft's Cloud Adoption Framework, are often deployed and maintained through Azure DevOps. In Microsoft's recommended setup, the deployment identity holds Owner rights over the entire landing zone and can change every policy and permission. The landing zone's security controls do not cover Azure DevOps. Your landing zone is therefore only as secure as your Azure DevOps.
Many enterprises have built their Azure environment on Microsoft's Cloud Adoption Framework: management groups, hundreds of Azure Policy assignments, Microsoft Defender for Cloud in every subscription, a hub network behind Azure Firewall. On paper, an Azure landing zone looks like a fortress.
In our previous article Securing Azure DevOps: The Top 5 Misconfigurations We Find in Real Environments we described what we find in Azure DevOps during penetration tests. There we did not mention that many of those organizations had implemented an Azure landing zone, deployed and maintained from that same Azure DevOps.
Your landing zone enforces the rules. Your pipeline writes them.
In this blog we explain:
What the Cloud Adoption Framework and Azure landing zones are.
Which security controls Microsoft builds into a landing zone.
Why the deployment pipeline is the blind spot, and what you should check.
The Cloud Adoption Framework (CAF) is Microsoft's guidance for adopting Azure, organized into seven phases from Strategy to Manage. Its outcome is "an Azure landing zone and operational standards that support all Azure workloads" (Cloud Adoption Framework overview).
An Azure landing zone is "a proven and flexible architecture for governing, securing, and scaling a multi-subscription Azure environment" (What is an Azure landing zone?). You may know it under its original name Enterprise-Scale (GitHub: Azure/Enterprise-Scale). A central platform landing zone provides governance, security and shared services, while application teams work in workload landing zones within its guardrails.
The heart of every landing zone is a management group hierarchy (Management groups). Policies and permissions assigned at the top are inherited by every subscription below:
The CAF design area Platform automation and DevOps defines how the landing zone itself is operated: "through extreme automation and Infrastructure as Code", using "Azure DevOps Services or GitHub" (Platform automation and DevOps).
A landing zone ships with a strong security baseline:
Identity: Entra ID with phishing-resistant MFA, Conditional Access and just-in-time administration via Privileged Identity Management (Landing zone identity and access management).
Policy-driven governance: Azure Policy denies insecure configurations and automatically deploys Defender for Cloud and logging. The Microsoft cloud security benchmark is assigned at the top of the hierarchy (ALZ Policy Assignments).
Security operations and network: Defender for Cloud, Microsoft Sentinel, central logging, Azure Firewall and private endpoints (Security design area).
All of these controls protect Azure resources. Azure Policy "evaluates resources and actions in Azure" (Azure Policy overview). Your Azure DevOps organization, its pipelines, service connections and branch policies are not Azure resources. Not a single landing zone policy looks at them.
Microsoft recommends deploying the landing zone with the Azure Landing Zones IaC Accelerator. In Azure DevOps, it creates repositories, pipelines and a service connection backed by a managed identity (IaC accelerator). The permissions of the IaC Accelerator, as documented by Microsoft:
"Apply UAMI: Owner at the intermediate root management group scope." (Permissions FAQ)
That is Owner over every platform subscription, every workload subscription, every policy assignment and every policy exemption.
The accelerator does set up approvals, branch policies and a separate read-only identity for planning in Azure DevOps. But a pipeline run executes whatever its definition says, with every credential it is allowed to use. In our assessments, these safeguards are regularly weakened or bypassed. The landing zone is exactly as secure as the weakest path to that pipeline. In an assessment we start by checking the Azure DevOps configurations:
Which pipelines may use the Owner service connection, and who can create or edit them?
Are approvals enforced on the apply environment, and can people approve their own changes?
Are the main branch and the pipeline templates protected by branch policies with required reviewers?
Who is Project Collection Administrator, and who controls the build agents?
How misconfigurations in these areas can lead to a compromise of the Owner of your landing zone is described in our article Securing Azure DevOps: The Top 5 Misconfigurations We Find in Real Environments.
If you take away only three things from this article:
Your landing zone has a root account, and it is a pipeline. In CAF, the deployment identity typically holds Owner over the entire landing zone.
Your Cloud Adoption Framework is only as secure as your Azure DevOps. Since the most critical identities reside in Azure DevOps, they must be managed with the highest security standards.
Microsoft documents all the controls you need. They just have to be switched on and verified.
That verification is exactly what we do. In a security review of your Azure landing zone we assess the management group hierarchy, policies, RBAC and PIM, and the Azure DevOps or GitHub platform that deploys it. We map the findings against the Cloud Adoption Framework and the Microsoft cloud security benchmark. Where it is in scope, we demonstrate the actual attack path: from a single developer account to Owner of your landing zone.
Interested? Let's have an informal first conversation. Tell us a bit about your environment and we will walk you through how such a review works, what it covers, and what you would get out of it. No obligations.
📧 contact@wallsec.de