Compliance assessment
All listed controls, with their descriptions from CIS Google Cloud Platform Foundation Benchmark v1.2.0
Identity and Access Management15
1.1Ensure that corporate login credentials are used1.2Ensure that multi-factor authentication is enabled for all non-service accounts1.3Ensure that Security Key Enforcement is enabled for all admin accounts1.4Ensure that there are only GCP-managed service account keys for each service account1.5Ensure that Service Account has no Admin privileges1.6Ensure that IAM users are not assigned the Service Account User or Service Account Token Creator roles at project level1.7Ensure user-managed/external keys for service accounts are rotated every 90 days or less1.8Ensure that Separation of duties is enforced while assigning service account related roles to users1.9Ensure that Cloud KMS cryptokeys are not anonymously or publicly accessible1.10Ensure KMS encryption keys are rotated within a period of 90 days1.11Ensure that Separation of duties is enforced while assigning KMS related roles to users1.12Ensure API keys are not created for a project1.13Ensure API keys are restricted to use by only specified Hosts and Apps1.14Ensure API keys are restricted to only APIs that application needs access1.15Ensure API keys are rotated every 90 days
Logging and Monitoring12
2.1Ensure that Cloud Audit Logging is configured properly across all services and all users from a project2.2Ensure that sinks are configured for all log entries2.3Ensure that retention policies on log buckets are configured using Bucket Lock2.4Ensure log metric filter and alerts exist for project ownership assignments/changes2.5Ensure that the log metric filter and alerts exist for Audit Configuration changes2.6Ensure that the log metric filter and alerts exist for Custom Role changes2.7Ensure that the log metric filter and alerts exist for VPC Network Firewall rule changes2.8Ensure that the log metric filter and alerts exist for VPC network route changes2.9Ensure that the log metric filter and alerts exist for VPC network changes2.10Ensure that the log metric filter and alerts exist for Cloud Storage IAM permission changes2.11Ensure that the log metric filter and alerts exist for SQL instance configuration changes2.12Ensure that Cloud DNS logging is enabled for all VPC networks
Networking10
3.1Ensure that the default network does not exist in a project3.2Ensure legacy networks do not exist for a project3.3Ensure that DNSSEC is enabled for Cloud DNS3.4Ensure that RSASHA1 is not used for the key-signing key in Cloud DNS DNSSEC3.5Ensure that RSASHA1 is not used for the zone-signing key in Cloud DNS DNSSEC3.6Ensure that SSH access is restricted from the internet3.7Ensure that RDP access is restricted from the Internet3.8Ensure that VPC Flow Logs is enabled for every subnet in a VPC Network3.9Ensure no HTTPS or SSL proxy load balancers permit SSL policies with weak cipher suites3.10Ensure Firewall Rules for instances behind Identity Aware Proxy (IAP) only allow the traffic from Google Cloud Loadbalancer (GCLB) Health Check and Proxy Addresses
Virtual Machines11
4.1Ensure that instances are not configured to use the default service account4.2Ensure that instances are not configured to use the default service account with full access to all Cloud APIs4.3Ensure "Block Project-wide SSH keys" is enabled for VM instances4.4Ensure oslogin is enabled for a Project4.5Ensure 'Enable connecting to serial ports' is not enabled for VM Instance4.6Ensure that IP forwarding is not enabled on Instances4.7Ensure VM disks for critical VMs are encrypted with Customer-Supplied Encryption Keys (CSEK)4.8Ensure Compute instances are launched with Shielded VM enabled4.9Ensure that Compute instances do not have public IP addresses4.10Ensure that App Engine applications enforce HTTPS connections4.11Ensure that Compute instances have Confidential Computing enabled
Storage2
Cloud SQL Database Services - MySQL Database3
Cloud SQL Database Services - PostgreSQL Database16
6.2.1Ensure that the 'log_checkpoints' database flag for Cloud SQL PostgreSQL instance is set to 'on'6.2.2Ensure 'log_error_verbosity' database flag for Cloud SQL PostgreSQL instance is set to 'DEFAULT' or stricter6.2.3Ensure that the 'log_connections' database flag for Cloud SQL PostgreSQL instance is set to 'on'6.2.4Ensure that the 'log_disconnections' database flag for Cloud SQL PostgreSQL instance is set to 'on'6.2.5Ensure 'log_duration' database flag for Cloud SQL PostgreSQL instance is set to 'on'6.2.6Ensure that the 'log_lock_waits' database flag for Cloud SQL PostgreSQL instance is set to 'on'6.2.7Ensure 'log_statement' database flag for Cloud SQL PostgreSQL instance is set appropriately6.2.8Ensure 'log_hostname' database flag for Cloud SQL PostgreSQL instance is set appropriately6.2.9Ensure 'log_parser_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'6.2.10Ensure 'log_planner_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'6.2.11Ensure 'log_executor_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'6.2.12Ensure 'log_statement_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'6.2.13Ensure that the 'log_min_messages' database flag for Cloud SQL PostgreSQL instance is set appropriately6.2.14Ensure 'log_min_error_statement' database flag for Cloud SQL PostgreSQL instance is set to 'Error' or stricter6.2.15Ensure that the 'log_temp_files' database flag for Cloud SQL PostgreSQL instance is set to '0' (on)6.2.16Ensure that the 'log_min_duration_statement' database flag for Cloud SQL PostgreSQL instance is set to '-1' (disabled)
Cloud SQL Database Services - SQL Server7
6.3.1Ensure 'external scripts enabled' database flag for Cloud SQL SQL Server instance is set to 'off'6.3.2Ensure that the 'cross db ownership chaining' database flag for Cloud SQL SQL Server instance is set to 'off'6.3.3Ensure 'user connections' database flag for Cloud SQL SQL Server instance is set as appropriate6.3.4Ensure 'user options' database flag for Cloud SQL SQL Server instance is not configured6.3.5Ensure 'remote access' database flag for Cloud SQL SQL Server instance is set to 'off'6.3.6Ensure '3625 (trace flag)' database flag for Cloud SQL SQL Server instance is set to 'off'6.3.7Ensure that the 'contained database authentication' database flag for Cloud SQL on the SQL Server instance is set to 'off'
Cloud SQL Database Services4
6.4Ensure that the Cloud SQL database instance requires all incoming connections to use SSL6.5Ensure that Cloud SQL database instances are not open to the world6.6Ensure that Cloud SQL database instances do not have public IPs6.7Ensure that Cloud SQL database instances are configured with automated backups