Table of Contents
End-of-Life (EoL)

AWS Security Hub

AWS Security Hub aggregates, organizes, and prioritizes security alerts from multiple AWS services and AWS Partner Network solutions, including Prisma Cloud, to give you a comprehensive view of security across your environment.


The minimum required permissions policy to integrate Prisma Cloud with AWS Security Hub is
. Whether using IAM users, groups, or roles, be sure the entity Prisma Cloud 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
permissions policy. You will need the service account’s access key ID and secret access key to integrate with Prisma Cloud.

Enabling AWS Security Hub

  1. Log into your AWS tenant and enter
    Security Hub
    in the
    Find services
    search, then select
    Security Hub
  2. Click
    Enable Security Hub
  3. Enable the Prisma Cloud integration.
    1. Choose Integrations from the Security Hub menu.
    2. Accept findings from Palo Alto Networks: Prisma Cloud Compute.

Configuring alert frequency

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.
  1. Open Console, and go to
    Manage > Alerts
  2. In
    Aggregate audits every
    , specify the maximum rate that alerts should be sent.
    You can specify

Sending alerts to Security Hub

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 Prisma Cloud 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 new alert profile

Create a new alert profile.
  1. In
    Manage > Alerts
    , click
    Add profile
  2. Enter a name for your alert profile.
  3. In
    , select
    AWS Security Hub

Configure the channel

Configure the channel.
  1. In
    , select your region.
  2. Enter your
    Account ID
    , which can be found in the AWS Management Console under
    My Account > Account Settings
  3. Select or create credentials, which Prisma Cloud uses to integrate with AWS Security Hub.
    You can use an IAM user, IAM role, or AWS STS.
  4. Click
    Send Test Alert
    to test the connection. An alert is sent immediately.

Configure the triggers

Configure how the alert is triggered.
  1. Under
    Alert Types
    , check the boxes types of events that should trigger an alert.
  2. For additional configuration options, click
  3. To specify specific rules that should trigger an alert, deselect
    All rules
    , and then select any individual rules.
  4. Click

Recommended For You