Individual skill

gcp-cloud-pentesting

GCP offensive testing — principal and project identification, org/folder/project IAM inheritance, service accounts, Cloud Asset Inventory, storage, secrets, KMS, Compute, Cloud Run and Cloud Functions, GKE boundaries, Cloud Build, and Artifact Registry with gcloud as the baseline

internal/tools/skills/data/cloud-security/gcp-cloud-pentesting/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,329
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# GCP Cloud Pentesting

## Purpose
Full GCP offensive methodology: from project IDs/buckets discovered black-box to mapped IAM inheritance, service-account identity, and resource access with a validated credential. Modern tooling only — gcloud, Cloud Asset Inventory, Policy Analyzer, and native IAM/resource APIs. (Forseti is retired: the upstream project is archived; its inventory concepts live on in Cloud Asset Inventory.)

## Entry Conditions
- Black-box: project IDs, `storage.googleapis.com` buckets, Firebase configs, or `run.app`/`cloudfunctions.net` endpoints from `cloud-attack-surface-discovery`
- Credentialed: service-account JSON, OAuth token, or ADC credential from `cloud-credential-abuse`

## Discovery Signals
- Project IDs: bucket names (`gs://<project>-*`), Firebase `projectId`, API error messages
- Service-account emails in configuration, IAM bindings, metadata leaks
- `*.googleapis.com` endpoints in client code
Back to top