The Raptoric Journal/Application & Cloud
Application & CloudJune 2, 2026 · 9 min read

Cloud security assessment: what it covers, and why IAM comes first

Cloud breaches rarely start with a clever exploit. They start with a permission nobody walked back. Here is what a cloud security assessment covers and where the real risk hides.
Written by
R
Raptoric Application & Cloud
Share
LinkedInX / TwitterCopy link

Moving to the cloud changes where your risk lives. The firewall and the patch cycle matter less. Identity, configuration, and the blast radius of a single over-broad role matter more. A cloud security assessment reviews how your environment is actually built and finds the paths an attacker would take through it.

The shared responsibility line

Your cloud provider secures the infrastructure. You secure what you put on it: identities, configurations, data, and access. Most cloud incidents happen on your side of that line, in choices that looked reasonable at the time and were never revisited.

What the assessment covers

  • Identity and access management. Roles, policies, trust relationships, and the privilege paths between them. This is where most cloud breaches actually happen.
  • Network. Exposed services, security groups, and segmentation, or the lack of it.
  • Storage. Public buckets, weak access controls, and unencrypted data.
  • Logging and monitoring. Whether you would even see an attacker, and whether the evidence survives.
  • Workloads and containers. Image hygiene, Kubernetes RBAC, network policies, and secrets handling.
  • Configuration drift. The settings that were hardened once and quietly loosened since.

Why IAM comes first

Identity is the new perimeter. Every project adds a role. Every incident adds a temporary grant that becomes permanent. Over time the environment accumulates a web of permissions no single person understands, and any one of them can be the path from a minor foothold to full control. When we assess a cloud environment, we trace those privilege paths: if an attacker lands here, where can they get? We go deeper on this in the quietest risk in your cloud is IAM.

Assessment versus CSPM

A cloud security posture management tool watches configuration continuously and flags drift. That is valuable and belongs in your program. But it reports misconfigurations against a checklist. It does not chain them into an attack path or judge which ones actually matter for your business. The tool gives you continuous coverage. The assessment gives you the judgment of someone who has broken into environments like yours.

What you get

  • A map of privilege paths and the real attack routes through your environment.
  • Risk-ranked findings across IAM, network, storage, logging, and workloads.
  • Remediation guidance specific to AWS, Azure, or GCP.
  • Evidence suitable for auditors and regulators.
Closing an over-broad permission is unglamorous, and it is the highest-leverage work in cloud security.

See application and cloud security for how we assess cloud environments, or book a scoping call.

Want this tested on your own systems?
A senior engineer will scope it with you on a 30-minute call.
Book a scoping call