Soru

Zorluk: OrtaIdentity and Access Management (IAM) Roles and Resource Hierarchy

An enterprise cloud security architect is documenting how Google Cloud IAM calculates effective access permissions when a service account attempts to read an object stored in a Cloud Storage bucket. Arrange the steps of the IAM policy evaluation process in the correct chronological order from initial API request submission to the final access determination.

  1. 1The service account issues an authenticated API request targeting the specific Cloud Storage object.
  2. 2IAM evaluates policy bindings attached at the Organization root level.
  3. 3IAM evaluates inherited policy bindings attached along the Folder hierarchy path.
  4. 4IAM evaluates policy bindings defined directly on the hosting Project node.
  5. 5IAM evaluates resource-level IAM policies on the bucket and calculates the union of all granted permissions to issue an access decision.

Cevap

The correct sequence evaluates IAM permissions top-down along the resource hierarchy: Request initiation -> Organization root evaluation -> Folder hierarchy evaluation -> Project level evaluation -> Resource policy evaluation and final union calculation.
Google Cloud IAM evaluates permissions top-down starting from the API request receipt, proceeding from the Organization root down through Folders, Project, and finally Resource-level policies. Effective access is determined by combining all permissions granted along the hierarchy path.

Adım Adım Çözüm

1
Submit API Request
The API call containing identity context and desired permission is received by Google Cloud services.
Evaluation begins only after an authenticated call specifies a target operation.
2
Evaluate Organization Root Policies
Permissions granted at the top-level Organization node are gathered.
GCP IAM permission inheritance starts at the top ancestor of the resource tree.
3
Evaluate Folder Nodes
Permissions granted across parent folders and sub-folders are gathered.
Permissions inherit down through intermediate folder nodes in the resource hierarchy.
4
Evaluate Project Node
Permissions granted at the Project level are gathered.
Project-level policy bindings apply to all resources residing within that project.
5
Evaluate Resource Policies & Determine Access
Effective permissions across all levels are combined to make an allow or deny authorization decision.
IAM permissions are additive down the hierarchy, with explicit deny policies taking precedence.

Anahtar Kavram

GCP IAM Resource Hierarchy Evaluation and Permission Inheritance
Bu soruyu puanla