1. Overview

Prisma Cloud can send email alerts when your policies are violated. Audits in Monitor > Events are the result of a policy violation. Prisma Cloud can be configured to notify the appropriate party by email when an entire policy, or even specific rules, are violated.

Because Prisma Cloud Enterprise Edition Compute Console is hosted on Google Cloud Platform, outbound connections to port 25 from Console are blocked. All other ports are available, including ports 587 and 465. For more information, see here.

1.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

2. Sending email alerts

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.

email config

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

3. 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 Email.

4. Configure the channel

Configure the channel.

  1. In SMTP address, specify the hostname for your outgoing email server.

  2. In Port, specify the port for email submissions.

  3. In Credential, create the credentials required to access the email account that sends alerts. This isn’t a required field.

    1. Click Add new.

    2. Select Basic authentication.

    3. Enter a username and password.

  4. If you’re using SMTPS (your SMTP connection is secured by SSL), set SSL to On.

  5. Set up your recipients.

    1. Click Add recipient, and enter an email address. Every email alert profile must have at least one recipient, even if you’re using alert labels.

    2. (Optional) Specify recipients using alert labels.

  6. Click Send Test Alert to test the connection to your SMTP server.

4.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.

    frag config triggers
  4. Click Save.