What is CSPM (cloud security posture management)?
CSPM continuously checks cloud configurations against security standards to find and fix misconfigurations and compliance gaps.
Definition
CSPM
Also called Cloud security posture management, Cloud posture management
CSPM (cloud security posture management) is the practice and tooling for continuously assessing cloud infrastructure configurations against security standards and best practices, to find and remediate misconfigurations and compliance violations.
How it works
Palo Alto Networks describes CSPM as the practice of controlling public cloud infrastructure risk, with tools that automate detection and remediation of misconfigurations across cloud resources. Microsoft's Defender for Cloud documentation describes it as continuous visibility into the security state of cloud assets and workloads across Azure, AWS, and GCP, with recommendations to reduce misconfigurations and risk.
A CSPM tool connects to cloud provider APIs, inventories resources, and evaluates their configurations against rules: industry benchmarks, regulatory frameworks, or custom policies. Findings include things like storage buckets open to the internet, databases without encryption, security groups allowing administrative ports from anywhere, or logging turned off. Each finding comes with remediation guidance, and many tools add a score so teams can track posture over time. Microsoft's foundational CSPM, for instance, evaluates resources against the Microsoft Cloud Security Benchmark and rolls the results into a secure score, where a higher score means lower identified risk. More advanced offerings add attack path analysis and risk prioritization to show which misconfigurations combine into a real route to sensitive data.
Rules are concrete and named. In AWS Security Hub CSPM, for example, control [S3.8] checks that S3 general purpose buckets block public access, and [CloudTrail.1] checks for at least one multi-Region trail that records read and write management events. Defaults also shift what a scan finds: since April 2023, AWS enables S3 Block Public Access and disables ACLs on every new bucket, so a public bucket created after that date means someone turned the protection off.
The main trade-off is noise. A first scan of a large estate can return a very long list of findings, most of them low risk. Teams get value by starting with a small set of high-impact rules (public exposure, missing encryption on sensitive data, disabled audit logging, overly broad network access), assigning findings to owning teams, and adding preventive guardrails so the same misconfiguration can't be deployed again.
Example
A developer creates an S3 bucket for a demo, turns off Block Public Access, and makes it public to share a file. Within the next scan, CSPM fails [S3.8] for the bucket and notes it contains objects tagged as customer data. The finding goes to the owning team with a one-line fix, and the security team adds a preventive policy (an organization-level Block Public Access setting or a service control policy) so new buckets can't be made public without an exception.
A week later, CloudTrail shows a burst of GetObject calls on that bucket from an unfamiliar IP address. Whoever triages that alert needs the earlier finding: the bucket was public for some window, so the question is whether those reads happened inside it.
Why it matters for a SOC
Many cloud incidents start with a misconfiguration rather than an exploit, so posture findings are early warnings. For the SOC, CSPM is also context: when an alert fires on a cloud resource, knowing it was already exposed to the internet or over-permissioned changes its priority. CSPM is usually one component of a broader CNAPP, alongside workload protection and entitlement management, and its findings are most useful when they flow into the same SIEM and triage process as runtime alerts. On Cotool, for example, detections are Python that can query logs or call the tools where the data lives, and every agent verdict shows the evidence and reasoning behind it, so a reviewer can see whether the posture finding was part of the call.
Related terms
- CNAPPA CNAPP (cloud-native application protection platform) is a security platform that combines cloud posture management, identity and entitlement management, and workload protection to secure cloud-native applications from development through runtime.
- CIEMCIEM (cloud infrastructure entitlement management) is the practice and tooling for analyzing and managing the identities, permissions, and entitlements in cloud environments, to find excessive access and enforce least privilege.
- Zero trustZero trust is a security model that grants no implicit trust to users or devices based on their network location or ownership, and instead authenticates and authorizes every access request to each resource based on dynamic policy.
- SIEMA SIEM (security information and event management) system collects security logs from across an organization, stores them in one searchable place, and runs detection rules over them so a security team can find, investigate, and respond to threats.
- Threat modelingThreat modeling is the practice of analyzing a representation of a system to identify what could go wrong with its security and privacy, and deciding which countermeasures to apply.
Sources
- What is Cloud Security Posture Management (CSPM) - Microsoft Defender for Cloud · accessed November 16, 2026
- What Is CSPM? | Palo Alto Networks · accessed November 16, 2026
- Security Hub CSPM controls for Amazon S3 - AWS Security Hub · accessed November 16, 2026
- Security Hub CSPM controls for AWS CloudTrail - AWS Security Hub · accessed November 16, 2026
- Heads-Up: Amazon S3 Security Changes Are Coming in April of 2023 - AWS News Blog · accessed November 16, 2026
- AI Detection Engineering with Python Detections - Cotool · accessed November 16, 2026
- AI SOC Without the Black Box | Cotool · accessed November 16, 2026
