AWS Security Hub is a cloud security posture management service that:
- Reduced effort to collect and prioritize findings
- performs automatic security checks against best practices and standards
- aggregates your security alerts in a consolidated view of findings across accounts and providers
- enables automated remediation
Security Hub enables you to understand your overall security posture via a consolidated security score across all of your AWS accounts, and automatically assesses the security of your AWS accounts resources via the security standards available:
- AWS Foundational Security Best Practices
- CIS AWS Foundations Benchmark
- PCI DSS
Enabling this service is a MUST and a quick win to improve your security posture: just by enabling some security standard you will receive security alerts (findings), and the service will aggregate your security alerts automatically.
To maintain a complete view of your security posture on AWS, you need to integrate multiple tools and services including
- Threat detections from Amazon GuardDuty,
- vulnerabilities scan from Amazon Inspector,
- publicly accessible and cross-account resources from IAM Access Analyzer,
- sensitive data classifications from Amazon Macie,
- resources lacking WAF coverage from AWS Firewall Manager,
- resource configuration issues from AWS Config,
- and AWS Partner Network Products.
Whether an account needs to enable AWS Security Hub manually depends on how the accounts are managed.
If you use the integration with AWS Organizations:
- The organization management account chooses a Security Hub administrator account. Security Hub is enabled automatically for the chosen account. See Designating a Security Hub administrator account.
- The Security Hub administrator account enables organization accounts as member accounts. Those organization accounts also have Security Hub enabled automatically. See Managing member accounts that belong to an organization.
- The only organization account for which Security Hub is not enabled automatically is the organization management account. The organization management account does not need to enable Security Hub before it designates the Security Hub administrator account. The organization management account must enable Security Hub before it is enabled as a member account.
Accounts that are not managed using the Organizations integration must enable Security Hub manually.
To start using AWS Security Hub, it only takes a few clicks from the Management Console to start adding findings and performing security checks.
As you can see in the image, you only need to check the Security Standard you want to enable and then enable de service. Additionally, you can download a CloudFormation template to deploy it as StackSet.
After you enable a security standard, AWS Security Hub begins to run all checks within two hours but it can take up to 24 hours for the Security standards pane to populate
Pricing (USD), Per account, per month, per Region
|100,001 – 500,000||$0.0008/check|
|Finding ingestion events|
It includes ingestion of updates to existing findings. Finding ingestions for Security Hub security checks is free.
Within the Security Hub service, under the Settings Usage tab, you can find your monthly estimate:
On the Summary page:
- Security standards show you your security score (total and by standard), and the resources with the most failed security checks
- Findings by Region summarize the number of active findings for each severity across Regions. The counts only include findings that have a workflow status of NEW or NOTIFIED.
- Insights: An AWS Security Hub insight is a collection of related findings. It identifies a security area that requires attention and intervention.
This page shows you the 3 security standards and whether you have them enabled (with their security score) or not (you can enable them with a one-click action).
If you access one of them, you will be able to see more details about how many security controls are enabled, failed, passed, disabled… and a table with information about compliance status, severity, ID, title and Failed checks:
This page shows all the findings, the ones generated by AWS Security Hub with Security Standards and all the rest of the other tools and services.
In the following image, you can view Security Hub and GuardDuty findings:
With finding aggregation, you can use a single aggregation account & Region to view and update findings from multiple linked accounts & Regions. Administrator accounts configure the aggregation. Security Hub replicates findings and finding updates for all of the member accounts in the linked Regions.
- You can connect multiple AWS accounts and consolidate findings across those accounts
- You can also designate an aggregator Region and link some or all Regions to that aggregator Region to give you a centralized view of all your findings across all your accounts and all your linked Regions
Interesting article in AWS Security Blog: Best practices for cross-Region aggregation of security findings. Best practices mentioned:
- Enable cross-Region aggregation
- Consolidating downstream SIEM and ticketing integrations
- Auto-archive GuardDuty findings associated with global resources
- Reduce AWS Config cost by recording global resources in one Region
- Disable AWS Security Hub AWS Foundational Best Practices periodic controls associated with global resources
- Implement automatic remediation from a central Region
You also can show your AWS Security Hub findings in a view of data to enable decision-makers to assess the health and status of an organization’s IT infrastructure at a glance. This article contains how to do it.
When you enable a standard, all the controls for that standard are enabled by default. You can then disable and enable specific controls within an enabled standard.
There are several reasons why you may choose to disable the controls:
- Controls for unused services
- Controls using global resources
- Controls with compensating controls
It can be useful to turn off security checks for controls that are not relevant to your environment. Disabling irrelevant controls reduces the number of irrelevant findings. It also removes the failed check from the security score for the associated standard.
When you disable a control, the following occurs:
- The check for the control is no longer performed.
- No additional findings are generated for that control.
- Existing findings are archived automatically after three to five days (note that this is the best effort and not guaranteed).
- The related AWS Config rules that Security Hub created are removed.
Remember that Security Hub is Regional. When you disable or enable a control, it is disabled only in the current Region or in the Region that you specify in the API request.
This is the fastest way to disable one control, with the CLI:
1 aws securityhub update-standards-control --standards-control-arn "arn:aws:securityhub:eu-west-1:1234567890:control/aws-foundational-security-best-practices/v/1.0.0/GuardDuty.1" --control-status "DISABLED" --disabled-reason "testing functionality"
With the AWS Console, you can easily disable a control. Access to a security standard:
In the following links, you will find more information on how to do it in depth, how to do it in a multi-account environment (several options), and more relevant information!
- How to disable controls
- How to disable in a multi-account environment
- AWS Foundational Best Practices controls that you might want to disable
- how to Create Auto-Suppression Rules in AWS Security Hub
Security Hub provides the ability to integrate security findings from AWS services and third-party products.
For AWS services Security Hub automatically enables the integration, and you can optionally disable each integration. For third-party products Security Hub gives you the ability to selectively enable the integrations and provides a link to the configuration instructions related to the third-party product.
Some examples of custom integrations:
You can create custom automated response, remediation, and enrichment workflows using Security Hub’s integration with Amazon EventBridge. All Security Hub findings are automatically sent to EventBridge, and you can create EventBridge rules that have AWS Lambda functions, AWS Step Function functions, or AWS Systems Manager Automation runbooks as their targets.
Security Hub also supports sending findings to EventBridge on-demand via custom actions, so that you can have an analyst decide when to trigger an automated response or remediation action.
The Security Hub Automated Response and Remediation (SHARR) solution provides you with pre-packaged EventBridge rules for you to deploy via AWS CloudFormation.
More info about automated response and remediation here
- Regional service
- 30 days free trial when you enable it the first time, and during the free trial Security Hub provides an estimate of what the spend would be, so you can assess your spending beyond the free trial.
- All findings are stored in Security Hub for 90 days after the last update date
- Periodic checks run automatically within 12 hours after the most recent run. You cannot change the periodicity.
- Change-triggered checks run when the associated resource changes state. Even if the resource does not change state, the updated time for change-triggered checks is refreshed every 18 hours.
- After control statuses are generated for the first time, Security Hub updates the control status every 24 hours based on the findings from the previous 24 hours
- Security Hub processes the findings using a standard findings format called the AWS Security Finding Format (ASFF), which eliminates the need for time-consuming data conversion efforts. With the ASFF, all of Security Hub’s integration partners (including both AWS services and external partners) send their findings to Security Hub in a well-typed JSON format consisting of over 1,000 available fields. This means that all of your security findings are normalized before they are ingested into Security Hub, and you don’t need to do any parsing and normalization yourself. The findings identify resources, severities, and timestamps consistently so that you can more easily search and take action on them.
- The events are delivered to EventBridge in near-real-time and on a guaranteed basis
- When you enabled a security standard, AWS Config rules are created automatically (and you cannot delete them)
- You can create Custom Findings with AWS Config Rules and send them to Security Hub with EventBridge