Skip to content
Integrations/Google Workspace (Directory)
Core Security Platforms

Use Google Workspace (Directory) As a Review-Ready Evidence Source

Pull evidence from Google Workspace (Directory), preserve source and collection history, and map the output directly to the controls reviewers ask about. Aurora automates recurring collection where the connector supports it and keeps export-based handoffs clean where it does not.

IdentityDirect connectionEvidence captureContinuous checksUpdates every 30 minutes2 mapped controls
Common coverage includes Break-glass accounts and Multi-factor authentication.
Supports recurring audits, buyer reviews, and renewal requests. We'll show what can run automatically and where export-based collection still makes sense.
Connector Summary
Best for
Continuous checks and evidence capture
Authentication
Oauth2 Service Account Domain Wide Delegation
Cadence
Every 30 minutes
Setup time
10 to 20 minutes
Framework coverage
Australian Energy Sector Cyber Security Framework (AESCSF) and 79 more
Imported execution-stage guidance
Frameworks
82
Preferred requirement mappings
964
Candidate requirement mappings
1,859
Auth: Oauth2 Service Account Domain Wide DelegationCollection: Integration ApiEvidence objects: technical_state_snapshot, sso_configuration
Exports & records
Artifacts reviewers recognize. Preview the structure before you share anything.
Scroll for artifact previews

Setup

Setup

A short path from connection to an exportable evidence bundle.

01
Connect Google Workspace (Directory)
Sign-in method: Oauth2 Service Account Domain Wide Delegation. Read-only, least-privilege access.
02
Confirm Evidence Sources and Cadence
Confirm evidence sources and set cadence (every 30 minutes).
03
Validate Capture (Read-Only Where Possible)
Validate evidence capture in read-only mode (where possible) before expanding workflows.
04
Map Evidence to Controls
Map captured artifacts to controls (2 mapped controls listed).
05
Bundle evidence when needed
Export an evidence bundle (ZIP) when you need an offline attachment. Aurora keeps the underlying source and timestamps so the work stays reusable.

Capture

What This Integration Captures

Evidence types and collection notes, based on the integration’s published resources.

What Aurora monitors
3 continuous checks
Multi factor authentication is enabled for all active human users • Multi factor authentication is enabled for all admin users
Evidence Aurora can collect
3 evidence types
User accounts • Groups and roles
How it stays current
Incremental updates every 30 minutes. Full refresh daily.
Checks update as new data is synced.
Checks
Automated checks Aurora can run
Checks map directly to common buyer requirements. Reviewers see the result as exportable evidence, not a screenshot.
Multi factor authentication is enabled for all active human users
Multi factor authentication is enabled for all admin users
At least 1 break-glass account exists and is monitored
Evidence
Evidence types collected
These evidence objects can be mapped to controls and exported as an evidence bundle or audit workbook snapshot.
User accountsGroups and rolesSecurity and access policies
Produces
  • Evidence objects with source details
  • Freshness and cadence status
  • Evidence bundle exports (plan-based)
Security Note
Read-only API, scoped credentials, and an audit trail for every sync.
Cadence Controls
Incremental updates every 30 minutes. Full refresh daily.
Permissions
Permissions and Scope
Aurora Command uses least-privilege, read-only access. If elevated scope is required, it is documented during setup so you know exactly what is being accessed.
https://www.googleapis.com/auth/admin.directory.user.readonlyhttps://www.googleapis.com/auth/admin.directory.group.readonly

Reviewers

Why It Matters for Reviewers

A few ways this reduces follow-ups during audits and buyer reviews.

  • Reduces evidence follow-ups by attaching system exports directly to answers.
  • Keeps timestamps explicit for audit windows.
  • Makes sampling easier through evidence bundles.

Frameworks

Controls and Frameworks Impacted

A quick sense of which frameworks this connector helps cover (based on mapped controls).

Australian Energy Sector Cyber Security Framework (AESCSF)
AESCSF
2 controls
Aurora Essentials (Baseline Control Set)
AURORA_ESS
2 controls
Australian Information Security Manual (ISM)
AUSTRALIAN_ISM
2 controls
Australian ISM for IRAP and ASD
AUSTRALIAN_ISM_IRAP
2 controls
BSI C5
BSI_C5
2 controls
CSA Cloud Controls Matrix (CCM) v4.1
CCM
2 controls
FDA 21 CFR Part 11 (Electronic Records; Electronic Signatures)
21CFR11
1 control
Anecdotes AI Framework (AAIF)
AAIF
1 control
Adobe Common Controls Framework (Adobe CCF)
ADOBE_CCF
1 control
Japan APPI — Act on the Protection of Personal Information (APPI)
APPI
1 control
Australia Privacy Act 1988 — Australian Privacy Principles (APPs) & Notifiable Data Breaches (NDB)
AU_PRIVACY
1 control
AWS Foundational Technical Review (FTR) Validation Checklist
AWS_FTR
1 control

Common questions

Google Workspace (Directory) Integration Questions

Short answers to common evaluation questions.

Does this require admin access?
It depends on the evidence you choose to capture. We'll confirm required permissions during setup.
Can we control cadence?
Yes. In eligible plans, cadence is configurable.
Can we export evidence if a reviewer asks?
Yes. Export evidence bundles for offline attachments, or give reviewers structured access through Trust Center. Aurora keeps the source and timestamps so work stays reusable between reviews.
Live walkthrough
Want to Confirm Evidence Coverage for Google Workspace (Directory)?
Tell us about your evidence gap, audit question, or framework target. We'll show what can be automated, what stays manual, and how to share it in a controlled way.
15-minute walkthrough. No obligation. We'll show Aurora applied to your workflow and show the exact outputs. (No compliance guarantees.)