AWS Security Hub aggregates, organizes, and prioritizes security alerts from multiple AWS services and AWS Partner Network solutions, including Twistlock, to give you a comprehensive view of security across your environment.
The minimum required permissions policy to integrate Twistlock with AWS Security Hub is AWSSecurityHubFullAccess. Whether using IAM users, groups, or roles, be sure the entity Twistlock uses to access AWS Security Hub has this minimum permissions policy.
This procedure shows you how to set up integration with an IAM user (configured as a service account). In AWS IAM, create a service account that has the AWSSecurityHubFullAccess permissions policy. You will need the service account’s access key ID and secret access key to integrate with Twistlock.
Log into your AWS tenant and enter Security Hub in the Find services search, then select Security Hub.
Click Enable Security Hub.
You can configure the rate at which alerts are emitted. This is a global setting that controls the spamminess of the alert service. Alerts received during the specified period are aggregated into a single alert. For each alert profile, an alert is sent as soon as the first matching event is received. All subsequent alerts are sent once per period.
Open Console, and go to Manage > Alerts.
In Aggregate audits every, specify the maximum rate that alerts should be sent.
You can specify Second, Minute, Hour, Day.
Alert profiles specify which events should trigger the alert machinery, and to which channel alerts are sent. You can send alerts to any combination of channels by creating multiple alert profiles.
Alert profiles consist of two parts:
(1) Alert settings — Who should get the alerts, and on what channel? Configure Twistlock to integrate with your messaging service and specify the people or places where alerts should be sent. For example, configure the email channel and specify a list of all the email addresses where alerts should be sent. Or for JIRA, configure the project where the issue should be created, a long with the type of issue, priority, assignee, and so on.
(2) Alert triggers — Which events should trigger an alert to be sent? Specify which of the rules that make up your overall policy should trigger alerts.
If you use multi-factor authentication, you must create an exception or app-specific password to allow Console to authenticate to the service.
Create a new alert profile.
In Manage > Alerts, click Add profile.
Enter a name for your alert profile.
In Provider, select AWS Security Hub.
Configure the channel.
In Region, select your region.
Enter your Account ID, which can be found in the AWS Management Console under My Account > Account Settings.
Provide your credentials, which Twistlock uses to integrate with AWS Security Hub. You can either:
Set Use IAM Role to On to use the role assigned to the EC2 instance that runs Console.
Select a Credential, which holds the access key and secret for a service account. Select an existing credential or create a new one.
(Optional) Toggle the Use AWS STS to On. In Role ARN, specify the role to use.
For more information about AWS STS, see AWS Security Token Service.
Click Send Test Alert to test the connection. An alert is sent immediately.
Under Alert Types, check the boxes types of events that should trigger an alert.
For additional configuration options, click Edit.
To specify specific rules that should trigger an alert, deselect All rules, and then select any individual rules.
Click Save.