Overview
Prowler is a cloud security assessment tool that checks supported cloud environments against security best practices and frameworks. It can help identify risky configurations and produce evidence for remediation, provided access is scoped appropriately.
Key features
Cloud posture checks; supported cloud providers; report outputs; CI and scheduled assessment workflows.
Install & first run
# Isolated install (recommended - Prowler pins many SDK versions)
pipx install prowler
# or
python3 -m pip install --user prowler
# Docker
docker run --rm -ti toniblyx/prowler aws
# Assess a cloud account with a read-only profile
prowler aws --profile lab-readonly
# Save machine-readable reports next to the console output
prowler aws -M csv json html -o ./reports
Azure, GCP, Kubernetes and M365 use their own subcommands (prowler azure, prowler gcp, prowler kubernetes). Docs: https://docs.prowler.com/
Real-world example
Run a read-focused assessment against your own cloud account and prioritize public exposure, identity and logging findings.
Common questions
Does Prowler need cloud credentials?
Many assessments require permissions to read configuration. Use least-privilege, review the official guide and protect generated reports.
What permissions does it need?
Read-only: SecurityAudit plus ViewOnlyAccess covers most checks. Prowler never changes your account, but it does call many read APIs.
Who pays for the API calls?
You do - checks are metadata calls, which are free in AWS, but a cross-account run still needs credentials for every account.
How do I track a fix?
Export to CSV/JSON/OCSF and diff two runs. The delta is your progress; a single report is only a snapshot.
Related tools
Trivy
Find vulnerable dependencies, OS packages, IaC misconfigurations and secrets in images, repositories and clusters. Free, open source.
Keep exploring: browse every assessment phase in the Pentest Hub.
Authorized testing only — only ever test systems you own or have explicit written permission to assess.
