Agent skill · google
google-cloud-filestore-auditing
Audits Google Cloud Filestore instances across projects for disaster recovery readiness (missing or stale backups), security access governance (overly permissive NFS export rules, 0.0.0.0/0 exposure, missing ROOT_SQUASH), and reliability compliance (Physical Zone Isolation PZI and Physical Zone Separation PZS). Use when assessing storage health posture, auditing NFS export permissions, identifying unprotected file shares, or validating zone failure domains. Don't use for Cloud Storage buckets, Persistent Disk, or NetApp Volumes.
What it needs
About 7k tokens when loaded.
What this skill does
Google Cloud Filestore Auditing Skill This skill enables autonomous agents to audit, evaluate, and report the disaster recovery, security access governance, and architectural reliability posture of Google Cloud Filestore fleets across GCP projects. Prerequisites / IAM Requirements & Permissions Before executing this skill, the runtime principal (user account or Service Account) must possess the following IAM roles and granular permissions on the target GCP project(s): 1. Audit Operations (Read-Only Assessment) Requires the roles/file.viewer role, which provides: file.instances.list: Enumerate Filestore instances across project locations. file.instances.get: Inspect instance configuration, NFS export rules, IP ranges, squash mode, and PZI/PZS isolation status. file.backups.list: Enumerate existing backups across regions. file.backups.get: Inspect backup timestamps, source instance URIs, and status. 2. Remediation Operations (Backup Creation) Requires the roles/file.editor (or roles/file.admin) role, which provides: file.backups.create: Create on-demand baseline backups for unprotected instances. file.operations.get: Monitor long-running backup creation operations. 3. MCP Tool Invocation If invoking capabilities via the Google Cloud Filestore MCP Server (file.googleapis.com/mcp): roles/mcp.toolUser: Required to execute MCP tools (listinstances, getinstance, listbackups, getbackup, createbackup). 4. Cloud Authentication Setup Authenticate the runtime environment using the appropriate method for your execution context: CLI Execution (gcloud): Application SDKs & Scripts: Automated Services & Service Accounts: 5. Billing Account Attachment Active Billing Required: The target GCP project must have an active Cloud Billing account attached. Filestore instances and backup operations require active billing. Verify billing status with: Quick Start 1. Ensure gcloud is installed. See gcloud installation guide if needed. 2. Authenticate your environment: 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-filestore-auditing