1. Overview

You can configure Prisma Cloud to route alerts to PagerDuty. When Prisma Cloud detects anomalies, it generates alerts. Alerts are raised when the rules that make up your policy are violated.

2. Configuring PagerDuty

Create a new Prisma Cloud service, and get an integration key.

  1. Log into PagerDuty.

  2. Go to Configuration > Services.

  3. Click New Service.

    pagerduty create new service
  4. Under General Settings:

    1. Name: Enter Prisma Cloud.

  5. Under Integration Settings:

    1. Integration Type: Select Use our API directly, the select Events API v2.

    2. Integration Name: Enter Prisma Cloud.

      pagerduty add service form
  6. Click Add Service. You’re taken to Integrations tab for the Prisma Cloud service.

    pagerduty add service
  7. Copy the Integration Key, and set it aside. You’ll use it to configure the integration in Prisma Cloud Console.

    pagerduty integration key

2.1. 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 Second, Minute, Hour, Day.

    frag configure alerts

3. Sending alerts to PagerDuty

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.

pagerduty config

If you use multi-factor authentication, you must create an exception or app-specific password to allow Console to authenticate to the service.

4. 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 Provider, select PagerDuty.

5. Configure the channel

Configure the channel.

  1. In Routing Key, enter the integration key you copied from PagerDuty.

  2. In Summary, enter a brief description, which will appear in the PagerDuty dashboard alongside your alerts.

  3. For Severity, select the urgency of the alert.

  4. Click Send Test Alert to validate the integration.

    If the integration is set up properly, you will see a sample alert in PagerDuty. In the PagerDuty dashboard, click Alerts.

    pagerduty review test alert

5.1. 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 Edit.

  3. To specify specific rules that should trigger an alert, deselect All rules, and then select any individual rules.