Google Workspace AlertCenter Source

This topic has information about the Google Workspace AlertCenter Cloud-to-Cloud Source, part of Sumo Logic's Cloud-to-Cloud Integration Framework.

Data collected

Polling Interval	Data
5 minutes	Alerts data

Setup

Vendor configuration

Follow the below steps to create Google Workspace AlertCenter service account credentials:

1. From Google Cloud console, select your project or create a new one.
2. Enable Google Workspace Alert Center API for the Alert API. To locate this setting, you can search for "Google Workspace Alert Center API" in the search bar. Then select the Enable button.
   
3. You will be redirected to the dashboard page. Select the Credentials tab in the left panel.
   
4. Click Create Credentials, and select Service Account to create service account credentials. Later you'll supply the account details and click Done to create a service account.
   
5. To create JSON for the service account, you must create a key. Click the service account email to navigate to the Keys tab.
   
6. Click Add key and select Create new key. At the prompt, select JSON and click Create to create a key.
   
7. JSON for the service account is automatically downloaded. To see what the JSON looks like, and how the JSON fields map to the fields you'll configure, see the service account JSON example below.
8. Add domain-wide delegation to your service account using the client ID generated in step 5.
9. From the Google admin console, add your OAuth scope to the service account using the instructions here and select it in the input form. The OAuth scope for alert API is:

   https://www.googleapis.com/auth/apps.alerts
   note

   If you do not add an OAuth scope to your Google Workspace service account, you won't be authorized to fetch alert details. Learn more about OAuth scopes:

   • Using OAuth 2.0 to Access Google APIs
   • Setting up OAuth 2.0
10. For delegated user email, you need to add the email of the user whom you want to delegate for API calls.

Source configuration

1. Classic UI. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
   New UI. In the Sumo Logic top menu select Configuration, and then under Data Collection select Collection. You can also click the Go To... menu at the top of the screen and select Collection.
2. On the Collectors page, click Add Source next to a Hosted Collector.
3. Search for and select Google Workspace AlertCenter.
4. Name. Enter a name for the Source.
5. Description. (Optional). Enter the description of the Source.
6. Source Category. Enter a string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
7. Forward to SIEM. Click if you want the Source to forward the logs it ingests to Cloud SIEM.
   
   note

   Select Forward to SIEM only if you have Cloud SIEM installed.

8. Fields. (Optional) Click +Add Field to define the fields you want to associate, each field needs a name (key) and value. For more information, see Fields.
   •  A green circle with a checkmark is shown when the field exists in the Fields table schema.
   •  An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema it is ignored (i.e., dropped).
9. Delegated User Email. Enter the admin email address for the domain. This email should be the address that is configured for the specific service account in the Google Cloud console.
10. Google Workspace AlertCenter Credentials. You can authenticate your service account credentials directly by uploading a JSON file credentials instead of breaking down the file into different sections for the UI schema. Click Upload and select the JSON file that you downloaded in the Service Account Credentials section.
11. Exclude Alert Types. (Optional) Enter the data alert types and scope that you do not want to send to Sumo Logic.
    note

    All alert types are selected by default unless you exclude some of the alert types in the config JSON schema.

12. Processing Rules for Logs. (Optional) Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
13. When you are finished configuring the Source, click Submit.

Metadata

If the Source is configured with the SIEM forward option, then the metadata field _siemparser will be set to /Parsers/System/Google/GSuite Alert Center.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

Parameter	Type	Value	Required	Description
schemaRef	JSON Object	{"type":"Google Workspace AlertCenter"}	Yes	Define the specific schema type.
sourceType	String	"Universal"	Yes	Type of source.
config	JSON Object	Configuration object	Yes	Source type specific values.

Configuration Object

Parameter	Type	Required	Default	Description	Example
name	String	Yes	null	Type a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source.	"mySource"
description	String	No	null	Type a description of the source.	"Testing source"
category	String	No	null	Type a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details.	"mySource/test"
fields	JSON Object	No	null	JSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.	{"_siemForward": false, "fieldA": "valueA"}
delegatedUserEmail	String	Yes	null	Provide the super-administrator email address for the domain that granted access to the service account you created.
credentialsJson	String	Yes	null	Authentication service account's credentials to access Google Workspace Platform.
excludedAlertTypes	Array of Strings	No		Defines the types of alerts which the user want to exclude.

JSON example

{
    "type": "service_account",
    "project_id": "sample_project",
    "private_key_id": "asdfgh1234556",
    "private_key": "-----BEGIN PRIVATE KEY-----\nsample_private_key\n-----END PRIVATE KEY-----\n",
    "client_email": "sample_project@sample_service_account.com",
    "client_id": "12345678",
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://oauth2.googleapis.com/token",
    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
    "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/sample_url.com"
  }

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "google_workspace_alertcenter_source" {
  collector_id = sumologic_collector.collector.id
  schema_ref = {
    type = "Google Workspace AlertCenter"
  }
  config = jsonencode({
    "type": "service_account",
    "project_id": "sample_project",
    "private_key_id": "asdfgh1234556",
    "private_key": "-----BEGIN PRIVATE KEY-----\nsample_private_key\n-----END PRIVATE KEY-----\n",
    "client_email": "sample_project@sample_service_account.com",
    "client_id": "12345678",
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://oauth2.googleapis.com/token",
    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
    "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/sample_url.com"
  })
}
resource "sumologic_collector" "collector" {
  name        = "my-collector"
  description = "Just testing this"
}

Download example

FAQ

info

Click here for more information about Cloud-to-Cloud sources.