Domain restricted sharing is an organisation-level Google Cloud policy that limits which domains can be granted IAM access. It does not revoke existing permissions, but it blocks new role assignments to unapproved domains. Security teams use it to prevent a compromised external account from expanding its access inside a project.
What Domain Restricted Sharing Does
Domain restricted sharing is an organisation-level Google Cloud guardrail that narrows who can receive new IAM grants. It is designed to stop access expansion to unapproved external domains, which makes it a policy control rather than a revocation mechanism. The key security value is limiting where trust can spread after an account or project has been exposed.
That distinction matters operationally: existing bindings remain in place, so the control is strongest when it is paired with periodic access review and a clear inventory of who already has access. It reduces the chance that a compromised external principal can be granted fresh permissions inside the organisation.
How the Control Works in Google Cloud
The policy is set at the organisation level and applies to new IAM role assignments that target domain identities outside the approved list. In practice, it creates a boundary around who can be added to project or resource access lists, helping enforce a default-deny approach for external collaboration.
Because it operates at assignment time, it is especially useful where multiple teams manage projects independently. A central policy can prevent one project owner from inadvertently extending access to an unmanaged tenant domain or a partner domain that has not been approved for use.
Security Benefits and Common Failure Modes
Its main benefit is containment. If an external account is compromised, the attacker cannot use that account to gain additional permissions through ordinary sharing workflows unless the destination domain is already permitted. That limits one common path from account compromise to broader project access.
The main failure mode is assuming it is a cleanup tool. It does not remove access that already exists, and it does not replace least privilege, conditional access design, or periodic entitlement review. Organisations can still carry excessive legacy grants even when the policy is enabled.
Where It Fits in Cloud Access Governance
Domain restricted sharing fits best as a preventive policy in a broader Google Cloud governance model. It is most effective when combined with tight project ownership, controlled external collaboration, and review of any exceptions that must be allowed for business reasons.
It also helps align access design with data perimeter thinking. If a project handles sensitive data, restricting which external domains can be granted IAM roles reduces the chance that sharing decisions drift beyond the intended trust boundary. For a broader view of how this fits into Google Cloud policy design, see the Google Cloud Organization Policy Guide. For perimeter-oriented cloud controls across providers, the Cloud Data Perimeter Guide is the closer companion reference.
Risk and Threat Considerations
Domain restricted sharing reduces one route for privilege expansion, but it does not protect against already-granted access, overly broad internal roles, or malicious activity that uses legitimate permissions once access has been obtained. The control is strongest against new sharing abuse, not against standing exposure.
Failure mechanism: An attacker with a compromised external identity, or an insider making a risky sharing decision, cannot add fresh IAM bindings to an unapproved domain, but any pre-existing access remains exploitable.
Impact: The policy can prevent lateral expansion of access across domains, limiting blast radius and reducing the odds that a single external compromise turns into wider project compromise or data exposure.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST CSF 2.0 and CSA Cloud Controls Matrix set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | Restricts who can be granted access and under what conditions. |
| AC-6 — Least Privilege | Supports minimising access so domain sharing cannot expand privileges unnecessarily. | |
| Recommendation — Enforce access approval rules that block IAM grants to unapproved domains. Review granted access so domain restrictions are paired with least-privilege entitlement design. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions and Authorization | Addresses limiting access and authorisation for users and external parties. |
| Recommendation — Limit external IAM assignments to approved domains and review exceptions regularly. | ||
| CSA Cloud Controls Matrix | IAM — Identity and Access Management | Cloud access governance control area covering identity and entitlement boundaries. |
| Recommendation — Apply IAM domain restrictions to prevent unapproved external access grants. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access Control | Defines rules for controlling access rights and their allocation. |
| Recommendation — Set and enforce access rules that prevent new grants to unapproved domains. | ||
Practitioner Guidance
Governance implication: Treat this as an approval boundary, not an entitlement cleanup feature. Set the allowed domain list deliberately, review exceptions, and make sure project owners understand that the policy blocks future grants but does not repair old ones.
What to watch for: If a team relies on frequent external collaboration, monitor where exceptions are needed and check whether the business process is drifting toward unmanaged sharing. The practical test is whether the policy supports a stable collaboration model rather than being bypassed informally.
Related resources from NHI Mgmt Group
- Why do cross-domain file-sharing controls fail so often?
- Why do admin teams need visibility into password sharing and domain breach signals?
- Why does report sharing in Microsoft Fabric create a data exposure risk even when the visible report looks restricted?
- Why do Azure permissions create risk even when domain controller access is restricted on-premises?
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