Skip to main content

Overview

The Google Devices integration enables ThreatAware to collect device information from your Google Workspace environment, providing visibility into device inventory and security posture across your Google-managed infrastructure.
Connection Method: OAuth 2.0 with Domain-Wide Delegation Setup Time: 15 minutes Access Required: Google Workspace Super Admin account

Data collected

The Google Devices integration provides:
  • Device inventory and status
  • Device compliance information
  • Operating system details
  • Security posture indicators

Use cases

Device Inventory

Maintain an accurate inventory of all Google-managed devices in your organisation

Compliance Monitoring

Monitor device compliance with security policies

Security Posture

Track the security health of Google-managed devices

Access Control

Validate device credentials and access rights

Setup instructions

1

Access ThreatAware Integration

Begin the integration setup in ThreatAware:
  • Log in to the ThreatAware dashboard
  • Navigate to Settings → Integrations
  • Use the search bar to find Google
  • Click Connect to open the configuration wizard
2

Log in to Google Admin Console

Access Google Workspace administrative tools:
  • Go to Google Admin Console
  • Sign in with a Super Admin account
  • Navigate to Security settings in the left sidebar
3

Enable Domain-Wide Delegation

Configure API permissions for ThreatAware:
  • In Google Admin Console, select Security
  • Scroll down and click API Controls
  • Under Domain-Wide Delegation, select Manage Domain-Wide Delegation
  • This enables the OAuth flow required for ThreatAware integration
4

Add ThreatAware as API Client

Register ThreatAware as an authorised API client:
  • Click Add New to authorise a new client
  • Enter the Client ID provided by ThreatAware support
  • In the OAuth scopes field, enter the following scope (comma-separated if multiple):
  • Click Authorize to grant ThreatAware access
Only the read-only scope is required. Never grant additional permissions beyond what is specified.
5

Configure ThreatAware with Admin Email

Complete the integration in ThreatAware:
  • Return to the ThreatAware integration window
  • Enter the email address of the Super Admin account used in Google Admin Console
  • Click the Authorize button to complete the setup
  • ThreatAware will initiate OAuth authentication
6

Verify Connection

Confirm successful integration:
  • Check that the integration status in ThreatAware shows Active
  • Wait 5-10 minutes for initial data synchronization
  • Verify Google device data appears in the ThreatAware dashboard

Required credentials

Field Name: Google Workspace Super Admin Email Type: String Description: Email address of a Google Workspace Super Admin accountThis account must have:
  • Super Admin privileges in Google Workspace
  • Access to the Google Admin Console
  • Permission to manage API access and domain-wide delegation
Example: admin@company.com
Field Name: OAuth Scope Type: String Description: The API permission scope required for device accessRequired scope:
This read-only scope allows ThreatAware to:
  • View device inventory
  • Read device compliance status
  • Access device metadata
Field Name: ThreatAware Client ID Type: String Description: The Client ID provided by ThreatAware support for OAuth registrationThis ID uniquely identifies ThreatAware as an authorised application in Google Workspace.

Verification and testing

After setup, verify the integration is working correctly:
  1. Check Integration Status
    • Navigate to Settings → Integrations in ThreatAware
    • Confirm Google shows Active status
    • Check the last sync timestamp
  2. Verify Data Collection
    • Wait 5-10 minutes for initial data synchronization
    • Search the ThreatAware dashboard for Google device data
    • Verify device inventory matches Google Admin Console
  3. Test Queries
    • Create a test query filtering by Google-managed devices
    • Verify device names and metadata match your Google Workspace inventory

Troubleshooting

Symptoms: Integration fails with scope error or shows limited permissionsSolutions:
  • Double-check the scope entry in Google Admin Console exactly matches:
  • Verify there are no extra spaces or special characters
  • If the scope was entered incorrectly, remove the client and add it again with the correct scope
Symptoms: OAuth authorization fails or returns permission denied errorSolutions:
  • Ensure the email address is for a Super Admin account
  • Verify the account has access to Google Admin Console
  • Confirm Domain-Wide Delegation is enabled
  • Try authorising again with a different Super Admin account
  • Check that the Client ID in Google Admin Console matches ThreatAware’s Client ID
Symptoms: Integration shows active but no Google devices appear in ThreatAwareSolutions:
  • Verify you have Google-managed devices enrolled in Google Workspace
  • Check that the OAuth scope is correctly configured
  • Ensure the Super Admin account has access to view devices
  • Wait up to 15 minutes for initial data synchronization
  • Review Google Admin Console to confirm devices are managed by Google
Symptoms: Integration fails to authenticate or frequently disconnectsSolutions:
  • Verify your network allows HTTPS (443) outbound to Google APIs
  • Check that googleapis.com is accessible from your ThreatAware instance
  • Temporarily disable any corporate proxy or VPN and test
  • Contact Google Cloud support if API access is blocked

Additional resources

Google Admin Console

Access your Google Workspace administration dashboard

Google API Documentation

Official Google OAuth 2.0 and API documentation

Domain-Wide Delegation Guide

Google’s guide to setting up domain-wide delegation

ThreatAware Support

Contact ThreatAware support for integration assistance

Best practices

Use a Dedicated Admin Account
  • Create a dedicated Super Admin account specifically for ThreatAware integration
  • Use a different account for day-to-day administration
  • This improves security and audit trail tracking
Monitor API Access
  • Periodically review API access in Google Admin Console
  • Check for any suspicious API activity logs
  • Revoke access immediately if the integration is no longer needed
Keep Scope Minimal
  • Never grant additional scopes beyond the read-only device scope
  • Review Google’s documentation to understand what each scope provides
  • Request only the permissions necessary for your use case