> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/alerts/google-cloud-scc.md).

# Google Cloud SCC

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](https://console.cloud.google.com/marketplace/details/twistlock/twistlock). 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.

   <figure><img src="/files/Y6S2AriCLqx0dRtnFxc3" alt="alerts gcss svc account"><figcaption></figcaption></figure>
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**.

   <figure><img src="/files/rBkacjY1UVN3VWGJzzH0" alt="alerts gcss api key1"><figcaption></figcaption></figure>
10. Save the API key. We recommended that you restrict the key to the **Cloud Security Command Center API**.

    <figure><img src="/files/G1XCtedi2DeJ9sSmGyWQ" alt="alerts gcss api key2"><figcaption></figcaption></figure>
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**.

    <figure><img src="/files/H0xAEsrYNFX8hdT2R1Zx" alt="alerts gcss role"><figcaption></figcaption></figure>

## 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 **General settings**, select the default frequency for all alerts.

   You can specify the following frequencies.

   * **10 Minutes**
   * **1 Hour**
   * **1 Day**.

## 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, along 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.

<figure><img src="/files/wBNspdXoiFkgK39xvViQ" alt="google cloud scc config"><figcaption></figcaption></figure>

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 **Provider**, select **Security Center**.

## Configure the channel

Configure the channel.

1. In **Credential**, click **Add new** or select an existing service account.

   To create a new xref:\~/authentication/credentials-store/gcp-credentials.adoc\[GCP credential] as needed.
2. In **Source Name**, enter the resource path for a source that’s already been created.

   The source name has the following format:

   ```
   organizations/<organization_id>/sources/<source_id>
   ```

   Where organization\_id and source\_id are numeric identifiers. For example:

   ```
   organizations/111122222444/sources/43211234
   ```
3. Click **Send Test Alert** to test the connection.

## Configure the triggers

1. In **Select triggers**, select the events that should trigger an alert to be sent.
2. To specify specific rules that should trigger an alert, deselect **All rules**, and then select any individual rules.

   <figure><img src="/files/gmaXc0eG7BJcQwqAayqm" alt="frag config triggers"><figcaption></figcaption></figure>
3. Click **Next**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/33/alerts/google-cloud-scc.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.