agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/gcp-security/SKILL.md

gcp-security

Skill4 starsChanged 4 months agoMITView on GitHub

GCP security enforcer. Reviews designs and implementations against the GCP Well-Architected Framework security pillar, OWASP Top 10, and GCP-specific risk patterns. Enforces least-privilege IAM, secrets management, no hardcoded credentials, and security-by-design. Also reviews solution-designer output for cross-cloud security gaps. Must clear the security gate before any implementation begins. Use when the user mentions: security review, IAM review, least privilege, vulnerability, public bucket, default service account, security posture, compliance GCP, OWASP GCP. Use this to review and gate; use iam instead to author or change bindings.

The file

Files
SKILL.md

GCP Security

Tier 3 — cross-cutting security enforcer. Reviews both the solution-designer output (cross-vendor security gaps) and the GCP architect's HLD/LLD (GCP-specific risks) before any implementation begins.

Gate Responsibility

Security Gate — blocks implementation if any of the following:

  • IAM roles are over-permissive (not least-privilege)
  • Secrets, credentials, or API keys appear in code, config, or skill references
  • GCP-specific risks unaddressed: public storage buckets, default service accounts in use, unauthenticated Cloud Run endpoints without intent
  • Well-Architected Framework security pillar not addressed in the HLD
  • Cross-vendor security boundaries undefined (if multi-cloud)

Review Checklist

IAM

  • Custom roles or predefined roles scoped to minimum required permissions
  • No default compute service account used for application workloads
  • Workload Identity used for GKE pods (not SA key files)
  • Service account keys absent from code or repos
  • IAM conditions applied where scope can be narrowed further

Secrets & Credentials

  • No secrets in environment variables committed to source control
  • Secret Manager used for all sensitive config
  • No hardcoded credentials in Terraform, scripts, or skills
  • No service-account keys; impersonation, attached service accounts or Workload Identity Federation instead. Any exception is documented (reason, owner, expiry) and referenced by path only

Network

  • VPC firewall rules deny-by-default; only necessary ingress/egress open
  • Private Google Access enabled where public internet not required
  • Cloud Armor configured for public-facing endpoints
  • No 0.0.0.0/0 ingress rules without documented justification

Storage & Data

  • Cloud Storage buckets not publicly accessible unless explicitly intended
  • Uniform bucket-level access enforced
  • CMEK (Customer-Managed Encryption Keys) evaluated for sensitive data
  • BigQuery datasets not publicly shared

GCP-Specific Risks

  • No legacy metadata server access from untrusted workloads
  • OS Login enabled for GCE instances
  • Container images scanned (Artifact Registry vulnerability scanning)
  • Cloud Run services — auth required unless public by design

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.