: Google Cloud Security Command Center

Google Cloud Security Command Center

Table of Contents
End-of-Life (EoL)

Google Cloud Security Command Center

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.

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.
  5. Grant this service account access to project (optional)
    . Do not grant a role to the account at this time.
  6. Grant user account to this service account
    create key
  7. Set key type to
    , and click
    . Save the downloaded JSON key.
  8. Go to the project’s
    APIs & Services > Credentials
  9. Click
    Create credentials > API key
  10. Save the API key. We recommended that you restrict the key to the
    Cloud Security Command Center API
  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
    window click
  13. Paste in the name of the service account that has been created.
  14. Select Role:
    Security Center > Security Center Editor

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 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.
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
    Security Center

Configure the channel

Configure the channel.
  1. In
    , click
    Add new
    or select an existing service account.
    To create a new GCP credential, see here.
  2. In
    Source Name
    , enter the resource path for a source that’s already been created.
    The source name has the following format:
    Where organization_id and source_id are numeric identifiers. For example:
  3. Click
    Send Test Alert
    to test the connection.

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