Prowler SaaS and Prowler Open Source are as dynamic and adaptable as the environment they’re meant to protect. Trusted by the leaders in security.
Learn more at prowler.com
Prowler is an Open Source security tool to perform AWS, GCP and Azure security best practices assessments, audits, incident response, continuous monitoring, hardening and forensics readiness.
It contains hundreds of controls covering CIS, NIST 800, NIST CSF, CISA, RBI, FedRAMP, PCI-DSS, GDPR, HIPAA, FFIEC, SOC2, GXP, AWS Well-Architected Framework Security Pillar, AWS Foundational Technical Review (FTR), ENS (Spanish National Security Scheme) and your custom security frameworks.
| Provider | Checks | Services | Compliance Frameworks | Categories |
|---|---|---|---|---|
| AWS | 301 | 61 -> prowler aws --list-services |
26 -> prowler aws --list-compliance |
6 -> prowler aws --list-categories |
| GCP | 73 | 11 -> prowler gcp --list-services |
1 -> prowler gcp --list-compliance |
2 -> prowler gcp --list-categories |
| Azure | 37 | 4 -> prowler azure --list-services |
CIS soon | 1 -> prowler azure --list-categories |
| Kubernetes | Work In Progress | - | CIS soon | - |
The full documentation can now be found at https://docs.prowler.cloud
For Prowler v2 Documentation, please go to https://github.com/prowler-cloud/prowler/tree/2.12.1.
Prowler is available as a project in PyPI, thus can be installed using pip with Python >= 3.9, < 3.12:
pip install prowler
prowler -vMore details at https://docs.prowler.cloud
The available versions of Prowler are the following:
latest: in sync with master branch (bear in mind that it is not a stable version)<x.y.z>(release): you can find the releases here, those are stable releases.stable: this tag always point to the latest release.
The container images are available here:
Python >= 3.9, < 3.12 is required with pip and poetry:
git clone https://github.com/prowler-cloud/prowler
cd prowler
poetry shell
poetry install
python prowler.py -v
You can run Prowler from your workstation, an EC2 instance, Fargate or any other container, Codebuild, CloudShell and Cloud9.
Prowler has been written in Python using the AWS SDK (Boto3), Azure SDK and GCP API Python Client.
Since Prowler uses AWS Credentials under the hood, you can follow any authentication method as described here. Make sure you have properly configured your AWS-CLI with a valid Access Key and Region or declare AWS variables properly (or instance profile/role):
aws configureor
export AWS_ACCESS_KEY_ID="ASXXXXXXX"
export AWS_SECRET_ACCESS_KEY="XXXXXXXXX"
export AWS_SESSION_TOKEN="XXXXXXXXX"Those credentials must be associated to a user or role with proper permissions to do all checks. To make sure, add the following AWS managed policies to the user or role being used:
arn:aws:iam::aws:policy/SecurityAuditarn:aws:iam::aws:policy/job-function/ViewOnlyAccess
Moreover, some read-only additional permissions are needed for several checks, make sure you attach also the custom policy prowler-additions-policy.json to the role you are using.
If you want Prowler to send findings to AWS Security Hub, make sure you also attach the custom policy prowler-security-hub.json.
Prowler for Azure supports the following authentication types:
- Service principal authentication by environment variables (Enterprise Application)
- Current az cli credentials stored
- Interactive browser authentication
- Managed identity authentication
To allow Prowler assume the service principal identity to start the scan, it is needed to configure the following environment variables:
export AZURE_CLIENT_ID="XXXXXXXXX"
export AZURE_TENANT_ID="XXXXXXXXX"
export AZURE_CLIENT_SECRET="XXXXXXX"If you try to execute Prowler with the --sp-env-auth flag and those variables are empty or not exported, the execution is going to fail.
The other three cases do not need additional configuration, --az-cli-auth and --managed-identity-auth are automated options, --browser-auth needs the user to authenticate using the default browser to start the scan. Also --browser-auth needs the tenant id to be specified with --tenant-id.
To use each one, you need to pass the proper flag to the execution. Prowler for Azure handles two types of permission scopes, which are:
- Azure Active Directory permissions: Used to retrieve metadata from the identity assumed by Prowler and future AAD checks (not mandatory to have access to execute the tool)
- Subscription scope permissions: Required to launch the checks against your resources, mandatory to launch the tool.
Azure Active Directory (AAD) permissions required by the tool are the following:
Directory.Read.AllPolicy.Read.All
Regarding the subscription scope, Prowler by default scans all the subscriptions that is able to list, so it is required to add the following RBAC builtin roles per subscription to the entity that is going to be assumed by the tool:
Security ReaderReader
Prowler will follow the same credentials search as Google authentication libraries:
- GOOGLE_APPLICATION_CREDENTIALS environment variable
- User credentials set up by using the Google Cloud CLI
- The attached service account, returned by the metadata server
Those credentials must be associated to a user or service account with proper permissions to do all checks. To make sure, add the Viewer role to the member associated with the credentials.
By default,
prowlerwill scan all accessible GCP Projects, use flag--project-idsto specify the projects to be scanned.
To run prowler, you will need to specify the provider (e.g aws or azure):
prowler <provider>
Running the
prowlercommand without options will use your environment variable credentials.
By default, prowler will generate a CSV, a JSON and a HTML report, however you can generate JSON-ASFF (only for AWS Security Hub) report with -M or --output-modes:
prowler <provider> -M csv json json-asff htmlThe html report will be located in the output directory as the other files and it will look like:
You can use -l/--list-checks or --list-services to list all available checks or services within the provider.
prowler <provider> --list-checks
prowler <provider> --list-servicesFor executing specific checks or services you can use options -c/--checks or -s/--services:
prowler aws --checks s3_bucket_public_access
prowler aws --services s3 ec2Also, checks and services can be excluded with options -e/--excluded-checks or --excluded-services:
prowler aws --excluded-checks s3_bucket_public_access
prowler aws --excluded-services s3 ec2You can always use -h/--help to access to the usage information and all the possible options:
prowler -hSeveral Prowler's checks have user configurable variables that can be modified in a common configuration file. This file can be found in the following path:
prowler/config/config.yaml
Use a custom AWS profile with -p/--profile and/or AWS regions which you want to audit with -f/--filter-region:
prowler aws --profile custom-profile -f us-east-1 eu-south-2By default,
prowlerwill scan all AWS regions.
With Azure you need to specify which auth method is going to be used:
prowler azure [--sp-env-auth, --az-cli-auth, --browser-auth, --managed-identity-auth]By default,
prowlerwill scan all Azure subscriptions.
Optionally, you can provide the location of an application credential JSON file with the following argument:
prowler gcp --credentials-file pathBy default,
prowlerwill scan all accessible GCP Projects, use flag--project-idsto specify the projects to be scanned.
Prowler is licensed as Apache License 2.0 as specified in each file. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0