Your organization is accountable for how Workspace is configured inside your tenant. Google’s SOC 2 covers its service operations, but your audit tests admin settings such as MFA, privileged access, OAuth governance, and Drive sharing. Under the shared responsibility model, the customer owns configuration, monitoring, and evidence for those controls.
What Google’s SOC 2 does, and does not, cover
Google’s report speaks to the provider’s control environment, not your tenant’s day-to-day governance. That is why the customer-side audit question is really about how you operate the workspace you were given: who can administer it, which auth controls are enforced, how third-party apps are approved, and whether sharing and retention settings match policy.
The practical split is between provider assurance and tenant assurance. A vendor report can reduce the need to re-test Google’s underlying service operations, but it does not transfer your responsibility for settings that you can change, evidence you can produce, or exceptions you accept in your own environment.
For a deeper view of the scoping logic, see SOC 2 Guide, which covers trust services criteria, carve-outs, CUECs and access evidence.
Which controls usually remain with the customer
The controls auditors commonly expect you to own are the ones tied to your administrative choices and your users’ behaviour inside Google Workspace. That includes admin role design, MFA enforcement, privileged access review, OAuth app governance, Drive sharing restrictions, logging, alerting and evidence of periodic review. Those are not “Google controls” just because they run on Google’s platform.
Shared responsibility becomes visible in the evidence set. If your policy says super admin use must be tightly limited, you need the role assignments, the review cadence, the sign-in or admin activity logs and the decision trail for exceptions. If external sharing is restricted, you need the configuration state and the monitoring that proves it stayed that way.
NHIMG’s Google Workspace Security Guide is the natural companion when you need to map those admin settings to concrete hardening choices.
How to answer the auditor without overclaiming Google’s report
The clean answer is to separate inherited assurance from operated assurance. Google’s SOC 2 can support your vendor diligence, but your audit response still needs tenant-level evidence for the controls you configure, monitor and review. That means showing not only that the platform is assessed, but that your own administration, access governance and sharing model are consistent with policy.
When a control spans both parties, the safe approach is to identify the provider element, then the customer element, and treat the customer element as in scope unless the vendor contract or control design clearly removes it. For Workspace, that distinction matters because many audit findings arise from misconfiguration, overbroad admin rights, weak app trust decisions or unmanaged collaboration exposure, not from a failure in Google’s core service.
For audit execution, How to Read a SOC 2 Report Guide helps when you need to distinguish what the report supports from what your own evidence must still prove.
Risk and Threat Considerations
In Workspace, the main risk is assuming a strong vendor report covers tenant misconfiguration, when the most damaging exposures usually sit in admin roles, OAuth grants, external sharing and logging gaps. A well-audited provider does not stop a compromised or overprivileged tenant from leaking data, approving a malicious app or losing visibility into abuse.
Failure mechanism: Customer-owned settings can create a trust gap if access, app approval or sharing rules are too permissive, or if audit evidence is not retained long enough to reconstruct who changed what and when.
Impact: The organisation can fail its own control objectives even when Google’s service remains within scope for its own SOC 2 report, because the exposure is created by tenant operations, not provider operations.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
SOC 2 (AICPA) and ISO/IEC 27001:2022 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| SOC 2 (AICPA) | CC6.1 — Logical Access Security Software, Infrastructure, and Content | Workspace tenant access and admin governance are the customer-side controls auditors test. |
| CC7.2 — Change Management | Tenant configuration changes to sharing, admin roles and app access affect audit evidence and control operation. | |
| CC8.1 — Change Management for System Components | Workspace configuration changes create evidence and accountability obligations for the customer environment. | |
| Recommendation — Verify tenant-level access settings and evidence for the controls you operate. Track and approve Workspace setting changes that affect control effectiveness. Maintain change records for customer-managed Workspace settings and exceptions. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The question centers on who controls access settings inside the tenant versus the provider boundary. |
| A.5.23 — Information security for use of cloud services | Workspace is a cloud service where shared responsibility must be scoped between provider and customer. | |
| Recommendation — Define and enforce tenant access rules as customer-owned controls. Document customer responsibilities for cloud-service security settings and evidence. | ||
Practitioner Guidance
What to verify: Confirm which controls your organisation actually administers in the tenant, then tie each one to a named owner, a review cadence and a reproducible evidence source. If you cannot produce tenant-level evidence for MFA, admin roles, app grants or Drive sharing, treat that as an audit problem, not a vendor-report problem.
Decision rule: If the control is configurable in your Workspace tenant, assume customer responsibility unless you can show the vendor contract or shared-responsibility matrix says otherwise. If the control is purely inside Google’s service boundary, rely on Google’s report and avoid duplicating the test.
Practitioner takeaway: Google’s SOC 2 can reduce provider due diligence, but it never replaces your obligation to prove that tenant configuration, access governance and monitoring are operating as designed.
Related resources from NHI Mgmt Group
- SOC 2 (Service Organization Control 2)
- How should security teams implement Google Workspace controls for SOC 2 without relying on screenshots at audit time?
- Why do cloud customers still need their own controls even when the provider has a SOC 2 report?
- Who is accountable when access controls fail a SOC 2 review?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org