What it means
CSPM checks cloud resource configurations against expected security conditions. Typical questions include whether storage is publicly accessible, administrative network access is too broad, or important logging is enabled. Checks usually depend on cloud APIs and the permissions granted to the assessment tool. A posture finding describes an observed configuration and its interpretation; it is not automatically evidence of exploitation or complete proof of effective access. The organization must decide which policies matter, who fixes findings, and how exceptions and unsupported resources are handled.
See the idea / Cloud
A live fix can be undone by the next deployment.
Compare fixing the resource and its source with fixing the live resource alone.
Synthetic ResearchStore C170 has public object reading enabled. Sam’s rule requires private O170; W170 has its own read grant. A read-only posture collector captures the setting. Sam authorizes Nora to restrict C170. Compare changing the live setting plus deployment source D170 with changing only the live setting, then rerun D170 and independently test both readers. No real cloud account changes.
01 / 04
Inspect
The read-only collector retains C170’s public-read setting. Sam’s private-object rule and W170’s legitimate grant are known; no correction has run.
More about this step
The selected C170 snapshot, original O170 and deployment definition D170 are retained independently. D170 would currently recreate public reading. Sam owns the private-object decision and Nora may apply that exact correction. Assessment permission does not permit resource mutation. This exercise assumes no other network or policy layer changes the selected endpoint’s result.
Step through at your own pace.
Keep in mindThis is one SQL/HTTP-modeled object-read policy, not an AWS/Azure policy engine. Trusted collector/owner/operator identities and an otherwise reachable endpoint are assumed. Other policy layers, regions and resources are unassessed. A configuration finding is not proof of past theft; a refused fresh read does not recall earlier copies. Only the selected deployment replay is tested.
Read the visual, step by step
Live + source
- Inspect. The read-only collector retains C170’s public-read setting. Sam’s private-object rule and W170’s legitimate grant are known; no correction has run. The selected C170 snapshot, original O170 and deployment definition D170 are retained independently. D170 would currently recreate public reading. Sam owns the private-object decision and Nora may apply that exact correction. Assessment permission does not permit resource mutation. This exercise assumes no other network or policy layer changes the selected endpoint’s result.
- Assess + test. The rule comparison records F170. Separate fresh probes return O170 to an anonymous reader and permitted W170, without changing the object. The selected batch compares the collected public-read flag with Sam’s private rule, records F170 and independently checks effective object reads. Both readers return 200 with the same synthetic O170. A configuration comparison alone would not prove those responses. F170 is a scoped policy violation, not a demonstrated prior theft or a complete cloud assessment. The read-only collector cannot repair it.
- Correct. Nora applies Sam’s approved private setting to C170 and D170. No deployment replay or fresh access test has completed yet. The primary batch changes the live public-read gate and the selected deployment source to private. The comparison changes the live gate only and retains D170’s old public setting. Both branches preserve W170’s read grant, original O170, old snapshot and F170. Mutation authority is separate from the collector’s read access. A successful setting update is not the later deployment or access result.
- Redeploy + test. After D170 is replayed, fresh checks refuse anonymous reading and still return O170 to W170. The selected rule passes; the originals remain. The selected deployment is actually replayed before the new setting is read and independent HTTP object probes run. With corrected D170, C170 stays private: anonymous 403 without the object, W170 200 with O170. With the old D170, public reading returns: anonymous 200 and W170 200. The original snapshot and F170 remain historical records, not rewritten passing evidence. Other deployments, resources and prior disclosure stay unassessed.
Live change only
- Inspect. The read-only collector retains C170’s public-read setting. Sam’s private-object rule and W170’s legitimate grant are known; no correction has run. The selected C170 snapshot, original O170 and deployment definition D170 are retained independently. D170 would currently recreate public reading. Sam owns the private-object decision and Nora may apply that exact correction. Assessment permission does not permit resource mutation. This exercise assumes no other network or policy layer changes the selected endpoint’s result.
- Assess + test. The rule comparison records F170. Separate fresh probes return O170 to an anonymous reader and permitted W170, without changing the object. The selected batch compares the collected public-read flag with Sam’s private rule, records F170 and independently checks effective object reads. Both readers return 200 with the same synthetic O170. A configuration comparison alone would not prove those responses. F170 is a scoped policy violation, not a demonstrated prior theft or a complete cloud assessment. The read-only collector cannot repair it.
- Correct. Nora restricts live C170, but D170 still specifies public reading. No deployment replay or fresh access test has completed yet. The primary batch changes the live public-read gate and the selected deployment source to private. The comparison changes the live gate only and retains D170’s old public setting. Both branches preserve W170’s read grant, original O170, old snapshot and F170. Mutation authority is separate from the collector’s read access. A successful setting update is not the later deployment or access result.
- Redeploy + test. Replaying old D170 restores public reading. Fresh anonymous and W170 probes both return O170; the live-only correction did not survive deployment. The selected deployment is actually replayed before the new setting is read and independent HTTP object probes run. With corrected D170, C170 stays private: anonymous 403 without the object, W170 200 with O170. With the old D170, public reading returns: anonymous 200 and W170 200. The original snapshot and F170 remain historical records, not rewritten passing evidence. Other deployments, resources and prior disclosure stay unassessed.
This is one SQL/HTTP-modeled object-read policy, not an AWS/Azure policy engine. Trusted collector/owner/operator identities and an otherwise reachable endpoint are assumed. Other policy layers, regions and resources are unassessed. A configuration finding is not proof of past theft; a refused fresh read does not recall earlier copies. Only the selected deployment replay is tested.
Flow references: Microsoft: cloud posture and distinct CNAPP capabilities · NIST SP 800-210: cloud data-owner access control
AN ILLUSTRATIVE SCENARIO
The live setting and its deployment source
C170 exposes synthetic O170 despite Sam’s private-object rule. The read-only collector records F170, and fresh reads confirm public access. Nora restricts the live setting in both paths, but only one corrects D170 too. Replaying D170 preserves privacy or restores public reading; separate probes check anonymous access and W170’s legitimate read. Originals remain and other cloud resources are unassessed.
Put it to work
- Connect the intended cloud accounts and regions using the least assessment access required. Record unsupported services and any permissions that limit what the tool can see.
- Choose relevant policies and assign resource owners. Review findings in context, including inherited policies, identities, network controls, and approved public services.
- Fix the deployment source as well as the current resource when possible. Manage exceptions with reasons and review dates, then rerun the check and validate the effective configuration.
How to check your work
Use a safe test resource with a known configuration problem. Confirm detection, ownership, correction, and re-evaluation. Check the actual access outcome and ensure the original deployment process does not recreate the same problem.
Connect the ideas
- CNAPP
A bundled category covering cloud posture, workload, and related application-risk features; boundaries vary by vendor.
- Shared responsibility
The split of security duties between a cloud or SaaS provider and the customer, which varies by service.
- Exposure
Whether and how a vulnerability or service can actually be reached in this environment.
- Least privilege
Granting each identity only the actions, objects, and time window required for the current job.