roles/file.viewer

• 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.

roles/file.editor

roles/file.admin

• file.backups.create

  : Create on-demand baseline backups for unprotected instances.

• file.operations.get

  : Monitor long-running backup creation operations.

file.googleapis.com/mcp

• roles/mcp.toolUser

  : Required to execute MCP tools (

  list_instances

  ,

  get_instance

  ,

  list_backups

  ,

  get_backup

  ,

  create_backup

  ).

• CLI Execution (

  gcloud

  ):
  bash

  gcloud auth login

• Application SDKs & Scripts:
  bash

  gcloud auth application-default login

• Automated Services & Service Accounts:
  bash

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

• 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:
  bash

  gcloud beta billing projects describe {project_id}

1. Ensure

   gcloud

   is installed. See gcloud installation guide if needed.
2. Authenticate your environment:
   bash

   gcloud auth login
   gcloud auth application-default login

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

   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:
   bash

   gcloud config set compute/region us-central1

5. Verify required service APIs are enabled:
   bash

   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.

• Rule: Answer immediately using pre-trained knowledge and the guidance in

  references/

  .
• Constraint: Do NOT execute external tool calls or API requests for basic conceptual queries.

• Rule: Strictly avoid calling the

  run_command

  tool to execute any shell, python, or

  gcloud

  commands.
• Discovery Hierarchy:
  1. First, check if Filestore MCP tools (

     list_instances

     ,

     list_backups

     ) are available and query them directly (these are API invocations, not shell command executions).
  2. If MCP tools are not present or cannot connect, search local reference markdown files (specifically the mock fleet definitions in

     references/zone-isolation-pzi-pzs.md

     ) for any mock instances or project details matching the request. (Do NOT attempt to read evaluation config files such as

     EVAL.yaml

     or

     EVAL.txtpb

     during evaluation runs as access is restricted and triggers anti-cheating timeouts).
  3. If no data is available in context or mock references, explain the audit evaluation formulas and provide the attributed

     gcloud

     commands the user should run.
• Mandatory User Confirmation Requirement: Even when the user prompt asks not to execute commands or asks only for audit recommendations, any response recommending backup remediation MUST STILL end with a clear confirmation prompt before execution (e.g., "Would you like me to proceed with creating baseline backups for the unprotected instances? Please confirm to proceed.").

• Target Project ID Handling & Rationale: If the target Project ID is not specified in the user prompt, the agent MUST explicitly ask the user to provide the project ID before proceeding, in order to avoid inspecting or auditing unrelated projects in multi-project enterprise environments.

1. Instances Discovery: Call

   list_instances(parent="projects/{project_id}/locations/-")

   .
2. Backups Discovery: Call

   list_backups(parent="projects/{project_id}/locations/-")

   .

1. Instances Discovery:
   bash

   CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-auditing)" \
   gcloud filestore instances list --project="{project_id}" --format="json"

2. Backups Discovery:
   bash

   CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-auditing)" \
   gcloud filestore backups list --project="{project_id}" --format="json"

   (Note: Do NOT pass

   --location=-

   to

   gcloud filestore backups list

   ; omitting the flag queries all regions across the project automatically).

1. Instances:

   GET https://file.googleapis.com/v1/projects/{project_id}/locations/-/instances

2. Backups:

   GET https://file.googleapis.com/v1/projects/{project_id}/locations/-/backups

• Match backups to instances using full canonical resource URIs (

  backup.sourceInstance == instance.name

  ).
• Unprotected Instance: If

  backup_count == 0

  , assign

  HIGH

  severity finding: "Instance has 0 backups on file share '{share_name}'. Disaster recovery is not configured."
• Stale Backup: If latest backup is older than SLA (default: 7 days), assign

  MEDIUM

  severity finding: "Latest backup is {days} days old (exceeds SLA threshold of 7 days)."
• Refer to

  references/backup-dr-governance.md

  for backup retention and SLA rules.

• Inspect

  fileShares[0].nfsExportOptions

  :
  • Open Network Exposure: If

    0.0.0.0/0

    ,

    0.0.0.0

    , or

    ::/0

    is present in

    ipRanges

    , assign

    CRITICAL

    severity (if

    accessMode: READ_WRITE

    ) or

    HIGH

    severity (if

    READ_ONLY

    ): "Export rule exposes share to 0.0.0.0/0 with accessMode='{access_mode}'."
  • Missing Root Squashing: If

    squashMode: NO_ROOT_SQUASH

    , assign

    CRITICAL

    severity (if world-exposed) or

    HIGH

    severity (for internal subnets): "Export rule has squashMode='NO_ROOT_SQUASH'. Remote root clients retain superuser UID 0 privileges."
  • Default Open VPC Export: If

    nfsExportOptions

    is empty, assign

    MEDIUM

    severity: "No explicit NFS export options configured. Share defaults to open client access within VPC with NO_ROOT_SQUASH."
• Refer to

  references/security-access-governance.md

  for export option configurations.

• Physical Zone Isolation (PZI): If

  satisfiesPzi: false

  , assign

  MEDIUM

  severity: "Instance does not satisfy Physical Zone Isolation (PZI)."
• Physical Zone Separation (PZS): If tier is

  REGIONAL

  or

  ENTERPRISE

  and

  satisfiesPzs: false

  , assign

  HIGH

  severity: "Enterprise/Regional tier instance does not satisfy Physical Zone Separation (PZS)."
• Performance Limits: Extract

  performanceLimits.maxWriteIops

  and

  performanceLimits.maxReadThroughputBps

  (convert to MB/s).
• Refer to

  references/zone-isolation-pzi-pzs.md

  for datacenter failure domain isolation standards.

references/audit-rules-matrix.md

• Grade F (🔴 CRITICAL RISK): $\ge 1$

  CRITICAL

  findings.
• Grade C (🟠 ELEVATED RISK): 0 Critical, but $\ge 1$

  HIGH

  findings.
• Grade B (🟡 MODERATE): 0 Critical/High, but $\ge 1$

  MEDIUM

  findings.
• Grade A (🟢 HEALTHY): 0 findings across all vectors.

Backup Protection Rate %

CLOUDSDK_METRICS_ENVIRONMENT="gcs-skills gcs-skills/1.0 (skill:google-cloud-filestore-auditing)" \
gcloud filestore backups create [INSTANCE]-backup-[DATE] \
    --project=[PROJECT_ID] \
    --instance=[INSTANCE] \
    --file-share=[SHARE] \
    [--instance-zone=[ZONE] | --instance-location=[REGION]] \
    --region=[BACKUP_REGION]

Confirmation Required: Would you like me to proceed with creating baseline backups for the unprotected instances? Please confirm to proceed.

• Security & Access Governance
• Disaster Recovery & Backup Governance
• Zone Isolation (PZI) & Reliability (PZS)
• Audit Rules & Scoring Matrix
• Standalone Python Audit Script