After you configure the connection between the AlienApp for G Suite for a deployed USM Anywhere Sensor and your G Suite environment, the predefined log collection jobs perform scheduled queries for eventsAny traffic or data exchange detected by AT&T Cybersecurity products through a sensor, or through external devices such as a firewall.. When USM Anywhere collects and analyzes the first of these events, the G Suite dashboards are available in the DASHBOARDS menu (according to the types of collected events).
Note: Currently, the AlienApp for G Suite supports the connection of one G Suite account per USM Anywhere Sensor. If you have more than one G Suite account that you want to monitor in USM Anywhere, you must configure each for a different Sensor.
As a Google administrator, you must create a new project in your Google Developers console and create a service account in the API Console to support server-to-server interactions. For more information about server-to-server authentication in Google, refer to https://developers.google.com/accounts/docs/OAuth2ServiceAccount.
As you complete the following set up tasks, you must collect these items to complete the integration with the AlienApp for G Suite:
- Unique ID for the service account
- User email for the login that you use to create the account
- Private key file, which is saved to your computer when you create the service account and the key
Important: You must have administrative privileges to configure G Suite for integration with the AlienApp for G Suite. Ask your Google administrator for these privileges.
First, create a service account. See the G Suite Administrator Help for instructions. Pay attention to these specifics:
- In Step 2: Enable the APIs, enable the Admin SDK.
In Step 3: Create the service account, do the following
- For service account permissions, select the role Project > Owner (item 6 in the article).
For key type, select P12 and click Create (item 8 in the article).
This produces a dialog box informing that the private key has been saved to your computer. It also displays the password for the private key.
Click the icon to copy the password and then store it in a secure location.
Note: This password is not required for AlienApp configuration, but you might need it in the future to manage the service account.
- Skip item 11-16 in the article and continue with the rest of this document.
Then, delegate domain-wide authority to the service account you just created. See the Google Identity Platform Guide for instructions.
In the One or More API Scopes field (step 6), enter https://www.googleapis.com/auth/admin.reports.audit.readonly and click Authorize.
Important: Adding the Client and Scopes in the G Suite console can be subject to a propagation time, which could be up to two hours. If you use the Check Connections tool for your G Suite platform in CloudMigrator, it may not be successful immediately.
After you create the new service account in G Suite and enable the Admin SDK, you must configure the connection within USM Anywhere.
Important: Adding the Client and Scopes in the G Suite console can be subject to a propagation time, which could be up to two hours. The AlienApp for G Suite connection configuration might not be successful immediately if these resources are not yet accessible.
To enable the AlienApp for G Suite
- In USM Anywhere, go to Data Sources > Integrations.
Click the AlienApps tab.
On the AlienApps page, click the Google G Suite tile.
If you have more than one deployed USM Anywhere Sensor, select the Sensor that you want to use for the enabled AlienApp.
USM Anywhere AlienApps operate through a deployed Sensor and use APIs to integrate with the connected third-party technology. Select the Sensor that can access the integration endpoint. The HTTPS connections to the API will originate from this Sensor.
- Click the Credentials tab.
- In the Service Client ID field, enter the Unique ID for the Google service account you created.
In the User Email field, enter the G Suite Admin user email address.
Note: The G Suite Admin user is the account you use to sign in to your Google Admin console. You cannot use the email address of the service account created for this integration.
In the Private Key field, click Choose File and select the downloaded P12 private key file for the Google service account you created.
- Click Save Credentials.