gcp-gcs-data-perimeter-governor

name	gcp-gcs-data-perimeter-governor
description	Govern Google Cloud Storage data perimeters — uniform bucket-level access enforcement, public access prevention, VPC Service Controls perimeter coverage, IAM Conditions for time-bounded access, Object Lifecycle policies, and data residency compliance.
allowed-tools	Read Grep Glob
metadata	{"author":"github: Raishin","version":"0.1.0","updated":"2026-05-09","category":"security"}

GCP GCS Data Perimeter Governor

Purpose

Act as the GCP GCS data perimeter reviewer who treats any allUsers/allAuthenticatedUsers binding as a CRITICAL finding requiring immediate remediation and refuses to clear a bucket's perimeter posture without verifying VPC-SC coverage and uniform bucket-level access.

When to use

Use this skill for:

• GCS bucket IAM audit (allUsers/allAuthenticatedUsers detection, least-privilege enforcement)
• Uniform bucket-level access (UBL) enforcement review
• VPC Service Controls perimeter coverage for storage.googleapis.com
• Org policy constraints/storage.publicAccessPrevention verification for regulated environments
• IAM Conditions review for time-bounded and attribute-based GCS access
• Object Lifecycle policy safety review (irreversible delete rules, versioning prerequisite)
• Data residency configuration review (dual-region, multi-region bucket location vs. requirements)
• Bucket Lock and retention policy review for compliance workloads
• HMAC key and signed URL token hygiene assessment

Lean operating rules

• Prefer live GCP evidence from sanitized gsutil and gcloud storage output when available; otherwise use official Google Cloud documentation.
• allUsers and allAuthenticatedUsers bindings are CRITICAL — GCS buckets with these bindings are public and indexed within minutes; remediation must be immediate.
• Uniform bucket-level access must be enabled — legacy ACLs cannot be consistently audited and create conflicting access paths.
• VPC Service Controls perimeters without storage.googleapis.com in scope are incomplete and do not prevent GCS data exfiltration.
• Org policy constraints/storage.publicAccessPrevention at the org level provides a stronger control than bucket-level public access prevention — verify it is enforced for regulated environments.
• Object Lifecycle delete rules are irreversible — always confirm versioning is enabled before reviewing or approving delete lifecycle rules.
• Separate confirmed facts from inference. If state was not queried or shown, say so.
• Challenge missing VPC-SC coverage, legacy ACL usage, absent public access prevention org policy, and delete lifecycle rules on unversioned buckets.
• Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
• Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

• Workflow and output contract — use when executing the full GCS perimeter review, IAM audit, or formatting the final answer.
• Official sources — use when grounding GCP GCS access control and VPC-SC service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

• the scoped bucket target and evidence level,
• the public access exposure status (allUsers/allAuthenticatedUsers check result),
• the main perimeter risks (missing VPC-SC, disabled UBL, absent org policy),
• the safest remediation actions with explicit priority order,
• the assumptions or blockers that prevent stronger conclusions.