Table of Contents | ||||
---|---|---|---|---|
|
Service description
The G Suite Alert Center manages alerts on potential issues within your domain. Apps you develop can use the Alert Center API to retrieve alerts in order to respond to them. Apps can also use the API to create and retrieve alert feedback. For example, a monitoring app could retrieve new alerts, prioritize them, and then notify members of your organization when action is needed.
Data source description
The G Suite API generates account activities for these applications and sources. The G suite collector that we provide processes the Google API responses and sends them to the Devo platform. Data will be categorized in different tables in your Devo domain, as you can check in the following table.
G Suite Alert Center
Listed in the table below are the alerts sources, types, the data that G Suite classifies and how Devo platform treats it.
...
Alert source
...
Alert type
...
Devo data tables
...
Domain wide takeout
...
Customer takeout initiated
...
cloud.gsuite.alerts.customer_takeout_initiated
...
Gmail phishing
...
Malware reclassification
...
cloud.gsuite.alerts.malware_reclassification
...
Misconfigured whitelist
...
cloud.gsuite.alerts.misconfigured_whitelist
...
Phishing reclassification
...
cloud.gsuite.alerts.phishing_reclassification
...
Suspicious message reported
...
cloud.gsuite.alerts.suspicious_message_reported
...
Table of Contents | ||||
---|---|---|---|---|
|
Service description
Workspace is Google’s suite of products that includes email, calendar, drive, meet, and other collaboration solutions. This collector provides the possibility to integrate Google Workspace with the Devo Platform making it easy to query and analyze the relevant data from Workspace, view it in the pre-configured Activeboards, or customize them to enable Enterprise IT and Cybersecurity teams to make impactful data-driven decisions.
This collector will retrieve alerts on potential issues within your domain. Apps you develop can use Google’s Alert Center API to retrieve alerts in order to respond to them. Apps can also use the API to create and retrieve alert feedback. For example, a monitoring app could retrieve new alerts, prioritize them, and then notify members of your organization when action is needed. The collector processes the API responses and sends them to the Devo platform which then categorizes all data received on tables along rows and columns in your Devo domain.
Data source description
The Google Workspace (formerly G Suite) API generates account activities for these applications and sources. The collector process the Google API responses and send them to the Devo platform that will categorize all information received on tables along rows and columns on your Devo domain.
Google Workspace Alert Center
Listed in the table below are the alert sources, types, the data that Google Workspace classifies, and how the Devo platform manages it.
Alert source | Alert type | Devo tables | Available from |
---|---|---|---|
Domain wide takeout | Customer takeout initiated |
|
|
Gmail phishing | Malware reclassification |
|
|
Misconfigured whitelist |
|
| |
Phishing reclassification |
|
| |
Suspicious message reported |
|
| |
User reported phishing |
|
| |
User reported spam spike |
|
| |
Google identity | Leaked password |
|
|
Suspicious login |
|
| |
Suspicious login (less secure app) |
|
| |
Suspicious programmatic login |
|
| |
User suspended |
|
| |
User suspended (spam) |
|
|
|
User |
suspended (spam through relay) |
|
|
Google identity
|
|
User suspended (suspicious activity) |
|
|
| |
Google Operations | Google Operations |
|
|
Suspicious login (less secure app)
cloud.gsuite.alerts.suspicious_login_less_secure_app
|
| |
State Sponsored Attack | Government attack warning |
|
|
|
| |
Mobile device management | Device compromised |
|
|
|
Suspicious activity |
|
|
User suspended (spam through relay)
cloud.gsuite.alerts.user_suspended_spam_through_relay
|
| |
AppMaker Editor | AppMaker Default Cloud SQL setup |
|
|
|
Google Operations
|
| |
Security Center rules | Activity Rule |
|
|
State Sponsored Attack
Government attack warning
cloud.gsuite.alerts.government_attack_warning
Mobile device management
|
| |
Data Loss Prevention | Data Loss Prevention |
|
|
Suspicious activity
cloud.gsuite.alerts.suspicious_activity
AppMaker Editor
|
| |
Sensitive Admin Action | Super Admin Password Reset |
|
|
|
Security Center rules
Activity Rule
cloud.gsuite.alerts.activity_rules
For more information about sources and types, visit the G Suite Alert Center API documentation.
Setup
...
|
|
For more information about Sources and Types, visit Google Alert Center API.
Devo collector features
Feature | Details |
---|---|
Allow parallel downloading ( |
|
Running environments |
|
Populated Devo events |
|
Setup
The Google Workspace Alerts collector needs to be configured in the Google Cloud Platform APIs console and also in the Google Admin console.
...
Anchor | ||||
---|---|---|---|---|
|
Follow the next steps to create the Service Account that will be used to collect the alerts and enable the necessary API and scopes to use it.
Go to the Google Cloud Platform APIs console.
Go to the Library section.
Search Google Workspace Alert Center API in the search box.
Click Enable.
Go to the Credentials section (You can type credentials api services on the search box or choose the section from the left panel).
Then, click Manage Service Accounts.
Click Create Service Account and fill in the required fields (the optional steps can be omitted).
Click on the previously created Service Account and make sure you are in the DETAILS section.
Click on SHOW DOMAIN-WIDE DELEGATION, then enable the option called Enable Google Workspace Domain-wide Delegation. Click Save and copy the value in the Client ID box (this value will be used in the Assigning proper permissions to credentials section).
Once saved, go to KEYS section, click ADD KEY → Create new key and choose the JSON file type. Then, click CREATE (a .json file will be downloaded).
Rename the downloaded file to
credentials-gsuite-alerts.json
and move it to the collector credentials directory (<any_directory>/devo-collector/gsuite-alerts/credentials/
).
Anchor | ||||
---|---|---|---|---|
|
Now, you must be associate a scope to the previously created Client ID. Follow these steps to do it:
...
Go to the Google admin console.
From your Google Workspace domain’s Admin console, go to Main menu → Security → API Controls.
In the Domain wide delegation pane, select Manage Domain Wide Delegation.
Click Add new.
In the Client ID field, enter the service account's Client ID. You can find your service account's client ID in the Service accounts page.
In the OAuth scopes (comma-delimited) field, enter the next scope :
https://www.googleapis.com/auth/apps.alerts
Click Authorize.
...
Run the collector
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
Rw ui tabs macro | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration.
This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running. StructureThe following directory structure will be required as part of the setup procedure (it can be created under any directory):
Devo credentialsIn Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in Editing the config-gsuite-alerts.yaml fileIn the config-gsuite-alerts.yaml file, replace the
Download the Docker imageThe collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table:
Use the following command to add the Docker image to the system:
The Docker image can be deployed on the following services:
DockerExecute the following command on the root directory
Docker ComposeThe following Docker Compose file can be used to execute the Docker container. It must be created in the
To run the container using docker-compose, execute the following command from the
|
Disclaimer
The API limits the number of requests for your APIs Console project. The API project's maximum number of requests per second (project QPS) is 5 QPS and the maximum number of requests per day (project QPD) is 150,000 QPD across the account. If these limits are exceeded, the server returns an HTTP 503 status code.