Module SDD-04 — Prowler

Prowler

The canonical open-source multi-cloud CSPM: provider-agnostic check engine, attack-path correlation, three-tier layering, GitHub Action integration.

60
minutes
8
artifacts
3
sub-sections
The world's most widely used open-source cloud security platform. Prowler reads configuration across AWS, Azure, GCP, Kubernetes, GitHub, and Microsoft 365, runs 600+ controls per cloud, normalizes findings to OCSF, and integrates into CI as a creation-time guardrail. The defensive complement to the offensive harnesses — and a study in what happens when you score a non-agent tool on the agent rubric.
Key Claims
Load-Bearing Claims

Prowler's provider-agnostic core plus per-cloud adapters is why it covers seven surfaces. Adding a cloud is 'write an adapter,' not 'rewrite the engine.' This extensibility seam is the architectural decision behind Prowler's breadth.

Read-only by default is the primary safety property. A compromised or misconfigured Prowler cannot destroy cloud resources — the worst case is a noisy report. This is what makes Prowler safe to run continuously in production.

OCSF normalization is the portability decision. Findings in a standard schema flow into any downstream tool (SIEM, ticketing, Security Hub). This is what makes Prowler the CSPM standard, not just a scanner.

Prowler is not an agent loop. It detects and reports; it does not remediate, diff, or reason over graphs. Scoring it on the agent rubric forces you to see the boundary — and the opportunity: wrapping Prowler in an agent loop turns it from a detector into a defensive harness.

After This Module
01
Map Prowler's architecture: provider-agnostic core, per-cloud adapters, check engine, findings normalization, three-tier output.
02
Distinguish Prowler's CSPM model from the offensive harnesses (SDD-01-03) and from point-in-time auditing (SDD-05).
03
Explain attack-path correlation vs full graph traversal, and where Prowler stops.
04
Score Prowler on the 12-module rubric (35/45, 3 modules n/a) and explain why the n/a modules reveal the tool/harness boundary.
05
Identify the three layers (remediation loop, cross-scan diffing, full graph traversal) a harness builder adds on top of Prowler.
Artifacts