Google Workspace: Configuring the Remediation Actions Integration

Prev Next

Overview

XOps integrations let you take response actions in connected third-party applications as part of an investigation. You can revoke a user’s sessions or disable their account in your single sign-on (SSO) provider or a specific application. These actions help you contain threats by restricting access to affected accounts. To enable these actions, configure a connector for the relevant third-party application.

For more information, see Mitigating Threats in XOps Stories.

To configure the Remediation Actions integration, you need to:

  1. Configure the required settings in the SaaS application

  2. Create the API connector in the CMA

A XOps license is required for Remediation Actions integrations.

Benefits of Connecting Google Workspace

The Google Workspace Remediation Actions connector lets Cato take response actions on user accounts during an investigation. It uses a separate connector with write access, without affecting your other Google Workspace connectors.

  • Disable User: Suspends the user's account and blocks sign-in. Email, documents, calendars, and other data are not deleted. An administrator can restore the account.

  • Revoke Sign-In Sessions: Signs the user out of all web and device sessions and resets their sign-in cookies, requiring another sign-in. It also deletes every third-party app access grant the user gave. The account is not suspended, and the action also works for suspended users.

Configuring the Google Workspace Integration

To configure the integration, set up a Google service account with domain-wide delegation and create the API connector in the Cato Management Application (CMA).

Prerequisites

  • A Google Workspace Business Standard, Business Plus, Enterprise, or Education edition

  • A Super Admin account to configure domain-wide delegation and act as the administrator for the connector

Step 1: Configure the Integration in Google Workspace

Enable the Admin SDK API, create a service account and JSON key, and authorize the required OAuth scopes through domain-wide delegation.

Create API access:

  1. In your Google Cloud console click Select a Project :

  2. Click New Project.

  3. Choose a Name and Location and click Create.

  4. Navigate to APIs & Services > Library.

  5. Search for Admin SDK.

  6. Click on Admin SDK API and click Enable.


  7. Navigate to IAM & Admin > Service Accounts.

  8. Select the project you created in step two, and click Create service account.

  9. Add a Service account ID and click Create and continue.

  10. Click Done. (No role is required for this connector)

  11. Click on the service account you created and navigate to the Keys tab,

  12. Click Add key > Create new key.

  13. Choose the JSON key type and click Create.

  14. A JSON file containing the private key is downloaded.

  15. Copy and save the Private key so it can be added to the CMA.

  16. In the Google Admin console, navigate to Security > Access and Data Control > API control.

  17. Under Domain wide delegation, select Manage Domain Wide Delegation.

  18. Click Add new.

  19. Add the Client ID of the Service Account. You can find this in the Service Account page.

  20. Add these scopes:

    https://www.googleapis.com/auth/admin.directory.user,https://www.googleapis.com/auth/admin.directory.user.security
  21. Click Authorize.


Step 2: Create the API Connector in the CMA

After you have set up an integration with the required application, add the details in the CMA.

To create the API connector in the CMA:

  1. From the navigation menu, click Resources > Integrations.

  2. Click the Configured Integrations tab.

  3. Click New. The New Integration panel opens.

  4. Select the SaaS Application you want to add.

  5. In the Capability drop-down, select Remediation Actions.

  6. Add the details created during step one.

    • SaaS Application: Google Workspace

    • Name: Enter a name for the integration

    • Description: Optionally, enter a description

    • Admin Email: Enter the email address of the Super Admin

    • Service Account Key: Paste the full contents of the downloaded JSON key file

  7. Click Save.

The app is visible on the Integrated Apps table with a Connected status.

Known Limitations

  • Directory search delays: Google states that most user data updates within one hour. New data can take up to 36 hours to appear in all search results. A recently created or changed user may not be found.

  • Connector administrator: The account the connector acts as cannot be suspended by Disable User.

  • Session revocation: Revoke Sign-In Sessions does not suspend the user, who can sign in again with their credentials. Deleting an app grant removes access issued by Google. Apps may retain their own sessions outside Google.

  • Administrator accounts: Only Super Admins can change another administrator's account. With a delegated administrator instead of a Super Admin, the action is unsuccessful for users who are administrators.

  • Connection status: Connected confirms read access to list users only. Missing scopes or privileges, including the scope for session revocation, are reported when an action runs.