Skip to content

Integration with Google Workspace (formerly G Suite)

There are two options to integrate with Google Workspace - by sharing the Workspace logs with GCP and by directly fetching audit log reports from Workspace.

Integration with Google Workspace (formerly G Suite) through GCP

In order to have your organization's Google Workspace audit logs integrated you should:

  1. Enable sharing of your Google Workspace audit logs with your Google Cloud Platform as described in this Google support page
  2. Create a GCP pull integration (unless you already have one) as described in our documentation

Note that this option only shares Admin logs, Login logs and Enterprise Group logs. If you need specific logs for Drive, Meet and other services, see the section below.

Direct integration with Google Workspace

In order to directly collect logs from Workspace, you need to create a service account. To do that:

  1. Following this guide, create a service account. You may need to create a new project in the Google API console if you don't have one already.
  2. To create a service account, first enable the admin API for the workspace project
  3. Choose to create credentials and select "Application data" for the Admin SDK credentials. Also select "No, I'm not using them" for the Google infrastructure question.
  4. The wizard takes you to IAM & Admin -> Service Accounts. Create one with default permissions
  5. Edit the newly created service account
  6. Go to the Keys tab to create a new key
  7. Download the API key in JSON format
  8. On the "Details" check the "Enable Google Workspace domain-wide delegation (specify a produsct name, e.g. LogSentinel SIEM)
  9. Go to the Workspace admin console and choose Security -> API Controls. Then select "Manage domain-wide delegation"
  10. Grant access to the service account (follow this guide). For "scopes" specify "" and click Authorize
  11. Go to LogSentinel -> Sources & Integrations -> Integrations and create a new Google Workspace integration
  12. Paste the contents of the JSON key file
  13. Specify a user email. This email is different than the service account and needs to have permissions to access the Admin API.
  14. Save the integration