Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A landing zone is a pre-built, governed cloud foundation—accounts, identity, networking, logging, and guardrails—so that every new workload starts from a secure baseline.

What Is a Cloud Landing Zone?
A landing zone is the foundation a cloud estate is built on: the account or subscription structure, the identity model, the network topology, the logging pipeline, and the guardrails that apply before anyone deploys anything. Its purpose is to make the secure configuration the default one, so that a team shipping a new service inherits segmentation, audit trails, and policy without having to ask for them.
Cloud estates that grow organically end up as a collection of accounts nobody owns, with inconsistent identity, logs scattered across regions, and no reliable way to answer simple questions—how many production environments are there, which of them hold personal data, who can reach them. Retrofitting governance onto that is expensive and politically painful. A landing zone front-loads the decisions while there is still only one account to change.
Each provider ships an opinionated starting point: AWS Control Tower with its multi-account structure, the Microsoft Cloud Adoption Framework landing zone accelerators for Azure, and Google Cloud’s foundation blueprint. You do not have to adopt them wholesale, but their account and policy structures encode a lot of accumulated experience.
Three choices are worth real debate before the first workload lands. Address space allocation determines whether you can connect to a partner, acquire a company, or peer two environments later; overlapping ranges are the most common and most tedious regret. Account granularity sets your blast radius—one account per workload per environment gives clean isolation and a larger operational surface, while shared accounts are simpler and leak permissions between teams. Region strategy affects latency, cost, and the data residency position you will have to defend to a regulator.
Everything else is adjustable. Policies can be tightened, logging extended, and tagging enforced retrospectively with enough effort. These three are not.
A landing zone defined by console clicks decays within months. Define it in Terraform, Bicep, CloudFormation, or the provider’s own accelerator modules, keep it in version control with code review, and run the same policy scanning against it that you expect from application teams—see our entry on infrastructure as code security. Vend new accounts through an automated pipeline rather than a ticket, because a manual process guarantees that the tenth account differs from the first.
The failure mode of a strict landing zone is shadow cloud: teams opening personal accounts on a corporate card because the governed path takes six weeks. Avoid it by publishing a small catalogue of approved patterns, making account provisioning fast and self-service, providing exemption routes with owners and expiry dates, and measuring how long it takes a new team to go from request to first deployment. If that number is measured in weeks, the guardrails will be routed around no matter how well written they are.
Finally, treat the foundation as a product with a backlog and an owner, not a project that finished. Providers add services continuously, and a guardrail set written two years ago has gaps around everything released since.
At Privia Security, we review foundation design and test the guardrails that depend on it through our infrastructure and architecture review services.
You need the principles, scaled down. A two-person startup does not need twelve accounts, but it does need separation between production and everything else, central logging it cannot accidentally delete, federated identity with multi-factor authentication, and a tagging standard. Those cost little at the start and are expensive to retrofit once dozens of resources already exist.
Control Tower, the Azure landing zone accelerators, and Google’s foundation blueprint give you a tested structure quickly and are a sensible default for most organisations. Building your own makes sense when you have unusual regulatory requirements, an existing estate that does not fit the model, or strong engineering capacity. Many teams start with the accelerator and extend it with their own modules.
A common pattern is one per workload per environment, plus dedicated accounts for logging, security tooling, shared networking, identity, and sandbox. That gives clean blast-radius separation and simple cost attribution at the price of more automation. Fewer, larger accounts are easier to operate but make permission boundaries harder to enforce and incidents harder to contain.
Yes, though it takes longer than starting fresh. The usual approach is to build the new structure alongside the existing one, enrol existing accounts into the organisation so central guardrails and logging apply immediately, then migrate workloads account by account as they are next worked on. Address space overlaps and hard-coded assumptions usually determine how painful the migration is.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.