HIGHCIS 4.1

Ensure default service account is not used

Instances should use custom service accounts instead of default compute SA.

Security Impact

Default service account has broad permissions including Editor role.

How to Remediate

Create custom service accounts with minimum required permissions.

Affected Resources

compute.googleapis.com/Instance

Compliance Frameworks

CIS GCP v1.3.0SOC 2NIST 800-53

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, NIST 800-53 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
gcp-compute-7
Service
Google Compute Engine
Category
Access Control
Severity
HIGH
CIS Benchmark
4.1

Automate This Check

TigerGate automatically scans your GCP environment for this and 79+ other security checks.

Start Free Trial