返回顶部
a

auditclaw-gcp

GCP compliance evidence collection for auditclaw-grc. 12 read-only checks across Cloud Storage, firewall, IAM, logging, KMS, DNS, BigQuery, Compute, and Cloud SQL.

作者: admin | 来源: ClawHub
源自
ClawHub
版本
V 1.0.2
安全检测
已通过
532
下载量
0
收藏
概述
安装方式
版本历史

auditclaw-gcp

# AuditClaw GCP 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** ## Security Model - **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 ## Prerequisites - 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 ## Commands - "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 ## Usage 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 ``` ## Check Categories (9 files, 12 findings) | Check | What It Verifies | |-------|-----------------| | **storage** | Uniform bucket-level access, public access prevention | | **firewall** | No unrestricted ingress (0.0.0.0/0) to SSH/RDP/all | | **iam** | Service account key rotation (90 days), SA admin privilege restriction | | **logging** | Audit logging enabled (all services), log export sink exists | | **kms** | KMS key rotation period <= 90 days | | **dns** | DNSSEC enabled on public zones | | **bigquery** | No public dataset access (allUsers/allAuthenticatedUsers) | | **compute** | No default service account with cloud-platform scope | | **cloudsql** | SSL enforcement, no public IP with 0.0.0.0/0 | ## Evidence Storage 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 ## Required IAM Roles - `roles/viewer` - `roles/iam.securityReviewer` - `roles/cloudsql.viewer` - `roles/logging.viewer` - `roles/dns.reader` - `roles/cloudkms.viewer` All checks use read-only access only. ## Setup Guide When a user asks to set up GCP integration, guide them through these steps: ### Step 1: Create Service Account ``` gcloud iam service-accounts create auditclaw-scanner --display-name="AuditClaw Scanner" ``` ### Step 2: Grant IAM Roles 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 ``` ### Step 3: Generate JSON Key ``` gcloud iam service-accounts keys create key.json --iam-account=auditclaw-scanner@PROJECT_ID.iam.gserviceaccount.com ``` ### Step 4: Configure Credentials Set environment variables: - GOOGLE_APPLICATION_CREDENTIALS=/path/to/key.json - GCP_PROJECT_ID=your-project-id ### Step 5: Verify Connection 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

标签

skill ai

通过对话安装

该技能支持在以下平台通过对话安装:

OpenClaw WorkBuddy QClaw Kimi Claude

方式一:安装 SkillHub 和技能

帮我安装 SkillHub 和 auditclaw-gcp-1776419950 技能

方式二:设置 SkillHub 为优先技能安装源

设置 SkillHub 为我的优先技能安装源,然后帮我安装 auditclaw-gcp-1776419950 技能

通过命令行安装

skillhub install auditclaw-gcp-1776419950

下载 Zip 包

⬇ 下载 auditclaw-gcp v1.0.2

文件大小: 18.93 KB | 发布时间: 2026-4-17 19:46

v1.0.2 最新 2026-4-17 19:46
- Added homepage and source fields for improved skill metadata.
- Updated install metadata to specify pip installation from scripts/requirements.txt.
- Listed "GOOGLE_APPLICATION_CREDENTIALS" as a required environment variable for clarity.
- No changes to functionality or code; documentation and metadata improvements only.

Archiver·手机版·闲社网·闲社论坛·羊毛社区· 多链控股集团有限公司 · 苏ICP备2025199260号-1

Powered by Discuz! X5.0   © 2024-2025 闲社网·线报更新论坛·羊毛分享社区·http://xianshe.com

p2p_official_large
返回顶部