📝 Google GCE Instance is configured to use the Default Service Account 🟢

• Contextual name: 📝 Instance is configured to use the Default Service Account 🟢
• ID: /ce/ca/google/compute-engine/instance-use-default-service-account
• Located in: 📁 Google GCE

Flags

• 🟢 Policy with categories
• 🟢 Policy with type
• 🟢 Production policy

Our Metadata

• Policy Type: COMPLIANCE_POLICY
• Policy Category:
  • SECURITY

Similar Policies

• Cloud Conformity
  • Check for Instances Associated with Default Service Accounts

Logic

• 🧠 prod.logic.yaml 🟢
  • 📕 Google GCE Instance
  • 🔌 Google GCE Instance ServiceAccount Link - object.extracts.yaml
  • 🔌 Google GCE Instance - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

It is recommended to configure your instance to not use the default Compute Engine service account because it has the Editor role on the project.

Rationale

When a default Compute Engine service account is created, it is automatically granted the Editor role (roles/editor) on your project which allows read and write access to most Google Cloud Services. This role includes a very large number of permissions. To defend against privilege escalations if your VM is compromised and prevent an attacker from gaining access to all of your project, you should either revoke the Editor role from the default Compute Engine service account or create a new service account and assign only the permissions needed by your instance. To mitigate this at scale, we strongly recommend that you disable the automatic role grant by adding a constraint to your organization policy.

The default Compute Engine service account is named [PROJECT_NUMBER]-compute@developer.gserviceaccount.com.

Audit

From Google Cloud Console

1. Go to the VM instances page by visiting: https://console.cloud.google.com/compute/instances.

... see more

Remediation

Open File

Remediation

From Google Cloud Console

1. Go to the VM instances page by visiting: https://console.cloud.google.com/compute/instances.
2. Click on the instance name to go to its VM instance details page.
3. Click STOP and then click EDIT.
4. Under the section API and identity management, select a service account other than the default Compute Engine service account. You may first need to create a new service account.
5. Click Save and then click START.

From Google Cloud CLI

1. Stop the instance:

        gcloud compute instances stop <INSTANCE_NAME>

2. Update the instance:

        gcloud compute instances set-service-account <INSTANCE_NAME> --service-account=<SERVICE_ACCOUNT>

3. Restart the instance:

        gcloud compute instances start <INSTANCE_NAME>

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS GCP v3.0.0 → 💼 4.1 Ensure That Instances Are Not Configured To Use the Default Service Account - Level 1 (Automated)			1
💼 Cloudaware Framework → 💼 Secure Access			43