---
title: Google Cloud Armor
description: ''
slug: /help/docs/platform-services/automation-service/app-central/integrations/google-cloud-armor/
canonical: https://www.sumologic.com/help/docs/platform-services/automation-service/app-central/integrations/google-cloud-armor/
---
import useBaseUrl from '@docusaurus/useBaseUrl';
})
***Version: 1.0
Updated: Jun 11, 2026***
Google Cloud Armor helps you protect your applications and websites against denial of service and web attacks.
## Actions
* **Get Rule** (*Enrichment*) - Retrieve details of a specific security policy rule.
* **Get Rule Hits Daemon** (*Daemon*) - Periodically monitor and retrieve rule hit counts for a security policy.
* **Get Security Policy** (*Enrichment*) - Retrieve the configuration and details of a specific security policy.
* **List Security Policies** (*Enrichment*) - List all security policies available in the specified project.
* **Update Rule** (*Containment*) - Update an existing security policy rule.
## Required IAM roles
The following table lists the required IAM roles for each action:
| Action | Required Role | Permission |
|:--------|:--------------|:------------|
| Get Rule | Security Admin (`roles/iam.securityAdmin`) | `compute.securityPolicies.getRule` |
| Get Rule Hits Daemon | Security Admin (`roles/iam.securityAdmin`) | `compute.securityPolicies.get` |
| Get Security Policy | Security Admin (`roles/iam.securityAdmin`) | `compute.securityPolicies.get` |
| List Security Policies | Security Admin (`roles/iam.securityAdmin`) | `compute.securityPolicies.list` |
| Update Rule | Compute Security Admin (`roles/compute.securityAdmin`) | `compute.securityPolicies.patchRule` |
:::note
For read-only actions (Get Rule, Get Rule Hits Daemon, Get Security Policy, List Security Policies), the **Security Admin** role is sufficient. For write actions (Update Rule), the **Compute Security Admin** role is required.
:::
## Google Cloud Armor configuration
The Google Cloud Armor integration supports two types of authentication: Service Account and WIF (Workload Identity Federation). We recommend using WIF since it is more secure and easier to manage. For more information, see [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation).
## Required AWS details from Sumo Logic
To configure the Google Cloud Armor integration using WIF authentication, you need the following AWS details from Sumo Logic. These details are essential for setting up the Workload Identity Federation (WIF) credentials in Google Workspace:
* Deployment name is the unique name of your Sumo Logic [deployment](/docs/api/about-apis/getting-started/#documentation), for example, `dub`, `fra`, etc.
* Sumo Logic AWS account ID: `926226587429`
* Sumo Logic AWS role: `-csoar-automation-gcparmor`
* Sumo Logic AWS Lambda function: `-csoar-automation-gcparmor`
* Full ARN: `arn:aws:sts::926226587429:assumed-role/-csoar-automation-gcparmor/-csoar-automation-gcparmor`
### Workload Identity Federation (WIF) authentication
To [create WIF credentials](https://cloud.google.com/iam/docs/workload-identity-federation) in Google Workspace needed to configure the Google Cloud Armor integration, follow these steps:
1. Log in to the [Google Cloud](https://console.cloud.google.com) portal.
2. Select a Google Cloud project (or create a new one).
3. Go to the **API&Services**.
4. In the same page click on **ENABLED API AND SERVICES** and search for Compute Engine API, Cloud Resource Manager API, IAM Service Account Credentials API, Identity and Access Management (IAM) API, Security Token Service API and enable them all.
5. Go to the **IAM & Admin** > **Service Accounts** page.
6. Click **CREATE SERVICE ACCOUNT**. A [Service Account](https://cloud.google.com/iam/docs/service-accounts-create) is required to access Google Cloud Armor.
7. While creating the service account, in **Permissions** add the role **Service Account Token Creator** and click on **DONE**.
})
8. Go to the **IAM & Admin** > **Workload Identity Federation** page.
})
9. Click **CREATE POOL**, provide the details, and click on **CONTINUE**.
})
10. Add **Provider details**. Select **AWS** as the provider type and provide the details of the AWS Account ID which is provided by Sumo Logic. Click on **CONTINUE** and **SAVE**.
})
11. Now you will see the created pool and provider.
})
12. Now we have to build a principal name to configure in Sumo Logic. The format of the principal name is: `principalSet://iam.googleapis.com/projects/{YourProjectID}/locations/global/workloadIdentityPools/{YourPoolName}/attribute.aws_role/arn:aws:sts::{SumoAWSAccountID}:assumed-role/{SumoAWSRole}/{SumoAWSLambdaFunction}`.
13. Go to the **IAM & Admin** > **IAM** page and click on **Grant Access** to add a new principal.
14. In the **New principals** field, provide the above principal name and select the role **Workload Identity User**. Click on **SAVE**.
})
15. Go to the **IAM & Admin** > **Workload Identity Federation** page and select the pool which was created above.
16. Click on **Grant Access** > **Grant access using service account impersonation**.
17. Select the service account which created above, select the principle as aws_role and provide the arn `arn:aws:sts::{SumoAWSAccountID}:assumed-role/{SumoAWSRole}` and click on **SAVE**.
})
18. Again go to **Grant Access** > **Grant access using service account impersonation**. Select the service account which was created above. Select the principle as `aws_role` and provide the arn `arn:aws:sts::{SumoAWSAccountID}:assumed-role/{SumoAWSRole}/{SumoAWSLambdaFunction}`. Click on **SAVE**.
19. Download the WIF `conf.json` file. Make sure you save it in a safe place. Use the JSON content to configure the Google Cloud Armor integration to use WIF authentication in Automation Service and Cloud SOAR.
### Service Account authentication
To [create service account credentials](https://developers.google.com/workspace/guides/create-credentials) in Google Workspace needed to configure the Google Cloud Armor integration, follow these steps:
1. Log in to the [Google Cloud](https://console.cloud.google.com) portal.
2. Select a Google Cloud project (or create a new one).
3. Go to the **API&Services** > **Credentials** page.
4. In the same page click on **ENABLED API AND SERVICES** and search for Compute Engine API, Cloud Resource Manager API, IAM Service Account Credentials API, Identity and Access Management (IAM) API, Security Token Service API and enable them.
5. Click **CREATE CREDENTIALS** and select **Service Account**.
})
6. Enter a service account name to display in the Google Cloud console. The Google Cloud console generates a service account ID based on this name.
7. (Optional) Enter a description of the service account.
8. Skip two optional grant permissions steps and click **Done** to complete the service account creation.
})
9. Click on the generated service account to open the details.
})
10. Under the **KEYS** tab, click **ADD KEY** and choose **Create new key**.
})
11. Click on **CREATE** (make sure **JSON** is selected).
})
12. The JSON file is downloaded. Make sure you save it in a safe place.
## Configure Google Cloud Armor in Automation Service and Cloud SOAR
import IntegrationsAuth from '../../../../reuse/integrations-authentication.md';
import IntegrationCertificate from '../../../../reuse/automation-service/integration-certificate.md';
import IntegrationEngine from '../../../../reuse/automation-service/integration-engine.md';
import IntegrationLabel from '../../../../reuse/automation-service/integration-label.md';
import IntegrationProxy from '../../../../reuse/automation-service/integration-proxy.md';
import IntegrationTimeout from '../../../../reuse/automation-service/integration-timeout.md';
*
* **Authentication Type**. Select the authentication type: **Service Account Private Key Json** or **Workload Identity Federation Private Key Json** and provide the selected type JSON content.
* **Scopes**. Default scope is already added as `https://www.googleapis.com/auth/cloud-platform`, if not then add this scope.
* **Project ID**. Provide the Google Cloud Project ID where the Cloud Armor actions will be performed.
*
*
})
For information about Google Cloud Armor, see [Google Cloud Armor documentation](https://cloud.google.com/armor/docs).
## Change Log
* June 11, 2026 (v1.0) - First upload