This article explains how to configure the App Activities integration for Google Drive and Workspace.
App Activities provides you with an API-based solution for out-of-band visibility of all activity made by any user in a connected SaaS application. To provide App Activities with visibility of data within an app, you need to set up an integration with the required application. Once you create the integration, if a field has changed or expired, you can edit it from the Resources >Integrations > Integrated Apps page. For more information, see What is Application Control via API with App Activities.
To configure the App Activities integration, you need to:
-
Configure the integration within the SaaS application
-
Create the API connector in the CMA
A CASB license is required for App Activities. This license includes app and data control and App Activities via API. For more about purchasing a CASB license, please contact your Cato representative.
Connecting your Google Workspace account to Cato enables visibility into:
-
User Login Activity: Track successful and failed login attempts across all Google Workspace services (e.g., Gmail, Drive, Docs, Sheets, Calendar).
-
Third-party App Authorizations (OAuth Events): Monitor when users sign in to third-party applications using Google Sign-In or grant external apps access to Workspace data. This includes token issuance, scopes granted (e.g., Drive read/write), and token revocations.
To configure the Google Drive and Workspace integration, create a new project.
In the Google Cloud Console, create a Service account private key to enter into the CMA.
To configure the Google Drive and Workspace integration:
-
In your Google Cloud Console, click Select a Project.
-
Click New project.
-
Choose a Name and Location and click Create.
-
Navigate to APIs & Services > Library.
-
Search for Admin SDK.
-
Click on Admin SDK API and click Enable.
-
Navigate to IAM & Admin > Service Accounts.
-
Select the project you created in step two, and click Create service account.
-
Add a Service account ID and click Create and continue.
-
In the Select a role drop down, choose Audit Manager Admin (you can search for this role).
-
Click Done.
-
Click on the service account you created and navigate to the Keys tab,
-
Click Add key > Create new key.
-
Choose the JSON key type and click Create.
A JSON file containing the private key is downloaded.
-
Copy and save the Private key so it can be added to the CMA.
-
In the Google Admin console, navigate to Security > Access and Data Control > API control.
-
Under Domain wide delegation, select Manage Domain Wide Delegation.
-
Click Add new.
-
Add the Client ID of the Service Account. You can find this in the Service Account page.
-
Add this scope:
https://www.googleapis.com/auth/admin.reports.audit.readonly. -
Click Authorize.
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:
-
From the navigation menu, click Resources > Integrations.
-
Click the Integrated Apps tab.
-
Click New.
The New Integration panel opens.
-
Select the SaaS Application you want to add.
Note: Enter the Private Key in JSON format.
-
In the Capability drop down select App Activities.
-
Add the details created during step one.
-
Click Save.
-
The app is visible on the Integrated Apps table with a Connected status.
After connecting your APIs, you can track the App activities in the Cloud Activities dashboard. Data may take a few minutes to appear.
-
Audit Logs Drive - Activities/drive endpoint to query Google Drive audit logs
-
Audit Logs Login - Activities/Login endpoint to query Google native logins audit logs
-
Audit Logs Third Party (Token) - Activities/token endpoint to query Google third_party logins audit logs
0 comments
Please sign in to leave a comment.