1. Overview

Prisma Cloud can be configured as a security source that provides security findings to Google Cloud Security Command Center (SCC). This lets you see all security tool findings in a single place.

Prisma Cloud is a registered Google Cloud Platform Marketplace partner.

2. Configuring Google Cloud Security Command Center

In Google Cloud Platform (GCP), create a service account in your project that has the Cloud Security Command Center API enabled. You will need the service account keys, API, and Organization ID to enable this feature.

You should have already enabled and onboarded Prisma Cloud as a Security Source in Google Security Command Center. Prisma Cloud supports the alpha and beta versions of Google Security Command Center. The following instructions show how to configure the beta version.

  1. Log into your GCP tenant and select the project that has the Cloud Security Command Center API enabled.

  2. Go to IAM & admin > Service accounts.

  3. Click Create Service Account.

  4. Enter a name and description for the service account.

    alerts gcss svc account
  5. Grant this service account access to project (optional) click continue. Do not grant a role to the account at this time.

  6. Grant user account to this service account click create key.

  7. Set key type to JSON, and click create. Save the downloaded JSON key.

  8. Go to the project’s APIs & Services > Credentials.

  9. Click Create credentials > API key.

    alerts gcss api key1
  10. Save the API key. We recommended that you restrict the key to the Cloud Security Command Center API.

    alerts gcss api key2
  11. Go to the Google tenant’s organizational IAM & admin.

    This setting is configured at the organizational level, not the project level.
  12. In the IAM window click +Add.

  13. Paste in the name of the service account that has been created.

  14. Select Role: Security Center > Security Center Editor.

    alerts gcss role

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 Google Cloud SCC

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.