Benchmark: CC6.1.3
Description
Entity uses Sprinto, a continuous monitoring system, to alert the security team to update the access levels of team members whose roles have changed.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-gcp-compliance
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select CC6.1.3.
Run this benchmark in your terminal:
powerpipe benchmark run gcp_compliance.benchmark.soc_2_2017_cc_6_1_3
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run gcp_compliance.benchmark.soc_2_2017_cc_6_1_3 --share
Controls
- Alloy DB clusters should use customer-managed encryption key (CMEK) for encryption
- Ensure that a default customer-managed encryption key (CMEK) is specified for all BigQuery Data Sets
- Ensure that all BigQuery Tables are encrypted with Customer-managed encryption key (CMEK)
- Ensure VM disks for critical VMs are encrypted with Customer-Supplied Encryption Keys (CSEK)
- Ensure 'Block Project-wide SSH keys' is enabled for VM instances
- Ensure that Compute instances have Confidential Computing enabled
- Ensure that Compute instances do not have public IP addresses
- Ensure that dataproc cluster is encrypted using customer-managed encryption key
- Ensure that Service Account has no Admin privileges
- Ensure that IAM users are not assigned the Service Account User or Service Account Token Creator roles at project level
- Ensure that Separation of duties is enforced while assigning service account related roles to users
- Ensure that Cloud KMS cryptokeys are not anonymously or publicly accessible
- Ensure KMS encryption keys are rotated within a period of 90 days
- Ensure that Separation of duties is enforced while assigning KMS related roles to users
- Check if BigQuery datasets are publicly readable
- Check if Cloud Storage buckets have Bucket Only Policy turned on
- Ensure 'skip_show_database' database flag for Cloud SQL Mysql instance is set to 'on'
- Ensure Instance IP assignment is set to private
- Ensure that the 'contained database authentication' database flag for Cloud SQL on the SQL Server instance is set to 'off'
- Ensure that the 'cross db ownership chaining' database flag for Cloud SQL SQL Server instance is set to 'off'
- Check if Cloud SQL instances are world readable
- Ensure that Cloud Storage buckets used for exporting logs are configured using bucket lock
- Ensure that Cloud Storage bucket is not anonymously or publicly accessible