Cloud Security

Defending the keys to the kingdom in the cloud

← All InsightsBy Dr. Derek A. Smith6 min read

Moving to the cloud didn’t just change where your servers live. It handed your organization an explosion of privileged identities — IAM roles, access keys, service principals, managed identities, cross-account trust — and every one of them is a potential path to the crown jewels.

In AWS, Azure, and GCP, access is identity. A single over-broad role or a forgotten access key can be the difference between a contained incident and a full compromise. And the cloud’s convenience works against you: it is trivial to grant a wildcard permission “just to get it working,” and almost no one goes back to trim it.

The failure mode

Cloud breaches rarely look like hacking. They look like logging in with credentials that had far more power than anyone realized. The recurring pattern: standing privileged access that’s always on, roles scoped with wildcards instead of specific actions, permissions granted and never used, and long-lived keys that outlive the projects that created them. Studies of cloud entitlements consistently find that the vast majority of granted permissions are never actually used — which means most of your risk is pure excess.

Attackers don’t hack cloud environments. They log into them — with access you forgot you granted.

Least privilege and just-in-time, concretely

  • Right-size to real usage. Analyze what each identity actually uses and trim the rest. Cloud Infrastructure Entitlement Management (CIEM) tooling exists precisely for this.
  • Kill standing admin. No one and no service should hold always-on privileged access by default.
  • Grant elevation just-in-time. Time-box privileged access, broker it through a PAM solution, and revoke automatically.
  • Replace long-lived keys with role-based, short-lived credentials, and enforce MFA on every privileged human path.
  • Rotate secrets and log everything, then monitor for anomalous API calls the way you’d watch a privileged user.
Do it before the breach
  • Find and delete unused permissions and orphaned access keys.
  • Remove standing admin; move to just-in-time elevation.
  • Put every privileged secret behind a vault with rotation.

The economics are simple: right-sizing privileged access is inexpensive when you do it on your schedule and brutally expensive when an incident forces it. Defend the keys to the kingdom before someone else picks them up.

Dr. Derek A. Smith is founder of DAS Advisory Group and author of The Defensible AI Program. He advises federal agencies and enterprises on governing and securing AI.

Want this applied to your organization?

A 30-minute conversation on where you are and what governing your AI actually takes.

Book a Consultation

Get new briefs in your inbox

Practical AI governance and security notes, sent when there's something worth reading. No spam.