Ensure block project-wide SSH keys is enabled
Instances should block project-wide SSH keys for granular access control.
Security Impact
Project-wide SSH keys grant access to all instances in the project.
How to Remediate
Enable block-project-ssh-keys metadata on sensitive instances.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Google Compute Engine resources across your GCP projects every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS GCP v1.3.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-compute-9
- Service
- Google Compute Engine
- Category
- Access Control
- Severity
- MEDIUM
- CIS Benchmark
- 4.3
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free Trial