Cloud security posture management (CSPM) explained

Line drawing of cloud-shaped platforms holding servers and storage, a searchlight resting on one open box in blue

Most cloud breaches start with a setting, not a sophisticated exploit. What CSPM does, what it does not do, which tools you may already have, and how to turn a long list of findings into fewer real risks.

In short

Cloud security posture management (CSPM) is the continuous, automated checking of your cloud accounts against security best practices and standards, to find misconfigurations such as public storage, open ports, missing encryption or over-privileged roles. It gives you an inventory, a score and prioritised recommendations. It does not fix anything on its own: value comes from owners, priorities and guardrails in code.

Cloud platforms make it easy to create resources and just as easy to expose them. A storage bucket made public for a test, a database with a firewall rule open to the internet, an old access key with administrator rights: none requires a skilled attacker to exploit. This explainer is written by Devies, a Gothenburg-based product and engineering consultancy, for CTOs, platform leads and IT managers responsible for cloud security (in Swedish often molnsäkerhet) in Azure, AWS or Google Cloud. It explains what CSPM is, how it differs from related tools, and how to make it useful.

What is CSPM?

CSPM is a category of security tooling that continuously inventories cloud resources and compares their configuration with a set of security rules, reporting deviations as findings with recommended fixes.

Key definitions:

  • Security posture is the overall security state of your environment at a given moment: what exists, how it is configured and how exposed it is.
  • A misconfiguration is a setting that weakens security compared with a defined baseline, such as unencrypted storage or logging switched off.
  • A benchmark is a published set of configuration recommendations, for example the CIS Benchmarks for each major cloud provider.
  • A secure score is a summary metric that many CSPM tools calculate from how many recommendations you meet, weighted by importance.

Typical checks include publicly accessible storage and databases, network rules open to the whole internet, disabled logging, missing encryption, identities with excessive permissions, accounts without MFA, unused credentials and resources in regions you never meant to use.

How does CSPM differ from related tools?

Posture management looks at configuration of the cloud control plane, while neighbouring tools look at workloads, code or identities, and the acronyms are easy to mix up.

Tool

What it examines

Example finding

CSPM

What it examines

Cloud account and resource configuration

Example finding

Storage account allows anonymous public read

CWPP (cloud workload protection)

What it examines

Running virtual machines, containers and serverless functions

Example finding

Malware or a vulnerable package on a VM

CIEM (cloud infrastructure entitlement management)

What it examines

Permissions of human and machine identities

Example finding

A service principal with owner rights it never uses

DSPM (data security posture management)

What it examines

Where sensitive data sits and who can reach it

Example finding

Personal data in an unprotected bucket

IaC scanning

What it examines

Infrastructure-as-code templates before deployment

Example finding

Template creates a database without encryption

CNAPP (cloud-native application protection platform)

What it examines

A bundle of the above in one platform

Example finding

Combined attack path across them

In practice the boundaries blur, because vendors bundle features. The useful question is not which acronym you buy, but whether you cover configuration, workloads, identities and code before deployment.

Which CSPM tools do you already have?

Most organisations already have basic posture management built into their cloud platform, so the first step is usually switching on and tuning what exists rather than buying something new.

Microsoft Defender for Cloud offers Foundational CSPM, which assesses Azure, AWS and Google Cloud resources against the Microsoft Cloud Security Benchmark and calculates a secure score, and a paid Defender CSPM plan that adds attack path analysis, risk prioritisation, agentless scanning and regulatory compliance assessments. AWS Security Hub CSPM runs continuous checks against standards such as the AWS Foundational Security Best Practices, the CIS AWS Foundations Benchmark, PCI DSS and NIST, and collects findings from other AWS security services. Google Cloud has its own built-in equivalent. Third-party platforms add multi-cloud views and broader features.

Choose a third-party tool when you run seriously in several clouds, need one view for many teams, or want features your provider's plan lacks. Otherwise, start with the native option.

How do you make CSPM findings useful?

Posture findings become useful when they have owners, are prioritised by real exposure and are prevented from recurring, because a tool that reports thousands of issues to nobody changes nothing.

Loop of five stations from a radar to a team, a priority list, a code page and a barrier, the barrier in blue

A practical approach:

  1. Enable it everywhere. All subscriptions or accounts, all regions, including the ones nobody uses, since attackers like those.
  2. Pick one baseline. Use the provider's benchmark or CIS as the default, and document exceptions with a reason and an expiry date.
  3. Assign owners by tag or account. Every finding should route to the team that owns the resource, not to a central inbox.
  4. Prioritise by exposure. Fix internet-facing resources, sensitive data and privileged identities first. A missing tag is not urgent; a public database is.
  5. Fix in code, not in the console. Correct the infrastructure-as-code template, otherwise the next deployment brings the problem back.
  6. Add guardrails. Use policies that block or flag risky settings at deployment time, such as Azure Policy, AWS Service Control Policies or IaC scanning in the pipeline.
  7. Track a small set of metrics. Critical findings older than an agreed number of days, share of resources deployed through code, and trend in secure score per team.

This is where posture management meets everyday engineering: posture checks belong in the same pipeline as tests and deployments; see DevOps for product teams.

Where does CSPM fit in a wider cloud security strategy?

CSPM is the visibility layer of cloud security: it tells you where configuration deviates, while identity, network design and workload protection determine how much damage a deviation can cause.

Two links matter most. First, the cloud provider's shared responsibility model makes configuration the customer's job, so posture management covers precisely the part you cannot hand over. Second, many of the highest-risk findings are about identity: owners without MFA, unused keys and excessive roles. Fixing them is part of identity and access management, and continuous verification of identity, device and configuration is the core of zero trust.

For organisations covered by NIS2, the Swedish Cybersecurity Act (cybersäkerhetslagen) requires risk-management measures including policies for assessing the effectiveness of security measures; as of October 2026 posture reports are a practical source of that evidence, though no law requires such a tool.

Devies

Want a second opinion?

Devies, a Gothenburg-based product and engineering consultancy, works on questions like this with Nordic product and IT teams. Tell us where you are and we will suggest a sensible first step.

Talk to Devies

Frequently asked questions

What does a CSPM tool actually do?

A CSPM tool connects to your cloud accounts through read-only APIs, builds an inventory of resources and continuously checks their configuration against security rules and benchmarks. It reports misconfigurations such as public storage, open network rules, missing encryption or excessive permissions, scores your posture and recommends fixes. Some tools can also remediate automatically or block risky settings, but most value comes from routing findings to the owning teams.

What is the difference between CSPM and CNAPP?

CSPM focuses on configuration of cloud accounts and resources. CNAPP, a cloud-native application protection platform, is a broader bundle that combines CSPM with workload protection, entitlement management, infrastructure-as-code scanning and sometimes data security in one platform. Many products sold as CNAPP grew out of CSPM. Choose based on which of these capabilities you actually need and already have.

Is the built-in CSPM in Azure or AWS enough?

For many mid-sized companies running mainly in one cloud, the built-in options are a good start: Microsoft Defender for Cloud offers foundational CSPM, and AWS offers Security Hub CSPM with standards such as the CIS benchmark. Consider a paid tier or third-party platform when you run across several clouds, need attack path analysis and risk prioritisation, or must give many teams a unified view.

How often should we review CSPM findings?

Critical findings on internet-facing resources should alert the owning team immediately and be fixed within days. Review the remaining findings in a regular rhythm, for example weekly in each team and monthly at management level with trend metrics. The goal is to reduce how often findings appear, by fixing templates and adding guardrails, rather than to clear the same list repeatedly.

Sources

Here’s more

Join Our Newsletter

We handle your data according to our privacy policy.

Shopping Cart

We use cookies

We use cookies to improve your experience on this website. You may choose which types of cookies to allow and change your preferences at any time. Disabling cookies may impact your experience on this website. You can learn more by viewing our Cookie Policy.

Check out

Contact Form text

We will contact you text

We handle your data according to our privacy policy.