An enterprise architecture team needs to prevent developers across all Google Cloud projects from granting IAM permissions to external Google accounts outside the corporate Cloud Identity directory. This governance control must apply automatically across all existing and newly created folders and projects within the organization. Which architectural approach should the team implement to meet this requirement?
- Define an Organization Policy at the organization root node enforcing the Domain Restricted Sharing constraint (constraints/iam.allowedPolicyMemberDomains) with your Cloud Identity customer ID.Cevap
- BAssign the primitive Owner IAM role to security administrators at the top-level folder so they can audit and manually remove external policy bindings.
- CConstruct a VPC Service Controls perimeter encompassing all projects to prevent external identities from accessing resource APIs.
- DGrant developers the Service Account User role across the resource hierarchy so they can delegate identity management exclusively through service accounts.
Cevap
Enforce an Organization Policy at the organization root using the Domain Restricted Sharing constraint (`constraints/iam.allowedPolicyMemberDomains`) configured with the enterprise Cloud Identity customer ID.
The Domain Restricted Sharing constraint (`constraints/iam.allowedPolicyMemberDomains`) enforced at the Organization node establishes a strict boundary for IAM member additions. By specifying the corporate Cloud Identity customer ID, Google Cloud prevents any user from binding IAM roles to accounts outside the specified identity domain across all existing and future projects.
Adım Adım Çözüm
Anahtar Kavram
Organization Policies - Domain Restricted Sharing
Tahmini Süre:1m 30s