/google-cloud-filestore-auditing

name: google-cloud-filestore-auditing
metadata:
  version: "1.0.3"
  category: Storage
description: >-
  Audits Filestore instances on Google Cloud 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.

Filestore Auditing Skill

This skill enables autonomous agents to audit, evaluate, and report the disaster recovery, security access governance, and architectural reliability posture of Filestore fleets across Google Cloud 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 Filestore MCP Server (`file.googleapis.com/mcp`):

• **`roles/mcp.toolUser`**: Required to execute MCP tools (`list_instances`,

`get_instance`, `list_backups`, `get_backup`, `create_backup`).

4. Cloud Authentication Setup

Authenticate the runtime environment using the appropriate method for your execution context:

• **CLI Execution (`gcloud`)**:

    gcloud auth login

• **Application SDKs & Scripts**:

    gcloud auth application-default login

• **Automated Services & Service Accounts**:

    export GOOGLE_APPLICATION_CREDENTIALS="/path/to/service-account-key.json"

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:

    gcloud beta billing projects describe {project_id}

Quick Start

1. Ensure `gcloud` is installed. See [gcloud installation guide](https://docs.cloud.google.com/sdk/docs/install-sdk.md.txt) if needed. 2. Authenticate your environment:

    gcloud auth login
    gcloud auth application-default login

3. Set the target project context and verify an active billing account is attached:

    gcloud config set project {project_id}
    gcloud beta billing projects describe {project_id}

4. Configure a well-supported default region (e.g., `us-central1`). See official [region availability documentation](https://cloud.google.com/about/locations):

    gcloud config set compute/region us-central1

5. Verify required service APIs are enabled:

    gcloud services enable file.googleapis.com --quiet

6. Run fleet discovery and backup inventory (see "Discovery & Read Operations" below). 7. Evaluate findings against the audit rules matrix and render the executive scorecard and inventory table. 8. If unprotected instances are identified, present baseline backup creation commands and prompt the user for confirmation.

Usage Attribution

**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you MUST read and follow the instructions in [Usage Attribution](references/attribution.md).

Conceptual & Informational Queries (CRITICAL)

For purely conceptual, educational, or architectural questions (e.g., *"What is Physical Zone Isolation (PZI) in Filestore?"*, *"What is the difference between PZI and PZS?"*, *"Why is NO_ROOT_SQUASH dangerous?"*, *"Explain Filestore backup architecture"*):

• **Rule**: Answer immediately in a single turn using pre-trained knowledge

and the definitions in this `SKILL.md` file:

• **Physical Zone Isolation (`PZI` / `satisfiesPzi`)**: Ensures a zonal

resource's physical hardware is confined to an isolated physical failure domain within a datacenter so localized hardware failures do not cross zones.

• **Physical Zone Separation (`PZS` / `satisfiesPzs`)**: Ensures

multi-zone or regional primary and replica nodes are hosted in physically distinct, independent datacenter facilities so a facility-wide outage cannot affect both copies.

• **Constraint**: **Do NOT call ANY tools whatsoever** (do NOT call

`read_file` on `references/`, `run_command`, MCP tools, or API requests) for purely conceptual questions—respond directly right away.

Handling "No-Command" Constraints & Evaluations (CRITICAL)

If the user prompt contains constraints like *"Do not execute commands"*, *"without executing"*, or *"read-only"*:

• **Rule**: **Strictly avoid calling the `run_command` tool** to execute any

shell, python, or `gcloud` commands.

• **Discovery Hierarchy**:

1. Always read [Usage Attribution](references/attribution.md) whenever outputting or recommending `gcloud` commands (such as backup creation or export r