LESSON 9 · RUNNING COVERAGE · 2 MIN READ
Keeping cloud security coverage complete as the estate grows
Short answer
Coverage decays. Teams open new accounts, business units adopt another cloud, and acquisitions bring estates nobody mapped. Connect at the organization level where you can, reconcile the platform's inventory with your own list every month, and make connection to the platform a step in creating any new environment.
How gaps appear
Most coverage gaps are not product failures. They are accounts that were never connected: a new AWS account created outside the main organization, an Azure subscription in a different tenant, a Google Cloud project owned by a data team, an Oracle tenancy that came with an acquisition.
Connect at the top level
Where a cloud provider offers an organization or management level, connect the platform there, so that new accounts under it are picked up automatically. Check in a trial whether each platform does this for each cloud you run, and how quickly new accounts appear.
Reconcile every month
Once a month, compare three lists:
- The accounts, subscriptions and projects your cloud providers' billing shows.
- The environments the security platform reports as connected.
- Your own estate map.
Anything on the first list but not the second is a gap. Anything on the second but not the third is a surprise worth asking about.
Watch vendor changes too
Coverage can also change on the vendor side. Microsoft states that from 27 October 2026 the free Foundational CSPM tier of Defender for Cloud becomes opt-in for new Azure subscriptions; existing subscriptions and AWS and Google Cloud connectors are not affected, according to its release notes. A team that relied on it being switched on by default now needs a step in its subscription setup. Our briefings track changes like this.
Make connection part of creation
The durable fix is procedural: no new cloud environment goes live until it is connected to the security platform. Put the step in your account-creation template or infrastructure-as-code module, and make the platform's read-only role part of the baseline.
When the estate changes shape
If a new cloud enters the estate, check whether your platform names it. On the pages we reviewed, Orca names 7 of our eight environments, Wiz 4, Upwind 4 and Defender for Cloud 4. If yours does not name the new cloud, that is the moment to revisit the decision with the rankings and your updated map.
Sources
Source: Microsoft Learn: Defender for Cloud release notes · Read 27 Sep 2026
Source: Microsoft Learn: Defender for Cloud CSPM · Read 27 Sep 2026