G Suite alert centre
In the last few days, Google began rolling out the G Suite Alert Center to all G Suite customers. It provides extensive visibility into threats detected in G Suite tenants. In this post, we explore how G Suite administrators and security teams can leverage security orchestration automation and response (SOAR) platforms, like Tines, to centralise, triage and respond to alerts from the G Suite Alert Center.
What is the G Suite Alert Center?
When Google announced the launch of G Suite Alert Center it was with the stated aim of providing “a single, comprehensive view of essential notifications, alerts, and actions across G Suite”. Admins can manage alerts more efficiently through the unified view that the alert center provides. Additionally, it provides insights that help them assess their organization’s exposure to internal and external security issues at the domain and user levels.
Out of the box, G Suite Alert Center includes the following types of alerts:
- Device compromised
- Suspicious device activity
- User-reported phishing
- Attacks caused by bad whitelists
- Google Operations
- Spike in user reported spam
- Suspicious message reported
- Phishing message detected post-delivery
- Malware message detected post-delivery
- Government-backed attack warning
- Suspicious login
- Suspicious login from a less secure app
- User suspended
- User suspended due to suspicious activity
- Leaked password
- User suspended for spamming
- User suspended for spamming through relay
Accessing G Suite Alert Center
When logged into the G Suite Admin portal click “Security” and then chose “Alert Center”.
On the next page, the G Suite Alert center displays all the alerts for your G Suite tenant. From this view, G Suite admins can view details of the alerts. Additionally, G Suite customers on the Enterprise plan can perform remediation actions from within the G Suite Alert Center itself. Later in this post, we’ll show how Tines can be used to automate the same remediation actions in real time regardless of your G Suite plan.
Tines and the G Suite Alert Center
The alerts produced by the G Suite Alert Center provide valuable insight into potential security issues in G Suite tenants. However, the alerts are at their most valuable when, rather than being treated in isolation, we include them as part of a larger threat detection and response effort. By automating interaction with the G Suite Alert Center through Tines, we can use the alerts as both a threat source and as source of additional context when investigating other incident types. By using Tines to integrate with the G Suite Alert Center, we’re also centralising our response and aligning it to existing security response processes.
Connecting Tines to the G Suite Alert Center
In a previous blog post, we described the steps required to connect Tines to G Suite, we’ll use a similar method to connect to the Alert Center.
Enabling the G Suite Alert Center API
Follow these steps, based on those from developers.google.com to set up the Alert Center API:
- Create a service account that can be used by your G Suite application (see instructions on creating a service account).
- Download the key file, it will be a JSON file containing your private key and other sensitive information.
- Enable the Alert Center API (for instructions, see section on enabling and disabling APIs).
- Grant domain-wide access to the application, and therefore domain-wide delegation of authority to the associated service account (note that the 3-legged OAuth won’t work for the Alert Center API):
- Go to your G Suite domain’s Admin console (see instructions on signing in to your Admin console).
- Click Security.
If you don’t see Security listed, select More controls at the bottom of the page, then click Security.
- Click Advanced settings.
- From the Authentication section, click Manage API client access.
- In the Client Name field, type the Client ID for the service account. This can be taken from the key file, in our example, this is a long number starting with 116.
- In the One or More API Scopes field, enter the list of scopes that your application should be granted access to. In this case, type the following value: https://www.googleapis.com/auth/apps.alerts.
- Click Authorize.
Creating a Tines Credential
Before Tines can connect to the G Suite Alert Center API, we need to configure a JWT credential type. For detailed instructions on how to use JWTs with G Suite, see here.
Use the information from your service account key file to fill in the required JWT fields. When you’re finished, the credential page will resemble the below.
After saving the credential, we can begin automating interaction with the G Suite Alert Center.
G Suite Alert Center Automation Story
Get a G Suite Auth Token
To begin orchestrating and automating activities in the G Suite Alert Center, we first need to retrieve an auth token. This will allow us interact with the Alert Center API. We’ll do this with a HTTP Request agent, configured as shown below:
When this agent runs, it will emit an event containing a bearer token which we will use in subsequent agents.
Get All Alerts from G Suite Alert Center
The G Suite Alert Center API is available at https://alertcenter.googleapis.com. We’ll use the list call in a HTTP Request Agent to get all alerts associated with our G Suite tenant.
When this agent runs and there are alerts in our tenant, the G Suite Alert Center API will return an array of alerts.
Get alerts in last five minutes
Additionally, we can use filters to find alerts that match certain criteria. For example, the below HTTP Request Agent uses the date liquid filter to find alerts created in the last 5 minutes (current time in seconds – 300 seconds, converted into Google’s preferred Timestamp format: RFC 3339).
Get alert details from the G Suite Alert Center API
We can also use a HTTP Request Agent configured as below to find details about a specific alert, using its ID.
A sample automation story
In the above automation story, we’ve created a blueprint for getting started with automatic handling of G Suite Alert Center threats. To begin, at five minute intervals, we fetch all alerts. Next, an Event Transformation Agent is used to explode the array of alerts so each alert can be treated individually. Then we use several Trigger agents to emit events based on the alert type. Finally, we create an incident ticket based on the alert’s priority (this could be in Jira or another case management system) and add the alerts details to the ticket.
From here, it would be trivial add additional threat intelligence sources or automate data gathering log searches in a SIEM. We could also automate remediation activity like blocking malicious senders, quarantining devices and resetting compromised accounts all without requiring human intervention.
When considering threat detection tools for their technology stack, it’s easy for security operation teams and security operation centers to overlook assets like the G Suite Alert Center. However, as enterprises continue their move to the cloud, these non-traditional sources of threat intelligence and security alerts are becoming increasingly valuable.
By using security automation and orchestration tools like Tines to respond to threats surfaced by data sources similar to the G Suite Alert Center, an enterprise incident response team can ensure their standardized workflow is followed. Additionally, their detection and response is smarter, quicker and less prone to human-error.