In a data centre, attackers had to get through the network first. In the cloud, anyone with valid credentials can reach the management APIs from anywhere. Identity is the new perimeter, and most serious cloud incidents involve a compromised or misused identity. Here are seven mistakes we see repeatedly, and how to fix them.

1. Long-lived access keys

Static access keys for users and applications, created years ago, stored in code repositories, CI systems, laptops and config files. They leak, and they don't expire.

Fix: use short-lived credentials everywhere you can: workload identities and instance roles for compute, workload identity federation for CI/CD and external systems, and single sign-on with temporary sessions for people. Scan repositories for secrets, and rotate or delete any static keys that remain.

2. Over-privileged roles

Admin rights granted "to get it working", wildcard permissions such as *:*, and roles that accumulate permissions over time and never lose them.

Fix: start from least privilege. Use the provider's access analysis tools to find unused permissions and right-size roles based on actual activity. Separate duties: people who deploy shouldn't also manage IAM. For when roles alone are not enough, see access control models compared.

3. Root or global admin accounts in daily use

The all-powerful account that created the cloud tenancy, still used for routine work, sometimes without MFA.

Fix: lock the root or global admin account away: strong MFA (preferably a hardware key), no access keys, break-glass procedures, and alerts on any use. Day-to-day admin happens through named, federated roles.

4. Missing or weak MFA

Users, especially administrators, without multi-factor authentication, or with SMS codes that can be phished or SIM-swapped.

Fix: enforce MFA through your identity provider for all users, and phishing-resistant MFA (FIDO2 security keys or passkeys) for administrators and other high-risk roles. Block legacy authentication protocols that bypass MFA.

5. Wildcard trust policies

Cross-account or federated roles whose trust policies allow any principal, any account, or any repository to assume them. For example, a CI federation trust that accepts tokens from any branch of any repository.

Fix: pin trust policies to specific accounts, specific identity providers and specific conditions (such as repository and branch claims, and external IDs for third parties). Review trust policies as carefully as permission policies.

6. Orphaned and forgotten identities

Accounts of people who left, service accounts for retired applications, test users with production access, and vendor access that outlived the contract.

Fix: connect cloud access to your joiner–mover–leaver process through the identity provider. Run regular access reviews. Disable identities unused for 90 days. Keep an inventory of non-human identities with owners, a fast-growing category with AI agents. See securing AI agents.

7. No visibility into identity activity

Audit logging not enabled in every region and account, logs not centralised, nobody alerted when a new admin is created or a key is used from an unusual location.

Fix: enable audit logs organisation-wide, send them to a central, tamper-protected store, and alert on high-risk events: root login, IAM policy changes, new access keys, disabled logging, unusual geographic access and mass data reads. Keep logs long enough to investigate.

Guardrails that prevent the mistakes

  • Organisation-level policies (service control policies, organisation policies) that block dangerous actions everywhere: disabling logging, creating public storage, leaving approved regions.
  • Infrastructure as code with policy checks in the pipeline, so mistakes are caught before deployment.
  • Posture management tools that continuously check identity configuration against benchmarks.

Learn more

Identity, access management and cloud security architecture are covered in the free CCSP and CISSP tracks. See also the shared responsibility model.

Written and reviewed by the DigiTrust Asia editorial team. How we research, review and correct articles.

Prepare for cloud security

Free CCSP lessons and practice questions.

Create a free account