Topic starter
11/11/2026 6:04 pm
TL;DR: Multi-cloud security works only when visibility, runtime, data and enforcement layers each do a different job, according to Native. Policy state has to be checked continuously, or drift quickly turns a one-time control into a false sense of coverage.
Editorial analysis by NHI Mgmt Group, based on content published by Native: “The Best Multi-Cloud Security Tools for 2026 and Where Each One Fits”.
Key questions
Q: How can identity data improve cloud segmentation decisions?
A: Identity data improves segmentation by showing which users, service accounts and workloads actually need to talk to each other, so network and application segments can be built around real access relationships rather than IP ranges alone.
Q: What is the difference between visibility and enforceable access control in cloud security?
A: Visibility shows what is happening, but enforceable access control changes what is allowed to happen.
Practitioner guidance
- Define the control layer you are missing first Separate visibility gaps from enforcement gaps before selecting a platform, then choose the tool class that closes the specific control failure you have identified.
- Map identity context into cloud policy design Track which service accounts, workloads and human operators can reach each cloud resource, then use that mapping to shape perimeter and segmentation controls.
- Check whether policy still holds after drift Revalidate cloud policy state after account changes, resource moves and configuration updates so a one-time decision does not become stale in production.
Bottom line: Multi-cloud security breaks into distinct layers, and visibility alone does not stop risky actions from recurring.
Glossary terms: Multicloud Security, CNAPP, DSPM, Service Account
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:06 pm
Multi-cloud enforcement is the control layer that converts discovery into actual risk reduction. Visibility tools can rank exposure, but they do not by themselves change which actions a cloud will allow. The decisive question is whether the policy layer in each provider can hold the same intent after configuration drift, account sprawl and cross-cloud exceptions. Practitioners should treat enforcement as the point where security design becomes real.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- By 2029, 40% of enterprises that successfully implement zero trust within cloud service provider environments will rely on the advanced visibility and control capabilities offered by CNAPP solutions.
A question worth separating out:
Q: How can identity data improve cloud segmentation decisions?
A: Identity data improves segmentation by showing which users, service accounts and workloads actually need to talk to each other, so network and application segments can be built around real access relationships rather than IP ranges alone. Practitioners use entitlement data, workload identity, communication graphs and least-privilege rules to reduce lateral movement and overbroad trust.
👉 Read our full editorial: Multi-cloud security needs enforcement to keep policy consistent