Google Cloud (GCP)
上線身份與存取Google Cloud (GCP) 連接器——唯讀、無代理
Audits your Google Cloud (GCP) project security posture — project IAM (service-account keys, primitive-role sprawl, inactive and external principals, public bindings), enabled APIs and API-key restrictions, Cloud Audit Log coverage and retention, VPC firewall exposure (SSH/RDP open to the internet), and public Cloud Storage buckets. Read-only.
我們掃描的內容
- Project IAM policy bindings, service accounts and their key metadata, API keys and their restrictions, and enabled APIs (never resource data or key material)
- Audit-log configuration and retention, VPC firewall rules, and Cloud Storage bucket IAM policies (never object contents)
唯讀監控——除非您開啟自動修復並單獨授予寫入存取權,否則 Google Cloud (GCP) 資料中的任何內容都不會改變。
安全發現結果
每次 Google Cloud (GCP) 掃描時會執行 17 個偵測規則。每個發現結果都附帶純文字說明、背後的證據和修復步驟。
- CRITICALPublic exposure
GCP IAM binding grants access to all (public) users
- CRITICALPublic exposure
GCP Cloud Storage bucket is public
- HIGHStale access
GCP service-account key not rotated in over 90 days
- HIGHOver permission
GCP service account has a project-level Owner/Editor role
- HIGHExternal access
External user has access to the GCP project
- HIGHMisconfig
GCP API key has no application (referrer/IP) restriction
- HIGHPublic exposure
GCP firewall allows SSH/RDP from the entire internet
- MEDIUMOver permission
GCP user has a project-level Owner/Editor primitive role
- MEDIUMMisconfig
GCP organization does not enforce MFA (2-Step Verification)
- MEDIUMMisconfig
GCP project has an overly-permissive API enabled
- MEDIUMStale access
GCP API key not rotated in over 90 days
- MEDIUMMisconfig
GCP Cloud Audit Logs are disabled for a service
- MEDIUMMisconfig
Vertex AI is enabled with no vertexai.* org policy
- MEDIUMMisconfig
Vendor AI-training data-contribution posture
- LOWStale access
GCP service account has been inactive for over 90 days
- LOWMisconfig
GCP log retention is shorter than 30 days
- LOWMisconfig
GCP project still has the legacy default network
如何連接 Google Cloud (GCP)
步驟 1
登入 8200.dev 或建立帳戶
步驟 2
前往連接器 → Google Cloud (GCP)
步驟 3
按一下「連接」並透過 Google Cloud (GCP) 的同意畫面授權
步驟 4
8200.dev 自動掃描——結果在幾分鐘內出現
在幾分鐘內連接您的第一個來源——免費、唯讀、無銷售電話。