AWS Security Hub Integration¶
Prowler supports natively and as official integration sending findings to AWS Security Hub. This integration allows Prowler to import its findings to AWS Security Hub.
With Security Hub, you now have a single place that aggregates, organizes, and prioritizes your security alerts, or findings, from multiple AWS services, such as Amazon GuardDuty, Amazon Inspector, Amazon Macie, AWS Identity and Access Management (IAM) Access Analyzer, and AWS Firewall Manager, as well as from AWS Partner solutions and from Prowler for free.
Before sending findings to Prowler, you will need to perform next steps:
- Since Security Hub is a region based service, enable it in the region or regions you require. Use the AWS Management Console or using the AWS CLI with this command if you have enough permissions:
aws securityhub enable-security-hub --region <region>.
- Enable Prowler as partner integration integration. Use the AWS Management Console or using the AWS CLI with this command if you have enough permissions:
aws securityhub enable-import-findings-for-product --region <region> --product-arn arn:aws:securityhub:<region>::product/prowler/prowler(change region also inside the ARN).
- Using the AWS Management Console:
- Allow Prowler to import its findings to AWS Security Hub by adding the policy below to the role or user running Prowler:
Once it is enabled, it is as simple as running the command below (for all regions):
or for only one filtered region like eu-west-1:
Note 1: It is recommended to send only fails to Security Hub and that is possible adding
-qto the command.
Note 2: Since Prowler perform checks to all regions by default you may need to filter by region when running Security Hub integration, as shown in the example above. Remember to enable Security Hub in the region or regions you need by calling
aws securityhub enable-security-hub --region <region>and run Prowler with the option
-f <region>(if no region is used it will try to push findings in all regions hubs). Prowler will send findings to the Security Hub on the region where the scanned resource is located.
Note 3: To have updated findings in Security Hub you have to run Prowler periodically. Once a day or every certain amount of hours.
Once you run findings for first time you will be able to see Prowler findings in Findings section:
Send findings to Security Hub assuming an IAM Role¶
When you are auditing a multi-account AWS environment, you can send findings to a Security Hub of another account by assuming an IAM role from that account using the
-R flag in the Prowler command:
Remember that the used role needs to have permissions to send findings to Security Hub. To get more information about the permissions required, please refer to the following IAM policy prowler-security-hub.json
Send only failed findings to Security Hub¶
When using Security Hub it is recommended to send only the failed findings generated. To follow that recommendation you could add the
-q flag to the Prowler command:
Skip sending updates of findings to Security Hub¶
By default, Prowler archives all its findings in Security Hub that have not appeared in the last scan.
You can skip this logic by using the option
--skip-sh-update so Prowler will not archive older findings: