TL;DR: Cloud security still hinges on identity, logging, encryption and governance, with NeuralTrust highlighting AI agents as a fifth layer of risk through scoped identities, key protection, tool control and auditability. Workloads need bounded authority, or ownership gaps can turn routine access into broader misuse.
Editorial analysis by NHI Mgmt Group, based on content published by NeuralTrust: “Cloud Security Best Practices: 25 Tips”.
By the numbers:
- The Cloud Controls Matrix v4.1 holds 197 control objectives in 17 domains.
- The CSA AI Controls Matrix adds 243 control objectives across 18 domains for AI workloads.
Key questions
Q: Why do short-term credentials reduce risk compared with manually managed cloud access keys?
A: Short-term credentials reduce risk because they limit how long an access token can be abused and remove much of the manual handling that leads to leakage.
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Q: How should teams implement cloud security without over-trusting the provider?
A: Start with the service model and draw ownership lines for identities, configurations, data, logging, and recovery.
Practitioner guidance
- Map shared responsibility per service Document who owns patching, configuration, logging, access control, and recovery for each cloud service model you use.
- Move all workloads to short-lived credentials Replace static API keys and shared service accounts with federated identities and temporary credentials that expire after the task ends.
- Scope every AI agent to a dedicated identity Assign one identity per agent, remove shared service accounts, and restrict each agent to the smallest set of tools and data it needs.
Bottom line: Cloud security programmes still fail most often at ownership boundaries, not only at configuration errors.
Glossary terms: Shared Responsibility Model, STS Temporary Credentials, Scoped identity, Downstream Authorization
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Cloud security is now an identity governance problem, not just a posture problem. The guide’s strongest point is that data, configurations, and identities remain customer-owned even when infrastructure is provider-managed. That means cloud governance must extend beyond CSPM-style misconfiguration checks into access modelling, entitlement review, and identity lifecycle control. For practitioners, the discipline is to govern who or what can act in the cloud, not just whether the cloud is configured correctly.
A few things that frame the scale:
- Valid account abuse was responsible for 35% of cloud-related incidents, according to CrowdStrike's 2025 Global Threat Report.
A question worth separating out:
Q: What should security teams do when cloud workloads start acting like agents?
A: Treat them as delegated identities with bounded authority, not as passive software. That means separate identities, per-action authorization, controlled egress, and audit logs that record what was called, when, and under which approval path.
👉 Read our full editorial: Cloud security best practices in 2026 centre on identity and control