Secure your Google Workspace surface
Two-step verification gaps, OAuth app grants against corporate data, and oversharing outside the domain. We don’t connect to Google Workspace to collect evidence for its own sake — we connect to secure it, and the compliance artefacts follow from that work.
Book a Demo[01] What This Surface Exposes
Where Google Workspace goes wrong
Google Workspace goes wrong through OAuth grants: users authorise third-party apps against corporate mail and Drive without any admin involvement.
- Users and admins without two-step verification enforced
- Third-party OAuth applications granted broad Drive and Gmail scopes by individual users
- Files and shared drives shared publicly or with anyone-with-the-link
- Super Admin accounts used for daily work rather than reserved for administration
- Forwarding rules and delegation set on mailboxes without oversight
[02] What We Secure
What we watch, catch and fix on Google Workspace
On Google Workspace we inventory OAuth grants by scope and data reach, since this is the most common quiet exfiltration path here.
- Two-step verification coverage measured per user, with admins treated as a separate and stricter population
- OAuth grant inventory by scope and data reach, since this is the most common quiet data exfiltration path here
- External sharing detected against data classification rather than reported as a raw count
- Admin account usage patterns reviewed, because a super admin reading email daily is a standing risk
- Mail forwarding and delegation monitored as a compromise indicator
[03] Where It Lands
Where Google Workspace lands in your registers
Directory data drives your access reviews directly: reviewers see live entitlements rather than a spreadsheet exported three weeks ago, and leaver revocation is verified against the systems themselves. The asset register records each identity provider as a critical dependency, and the risk register carries the concentration risk that comes with it — because if this tier fails, everything behind it fails with it.
[04] How We Engage
On Google Workspace specifically
On Google Workspace, we revoke risky OAuth grants, remove unauthorised forwarding rules, and correct external sharing under agreed authority. Enforcing two-step verification across the domain and separating admin accounts we plan and drive with you.
Platform licence
Everything you need to find and fix it yourself, with no ceiling on the depth of the answer.
- Every connected tool monitored for misconfiguration and drift, with findings mapped to the assets and risks they affect
- Remediation guidance that tells you what is wrong and exactly how to fix it — however deep or awkward the issue is. We are engineers running a security company, so the answer is the real one, not a link to vendor documentation
- Assets, access reviews, and risk register populated from the tools themselves rather than from spreadsheets
- Unlimited integrations and unlimited users, with anything missing built within two weeks
Managed service
Every tool you connect through Konfirmity comes under our care, with our team doing the work.
- Continuous misconfiguration and drift monitoring across every connected tool, watched by our analysts rather than by a dashboard waiting for you
- Incident response led by us, with containment coordinated with your team
- Remediation performed directly wherever you have granted us the authority to act — and where we cannot act, we project-manage the fix to completion rather than handing you a ticket
- Decision support on the tools themselves: where something is failing you on capability or costing more than it returns, we will tell you, and help you replace it
[05] Google Workspace FAQs
What Google Workspace access does Konfirmity need?
Konfirmity needs a service account with domain-wide delegation limited to read-only admin SDK, Drive metadata and audit report scopes. We read sharing metadata, not document contents. Every scope maps to a specific control, and we walk you through that mapping before you authorise it.
Do you read the contents of our files and email?
No. Konfirmity reads metadata — who a file is shared with, whether a link is public, whether forwarding is configured — not the content itself. Classification is driven by location, sharing posture and your own labelling rather than by us reading documents.
Okta
Microsoft Entra ID
Auth0
JumpCloud
1Password