Control: 4.3 Ensure 'Block Project-Wide SSH Keys' Is Enabled for VM Instances
Description
It is recommended to use Instance specific SSH key(s) instead of using common/shared project-wide SSH key(s) to access Instances.
Project-wide SSH keys are stored in Compute/Project-meta-data. Project wide SSH keys can be used to login into all the instances within project. Using project-wide SSH keys eases the SSH key management but if compromised, poses the security risk which can impact all the instances within project. It is recommended to use Instance specific SSH keys which can limit the attack surface if the SSH keys are compromised.
Remediation
From Console
- Go to the
VM instances
page by visiting: https://console.cloud.google.com/compute/instances. It will list all the instances in your project. - Click on the name of the Impacted instance.
- Click
Edit
in the toolbar. - Under SSH Keys, go to the
Block project-wide SSH keys
checkbox. - To block users with project-wide SSH keys from connecting to this instance, select
Block project-wide SSH keys
. - Click
Save
at the bottom of the page. - Repeat steps for every impacted Instance.
From Command Line
To block project-wide public SSH keys, set the metadata value to TRUE
:
gcloud compute instances add-metadata <INSTANCE_NAME> --metadata block- project-ssh-keys=TRUE
Default Value
By Default Block Project-wide SSH keys
is not enabled.
Usage
Run the control in your terminal:
powerpipe control run gcp_compliance.control.cis_v300_4_3
Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run gcp_compliance.control.cis_v300_4_3 --share
SQL
This control uses a named query:
compute_instance_block_project_wide_ssh_enabled