gcs-security-assessment

Assesses Google Cloud Storage security posture and detects toxic vulnerability combinations against SAIF.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill gcs-security-assessment-ricardolui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcs-security-assessment
Source: https://github.com/ricardolui/gcp-custom-agent-skills/tree/main/gcs-security-assessment
Command: npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill gcs-security-assessment-ricardolui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Manually auditing Google Cloud Storage buckets and projects for security misconfigurations is slow and error-prone, and isolated alerts miss dangerous combinations of individually low-risk settings. This Skill gathers real telemetry from your GCP project, evaluates baseline controls, and identifies toxic combinations of vulnerabilities mapped to Google's Secure AI Framework (SAIF). ## Core Features & Use Cases - Telemetry-Grounded Assessment: Runs preflight permission checks, then collects bucket- and object-level signals from Storage Insights BigQuery datasets plus project-level posture (org policies, VPC-SC, audit logs, Model Armor). - Toxic Combination Detection: Correlates multiple signals to flag critical exposures, such as a public bucket holding ML training data with no CMEK, no VPC-SC, and no audit logging. - SAIF-Aligned Reporting: Classifies bucket sensitivity (SDP, tags, or inferred), modulates severity, and produces a structured remediation report referencing SAIF risk categories. - Use Case: Ask the agent to assess a GCP project before deploying an AI workload; it verifies credentials, discovers Storage Insights datasets, evaluates UBLA/TLS/HMAC/audit-log controls, and outputs prioritized findings with fixes. ## Quick Start Ask the agent to run a security assessment on your GCP project by providing the project ID, for example: assess the security posture of project my-gcp-project.

Frequently Asked Questions about gcs-security-assessment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security assessment on a Google Cloud Storage project?

Provide your GCP project ID and invoke the skill; it runs a preflight check for credentials and Storage Insights, then gathers telemetry and evaluates baseline controls and toxic combinations. If Storage Insights is unavailable, it falls back to a project-level posture report.

What is a toxic combination in GCS security?

A toxic combination is a set of individually low-risk misconfigurations that together create critical exposure, such as public access on a bucket storing ML training data with no CMEK, no VPC-SC perimeter, and no audit logging. The skill correlates multiple telemetry signals to detect these scenarios.

Does the GCS security assessment work without Storage Insights?

Yes. When Storage Insights or its BigQuery dataset is unavailable, the assessment degrades to project_only scope, evaluating org policies, VPC-SC, audit logs, and Model Armor via the project-level script, and recommends enabling Storage Insights to unlock bucket-level analysis.

What permissions are needed for the GCS security assessment?

Application Default Credentials via gcloud are required. Optional permissions include storageinsights.datasetConfigs.list, BigQuery dataViewer and jobUser, accesscontextmanager.policies.list, and resourcemanager.projects.getIamPolicy; missing optional permissions mark specific signals as unknown rather than stopping the run.

Why does the assessment report VPC-SC status as unknown?

This happens when the caller lacks the accesscontextmanager.policies.list permission, so the perimeter check cannot be verified. The skill reports the status as UNKNOWN consistently across the report instead of assuming the perimeter is configured or missing.