Topic starter
20/08/2026 5:52 pm
TL;DR: Cloud security in 2026 is shifting toward identity, data, and workload governance rather than perimeter defense, with Sentra stressing shared responsibility, least privilege, CSPM, encryption, and continuous monitoring as cloud and multi-cloud estates expand. The core issue is not just misconfiguration but whether access, configuration, and data controls can keep pace with dynamic cloud operations.
Editorial analysis by NHI Mgmt Group, based on content published by Sentra: “Cloud Security 101: Essential Tips and Best Practices”.
By the numbers:
- Sentra says cloud storage costs can typically be reduced by approximately 20% by eliminating shadow and ROT data.
Key questions
Q: What breaks when cloud security is still built around a fixed network perimeter?
A: A fixed perimeter breaks down when workloads, data, and applications move across hybrid and multi-cloud environments.
Q: Why do over-privileged cloud entitlements increase breach impact?
A: They increase breach impact because a stolen credential or compromised integration can inherit far more access than the underlying task requires.
Q: What are the signs that cloud posture management is not enough on its own?
A: If CSPM findings keep surfacing while access reviews, role design, and workload permissions remain broad, the programme is only seeing half the problem.
Practitioner guidance
- Implement identity-centred cloud governance Map every cloud workload, human user, and service account to an explicit owner, scope, and review cadence so access decisions are traceable.
- Bind CSPM findings to entitlement review Require every misconfiguration finding to be checked against the identities that can exploit it, then remediate configuration and access together.
- Classify and trace sensitive data in cloud Maintain live data classification and lineage so teams can see where sensitive data sits, how it moves, and which identities can reach it.
Bottom line: Cloud security now fails most often at the point where identity scope, configuration drift, and data access intersect.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
20/08/2026 6:31 pm
Cloud security has become an identity governance problem because access, not perimeter location, now defines exposure. When workloads, users, and APIs all share the same cloud fabric, the decisive control is whether permissions are narrowly scoped and continuously reviewed. That changes cloud security from static hardening to ongoing authorisation governance, and practitioners should treat privilege drift as a first-order cloud risk.
A few things that frame the scale:
- 73% of vaults are misconfigured, leading to unauthorised access and exposure of sensitive data, according to the Ultimate Guide to NHIs.
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
A question worth separating out:
Q: How should security teams govern AI data access without slowing the business down?
A: Security teams should define policy around data context, not around static folders or file names. The practical model is continuous discovery, high-confidence classification, and automated enforcement that limits risky access while preserving approved AI use cases. If controls require manual review for every exception, they will fail at AI scale.
👉 Read our full editorial: Cloud security in 2026 is increasingly an identity problem