Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
GCP compliance evidence collection for auditclaw-grc. 12 read-only checks across Cloud Storage, firewall, IAM, logging, KMS, DNS, BigQuery, Compute, and Clou...
GCP compliance evidence collection for auditclaw-grc. 12 read-only checks across Cloud Storage, firewall, IAM, logging, KMS, DNS, BigQuery, Compute, and Clou...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Companion skill for auditclaw-grc. Collects compliance evidence from Google Cloud Platform projects using read-only API calls. 12 checks | Viewer + Security Reviewer roles only | Evidence stored in shared GRC database
Read-only access: Requires 6 read-only IAM roles (Viewer, Security Reviewer, Cloud SQL Viewer, Logging Viewer, DNS Reader, Cloud KMS Viewer). No write/modify permissions. Credentials: Uses standard GCP credential chain (GOOGLE_APPLICATION_CREDENTIALS or gcloud auth). No credentials stored by this skill. Dependencies: Google Cloud SDK packages (all pinned in requirements.txt) Data flow: Check results stored as evidence in ~/.openclaw/grc/compliance.sqlite via auditclaw-grc
GCP credentials configured (gcloud auth application-default login or service account JSON) GCP_PROJECT_ID environment variable set pip install -r scripts/requirements.txt auditclaw-grc skill installed and initialized
"Run GCP evidence sweep": Run all checks, store results in GRC database "Check GCP storage compliance": Run Cloud Storage checks "Check GCP firewall rules": Run firewall ingress checks "Check GCP IAM compliance": Run IAM service account checks "Check GCP logging status": Verify audit logging configuration "Check GCP KMS keys": Review KMS key rotation "Show GCP integration health": Last sync, errors, evidence count
All evidence is stored in the shared GRC database at ~/.openclaw/grc/compliance.sqlite via the auditclaw-grc skill's db_query.py script. To run a full evidence sweep: python3 scripts/gcp_evidence.py --db-path ~/.openclaw/grc/compliance.sqlite --all To run specific checks: python3 scripts/gcp_evidence.py --db-path ~/.openclaw/grc/compliance.sqlite --checks storage,firewall,iam
CheckWhat It VerifiesstorageUniform bucket-level access, public access preventionfirewallNo unrestricted ingress (0.0.0.0/0) to SSH/RDP/alliamService account key rotation (90 days), SA admin privilege restrictionloggingAudit logging enabled (all services), log export sink existskmsKMS key rotation period <= 90 daysdnsDNSSEC enabled on public zonesbigqueryNo public dataset access (allUsers/allAuthenticatedUsers)computeNo default service account with cloud-platform scopecloudsqlSSL enforcement, no public IP with 0.0.0.0/0
Each check produces evidence items stored with: source: "gcp" type: "automated" control_id: Mapped to relevant SOC2/ISO/HIPAA controls description: Human-readable finding summary file_content: JSON details of the check result
roles/viewer roles/iam.securityReviewer roles/cloudsql.viewer roles/logging.viewer roles/dns.reader roles/cloudkms.viewer All checks use read-only access only.
When a user asks to set up GCP integration, guide them through these steps:
gcloud iam service-accounts create auditclaw-scanner --display-name="AuditClaw Scanner"
Grant these 6 read-only roles: for role in roles/viewer roles/iam.securityReviewer roles/cloudsql.viewer roles/logging.viewer roles/dns.reader roles/cloudkms.viewer; do gcloud projects add-iam-policy-binding PROJECT_ID \ --member=serviceAccount:auditclaw-scanner@PROJECT_ID.iam.gserviceaccount.com \ --role=$role done
gcloud iam service-accounts keys create key.json --iam-account=auditclaw-scanner@PROJECT_ID.iam.gserviceaccount.com
Set environment variables: GOOGLE_APPLICATION_CREDENTIALS=/path/to/key.json GCP_PROJECT_ID=your-project-id
Run: python3 {baseDir}/scripts/gcp_evidence.py --test-connection The exact roles are documented in scripts/gcp-roles.json. Show with: python3 {baseDir}/../auditclaw-grc/scripts/db_query.py --action show-policy --provider gcp
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.