Cloud Scope Notes

CSPM buyer notes · US scope

CSPM deployment models and operating workflow

Deployment and sensor choices change data flow, onboarding speed, and operational work. Reviewed records below distinguish API-agentless, runtime-sensor, and self-hosted options.

What needs to run before you trust a finding?

A connector can be enabled while a resource is still outside the scan. These conditions explain what your team must check.

AWS Security Hub CSPM

Recorder setup
For AWS standards, standalone CSPM needs AWS Config recording in each enabled account and Region. With both Security Hub and CSPM enabled, AWS manages a service-linked recorder. SourceExternal-cloud standards use their connector and do not require this AWS Config setup. The bundle and standalone paths differ.
How fresh a finding is
Daily AWS Config recording can delay change-triggered findings until the 24-hour recording period ends. Disabling required recording can leave warning or retained findings that do not reflect current resources. SourceCorrect cloud coverage depends on recording the required resource types, not simply enabling the product. Recording can also incur Config charges.

Microsoft Defender for Cloud

Agentless scan cadence
Agentless machine scanning runs every 24 hours on a fixed schedule. Stopped or deallocated machines are not scanned during that cycle. SourceThis is disk scanning, not continuous runtime detection. Newly enabled or reconfigured environments may need the next cycle.
Cloud charges beyond the product
Agentless scanning adds no extra Defender charge within the stated plans, but AWS snapshot storage can add AWS charges. SourceSnapshots carry CreatedBy=Microsoft Defender for Cloud for cost tracking. Charges persist for retained snapshots.
Where snapshot analysis runs
Microsoft says snapshot analysis stays in the VM’s cloud region, and only metadata results leave the isolated scanning environment. SourceVendor architecture statement; this is not an independent security assessment or a blanket data-residency conclusion.

Upwind

Runtime-powered CNAPP/CSPM bridging build-time and runtime Layer 3/4/7 context across hybrid cloud.

Documentation introduction only.

Vendor source · Full claim and scope

Palo Alto Networks Prisma Cloud

available in two deployment models: SaaS (Prisma Cloud Enterprise Edition) and Self-Hosted (Prisma Cloud Compute Edition)

FAQ-named deployment choices.

Vendor source · Full claim and scope

Prowler (remediation workflow)

Triage lifecycle with auto-muting, Jira/Slack/email alerts, and Lighthouse AI / Autonomous Fixer (Prowler Cloud).

Open Source provides remediation guidance and mutelist only.

Vendor source · Full claim and scope
Ask before comparing: which edition is in the quote, where components run, what data leaves your environment, and whether controls behave identically across editions.