Vulnerabilities findings

Rapid Vulnerability Detection, Security Health Analytics, and Web Security Scanner detectors generate vulnerabilities findings that are available in Security Command Center. When they are enabled in Security Command Center, integrated services, like VM Manager, also generate vulnerability findings.

Your ability to view and edit findings is determined by the Identity and Access Management (IAM) roles and permissions you are assigned. For more information about IAM roles in Security Command Center, see Access control.

Detectors and compliance

This section describes the mapping between supported detectors and the best effort mapping to relevant compliance standards.

CIS Benchmarks

Security Command Center supports the following versions of the CIS Benchmarks for Google Cloud Platform Foundation:

• CIS Google Cloud Computing Foundations Benchmark v1.2.0 (CIS Google Cloud Foundation 1.2)
• CIS Google Cloud Computing Foundations Benchmark v1.1.0 (CIS Google Cloud Foundation 1.1)
• CIS Google Cloud Computing Foundations Benchmark v1.0.0 (CIS Google Cloud Foundation 1.0)

The CIS Google Cloud Foundation 1.2, 1.1, and 1.0 mappings have been reviewed and certified by the Center for Internet Security for alignment with CIS Google Cloud Computing Foundations Benchmark v1.2.0, v1.1.0, and v1.0.0, respectively.

While CIS 1.0 and CIS 1.1 are still supported, they will eventually be deprecated. We recommend that you use or transition to use the latest benchmark, CIS 1.2.

Some detectors are mapped to the CIS Google Kubernetes Engine (GKE) Benchmark v1.0.0 (CIS GKE 1.0). Support for this benchmark is limited and it should not be used as the basis for audits or reporting compliance.

Additional standards

Additional compliance mappings are included for reference and are not provided or reviewed by the Payment Card Industry Data Security Standard or the OWASP Foundation. You should refer to Payment Card Industry Data Security Standard 3.2.1 (PCI-DSS v3.2.1), OWASP Top Ten, National Institute of Standards and Technology 800-53 (NIST 800-53), and International Organization for Standardization 27001 (ISO 27001) for how to check for these violations manually.

This functionality is only intended for you to monitor for compliance controls violations. The mappings are not provided for use as the basis of, or as a substitute for, the audit, certification, or report of compliance of your products or services with any regulatory or industry benchmarks or standards.

For instructions on viewing and exporting compliance reports, see the Compliance section in Using the Security Command Center dashboard.

Security Health Analytics

Security Health Analytics detectors monitor a subset of resources from Cloud Asset Inventory (CAI), receiving notifications of resource and Identity and Access Management (IAM) policy changes. Some detectors retrieve data by directly calling Google Cloud APIs, as indicated in tables later on this page.

Security Health Analytics scans run in three modes:

• Batch scan: All detectors are scheduled to run for all enrolled organizations two or more times a day. Detectors run on different schedules to meet specific service level objectives (SLO). To meet 12- and 24-hour SLOs, detectors run batch scans every six hours or 12 hours, respectively. Resource and policy changes that occur in between batch scans are not immediately captured and are applied in the next batch scan. Note: Batch scan schedules are performance objectives, not service guarantees.

• Real-time scan: Supported detectors start scans whenever CAI reports a change in an asset's configuration. Findings are immediately written to Security Command Center.

• Mixed-mode: Some detectors that support real-time scans might not detect changes in real time in all supported assets. In those cases, configuration changes for some assets are captured immediately and others are captured in batch scans. Exceptions are noted in the tables on this page.

The following tables describe Security Health Analytics detectors, the assets and compliance standards they support, the settings they use for scans, and the finding types they generate. You can filter findings by detector name and finding type using the Security Command Center Vulnerabilities tab in the Google Cloud console.

For instructions on fixing issues and protecting your resources, see Remediating Security Health Analytics findings.

Note: Not all detectors are enabled by default. To turn on inactive detectors, see Enable and disable detectors.

API key vulnerability findings

The API_KEY_SCANNER detector identifies vulnerabilities related to API keys used in your cloud deployment.

Table 1. API key scanner

Detector	Summary	Asset scan settings	Compliance standards
API key APIs unrestricted Category name in the API: API_KEY_APIS_UNRESTRICTED	Finding description: There are API keys being used too broadly. To resolve this, limit API key usage to allow only the APIs needed by the application. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Retrieves the restrictions property of all API keys in a project, checking if any is set to cloudapis.googleapis.com. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.12 CIS GCP Foundation 1.1: 1.14 CIS GCP Foundation 1.2: 1.14
API key apps unrestricted Category name in the API: API_KEY_APPS_UNRESTRICTED	Finding description: There are API keys being used in an unrestricted way, allowing use by any untrusted app. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Retrieves the restrictions property of all API keys in a project, checking whether browserKeyRestrictions, serverKeyRestrictions, androidKeyRestrictions, or iosKeyRestrictions is set. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.11 CIS GCP Foundation 1.1: 1.13 CIS GCP Foundation 1.2: 1.13
API key exists Category name in the API: API_KEY_EXISTS	Finding description: A project is using API keys instead of standard authentication. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Retrieves all API keys owned by a project. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.10 CIS GCP Foundation 1.1: 1.12 CIS GCP Foundation 1.2: 1.12
API key not rotated Category name in the API: API_KEY_NOT_ROTATED	Finding description: The API key hasn't been rotated for more than 90 days. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Retrieves the timestamp contained in the createTime property of all API keys, checking whether 90 days have passed. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.13 CIS GCP Foundation 1.1: 1.15 CIS GCP Foundation 1.2: 1.15

Compute image vulnerability findings

The COMPUTE_IMAGE_SCANNER detector identifies vulnerabilities related to Google Cloud image configurations.

Table 2. Compute image scanner

Detector	Summary	Asset scan settings	Compliance standards
Public Compute image Category name in the API: PUBLIC_COMPUTE_IMAGE	Finding description: A Compute Engine image is publicly accessible. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Image Fix this finding	Checks the IAM allow policy in resource metadata for the principals allUsers or allAuthenticatedUsers, which grant public access. Batch scans: Every 6 hours Real-time scans: Yes

Compute instance vulnerability findings

The COMPUTE_INSTANCE_SCANNER detector identifies vulnerabilities related to Compute Engine instance configurations.

COMPUTE_INSTANCE_SCANNER detectors don't report findings on Compute Engine instances created by GKE. Such instances have names that start with "gke-", which users cannot edit. To secure these instances, refer to the Container vulnerability findings section.

Table 3. Compute instance scanner

Detector	Summary	Asset scan settings	Compliance standards
Confidential Computing disabled Category name in the API: CONFIDENTIAL_COMPUTING_DISABLED	Finding description: Confidential Computing is disabled on a Compute Engine instance. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks the confidentialInstanceConfig property of instance metadata for the key-value pair "enableConfidentialCompute":true. Assets excluded from scans: GKE instances, Serverless VPC Access, Compute Engine instances that are not of type N2D. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 4.11
Compute project wide SSH keys allowed Category name in the API: COMPUTE_PROJECT_WIDE_SSH_KEYS_ALLOWED	Finding description: Project-wide SSH keys are used, allowing login to all instances in the project. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks the metadata.items[] object in instance metadata for the key-value pair "key": "block-project-ssh-keys", "value": TRUE. Assets excluded from scans: GKE instances, Dataflow job, Windows instance Additional IAM permissions: roles/compute.Viewer Additional inputs: Reads metadata from Compute Engine Batch scans: Every 12 hours Real-time scans: No	CIS GCP Foundation 1.0: 4.2 CIS GCP Foundation 1.1: 4.3 CIS GCP Foundation 1.2: 4.3
Compute Secure Boot disabled Category name in the API: COMPUTE_SECURE_BOOT_DISABLED	Finding description: This Shielded VM does not have Secure Boot enabled. Using Secure Boot helps protect virtual machine instances against advanced threats such as rootkits and bootkits. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks the shieldedInstanceConfig property on Compute Engine instances to determine if enableIntegrityMonitoring, enableSecureBoot, enableVtpm are all set to true. The fields indicate whether attached disks are compatible with Secure Boot and if Shielded VM is turned on. Assets excluded from scans: GKE instances, Compute Engine disks that have GPU accelerators and don't use Container-Optimized OS), Serverless VPC Access Batch scans: Every 6 hours Real-time scans: Yes
Compute serial ports enabled Category name in the API: COMPUTE_SERIAL_PORTS_ENABLED	Finding description: Serial ports are enabled for an instance, allowing connections to the instance's serial console. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks the metadata.items[] object in instance metadata for the key-value pair "key": "serial-port-enable", "value": TRUE. Assets excluded from scans: GKE instances Additional IAM permissions: roles/compute.Viewer Additional inputs: Reads metadata from Compute Engine Batch scans: Every 12 hours Real-time scans: No	CIS GCP Foundation 1.0: 4.4 CIS GCP Foundation 1.1: 4.5 CIS GCP Foundation 1.2: 4.5
Default service account used Category name in the API: DEFAULT_SERVICE_ACCOUNT_USED	Finding description: An instance is configured to use the default service account. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks the serviceAccounts property in instance metadata for any service account email addresses with the prefix [e-mail], indicating the Google-created default service account. Assets excluded from scans: GKE instances, Dataflow jobs Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 4.1 CIS GCP Foundation 1.2: 4.1
Disk CMEK disabled Category name in the API: DISK_CMEK_DISABLED	Finding description: Disks on this VM are not encrypted with customer- managed encryption keys (CMEK). This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets compute.googleapis.com/Disk Fix this finding	Checks the kmsKeyName field in the diskEncryptionKey object, in disk metadata, for the resource name of your CMEK. Batch scans: Every 6 hours Real-time scans: Yes
Disk CSEK disabled Category name in the API: DISK_CSEK_DISABLED	Finding description: Disks on this VM are not encrypted with Customer Supplied Encryption Keys (CSEK). This detector requires additional configuration to enable. For instructions, see Special-case detector. Pricing tier: Premium Supported assets compute.googleapis.com/Disk Fix this finding	Checks the kmsKeyName field in the diskEncryptionKey object for the resource name of your CSEK. Assets excluded from scans: Compute Engine disks without the enforce_customer_supplied_disk_encryption_keys security mark set to true Additional IAM permissions: roles/compute.Viewer Additional inputs: Reads metadata from Compute Engine Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 4.6 CIS GCP Foundation 1.1: 4.7 CIS GCP Foundation 1.2: 4.7
Full API access Category name in the API: FULL_API_ACCESS	Finding description: An instance is configured to use the default service account with full access to all Google Cloud APIs. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Retrieves the scopes field in the serviceAccounts property to check whether a default service account is used and if it is assigned the cloud-platform scope. Assets excluded from scans: GKE instances, Dataflow jobs Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 4.1 CIS GCP Foundation 1.1: 4.2 CIS GCP Foundation 1.2: 4.2 PCI-DSS v3.2.1: 7.1.2 NIST 800-53: AC-6 ISO-27001: A.9.2.3
HTTP load balancer Category name in the API: HTTP_LOAD_BALANCER	Finding description: An instance uses a load balancer that is configured to use a target HTTP proxy instead of a target HTTPS proxy. Pricing tier: Premium Supported assets compute.googleapis.com/TargetHttpProxy Fix this finding	Determines if the selfLink property of the targetHttpProxy resource matches the target attribute in the forwarding rule, and if the forwarding rule contains a loadBalancingScheme field set to External. Additional IAM permissions: roles/compute.Viewer Additional inputs: Reads forwarding rules for a target HTTP proxy from Compute Engine, checking for external rules Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 2.3
IP forwarding enabled Category name in the API: IP_FORWARDING_ENABLED	Finding description: IP forwarding is enabled on instances. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks whether the canIpForward property of the instance is set to true. Assets excluded from scans: GKE instances, Serverless VPC Access Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 4.5 CIS GCP Foundation 1.1: 4.6 CIS GCP Foundation 1.2: 4.6
OS login disabled Category name in the API: OS_LOGIN_DISABLED	Finding description: OS Login is disabled on this instance. Pricing tier: Premium Supported assets compute.googleapis.com/Project Fix this finding	Checks the commonInstanceMetadata.items[] object in project metadata for the key-value pair, "key": "enable-oslogin", "value": TRUE. The detector also checks all instances in a Compute Engine project to determine whether OS Login is disabled for individual instances. Assets excluded from scans: GKE instances Additional IAM permissions: roles/compute.Viewer Additional inputs: Reads metadata from Compute Engine. The detector also examines Compute Engine instances in the project Batch scans: Every 12 hours Real-time scans: No	CIS GCP Foundation 1.0: 4.3 CIS GCP Foundation 1.1: 4.4 CIS GCP Foundation 1.2: 4.4
Public IP address Category name in the API: PUBLIC_IP_ADDRESS	Finding description: An instance has a public IP address. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Instance Fix this finding	Checks whether the networkInterfaces property contains an accessConfigs field, indicating it is configured to use a public IP address. Assets excluded from scans: GKE instances Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 4.9 CIS GCP Foundation 1.2: 4.9 PCI-DSS v3.2.1: 1.2.1, 1.3.5 NIST 800-53: CA-3, SC-7
Shielded VM disabled Category name in the API: SHIELDED_VM_DISABLED	Finding description: Shielded VM is disabled on this instance. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks the shieldedInstanceConfig property in Compute Engine instances to determine if enableIntegrityMonitoring, enableSecureBoot, enableVtpm fields are all set to true. The fields indicate whether attached disks are compatible with Secure Boot and if Shielded VM is turned on. Assets excluded from scans: GKE instances, Compute Engine disks that have GPU accelerators and don't use Container-Optimized OS), Serverless VPC Access Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 4.8 CIS GCP Foundation 1.2: 4.8
Weak SSL policy Category name in the API: WEAK_SSL_POLICY	Finding description: An instance has a weak SSL policy. Pricing tier: Premium Supported assets compute.googleapis.com/TargetHttpsProxy compute.googleapis.com/TargetSslProxy Fix this finding	Checks whether sslPolicy in asset metadata is empty and, for the attached sslPolicies resource, whether profile is set to Restricted or Modern, minTlsVersion is set to TLS 1.2, and customFeatures is empty or does not contain the following ciphers: TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_3DES_EDE_CBC_SHA. Additional IAM permissions: roles/compute.Viewer Additional inputs: Reads SSL policies for target proxies storage, checking for weak policies Batch scans: Every 6 hours Real-time scans: Yes, but only when the TargetHttpsProxy of the TargetSslProxy is updated, not when the SSL policy gets updated	CIS GCP Foundation 1.1: 3.9 CIS GCP Foundation 1.2: 3.9 PCI-DSS v3.2.1: 4.1 NIST 800-53: SC-7 ISO-27001: A.14.1.3

Container vulnerability findings

These finding types all relate to GKE container configurations, and belong to the CONTAINER_SCANNER detector type.

Table 4. Container scanner

Detector	Summary	Asset scan settings	Compliance standards
Alpha cluster enabled Category name in the API: ALPHA_CLUSTER_ENABLED	Finding description: Alpha cluster features are enabled for a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the enableKubernetesAlpha property of a cluster is set to true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.10.2
Auto repair disabled Category name in the API: AUTO_REPAIR_DISABLED	Finding description: A GKE cluster's auto repair feature, which keeps nodes in a healthy, running state, is disabled. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the management property of a node pool for the key-value pair, "key": "autoRepair", "value": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.7 CIS GKE 1.0: 6.5.2 PCI-DSS v3.2.1: 2.2
Auto upgrade disabled Category name in the API: AUTO_UPGRADE_DISABLED	Finding description: A GKE cluster's auto upgrade feature, which keeps clusters and node pools on the latest stable version of Kubernetes, is disabled. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the management property of a node pool for the key-value pair, "key": "autoUpgrade", "value": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.8 CIS GKE 1.0: 6.5.3 PCI-DSS v3.2.1: 2.2
Binary authorization disabled Category name in the API: BINARY_AUTHORIZATION_DISABLED	Finding description: Binary Authorization is disabled on a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the binaryAuthorization property contains the key-value pair, "enabled": true, and defaultAdmissionRule contains the key-value pair evaluationMode: ALWAYS_ALLOW. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.10.5
Cluster logging disabled Category name in the API: CLUSTER_LOGGING_DISABLED	Finding description: Logging isn't enabled for a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the loggingService property of a cluster contains the location Cloud Logging should use to write logs. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.7.1 PCI-DSS v3.2.1: 10.2.2, 10.2.7
Cluster monitoring disabled Category name in the API: CLUSTER_MONITORING_DISABLED	Finding description: Monitoring is disabled on GKE clusters. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the monitoringService property of a cluster contains the location Cloud Monitoring should use to write metrics. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.2 CIS GKE 1.0: 6.7.1 PCI-DSS v3.2.1: 10.1, 10.2
Cluster private Google access disabled Category name in the API: CLUSTER_PRIVATE_GOOGLE_ACCESS_DISABLED	Finding description: Cluster hosts are not configured to use only private, internal IP addresses to access Google APIs. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the privateIpGoogleAccess property of a subnetwork is set to false. Additional inputs: Reads subnetworks from storage, filing findings only for clusters with subnetworks Batch scans: Every 6 hours Real-time scans: Yes, but only if cluster is updated, not for subnetwork updates	CIS GCP Foundation 1.0: 7.1 PCI-DSS v3.2.1: 1.3
Cluster secrets encryption disabled Category name in the API: CLUSTER_SECRETS_ENCRYPTION_DISABLED	Finding description: Application-layer secrets encryption is disabled on a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the keyName property of the databaseEncryption object for the key-value pair "state": ENCRYPTED. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.3.1
Cluster shielded nodes disabled Category name in the API: CLUSTER_SHIELDED_NODES_DISABLED	Finding description: Shielded GKE nodes are not enabled for a cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the shieldedNodes property for the key-value pair "enabled": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.5.5
COS not used Category name in the API: COS_NOT_USED	Finding description: Compute Engine VMs aren't using the Container-Optimized OS that is designed for running Docker containers on Google Cloud securely. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the config property of a node pool for the key-value pair, "imageType": "COS". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.9 CIS GKE 1.0: 6.5.1 PCI-DSS v3.2.1: 2.2
Integrity monitoring disabled Category name in the API: INTEGRITY_MONITORING_DISABLED	Finding description: Integrity monitoring is disabled for a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the shieldedInstanceConfig property of the nodeConfig object for the key-value pair "enableIntegrityMonitoring": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.5.6
Intranode visibility disabled Category name in the API: INTRANODE_VISIBILITY_DISABLED	Finding description: Intranode visibility is disabled for a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the networkConfig property for the key-value pair "enableIntraNodeVisibility": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.6.1
IP alias disabled Category name in the API: IP_ALIAS_DISABLED	Finding description: A GKE cluster was created with alias IP ranges disabled. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the useIPAliases field of the ipAllocationPolicy in a cluster is set to false. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.6.2 PCI-DSS v3.2.1: 1.3.4, 1.3.7
Legacy authorization enabled Category name in the API: LEGACY_AUTHORIZATION_ENABLED	Finding description: Legacy Authorization is enabled on GKE clusters. Pricing tier: Premium or Standard Supported assets container.googleapis.com/Cluster Fix this finding	Checks the legacyAbac property of a cluster for the key-value pair, "enabled": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.3 CIS GKE 1.0: 6.8.3 PCI-DSS v3.2.1: 4.1
Legacy metadata enabled Category name in the API: LEGACY_METADATA_ENABLED	Finding description: Legacy metadata is enabled on GKE clusters. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the config property of a node pool for the key-value pair, "disable-legacy-endpoints": "false". Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.4.1
Master authorized networks disabled Category name in the API: MASTER_AUTHORIZED_NETWORKS_DISABLED	Finding description: Control Plane Authorized Networks is not enabled on GKE clusters. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the masterAuthorizedNetworksConfig property of a cluster for the key-value pair, "enabled": false. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.4 CIS GKE 1.0: 6.6.3 PCI-DSS v3.2.1: 1.2.1, 1.3.2
Network policy disabled Category name in the API: NETWORK_POLICY_DISABLED	Finding description: Network policy is disabled on GKE clusters. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the networkPolicy field of the addonsConfig property for the key-value pair, "disabled": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.6.7 PCI-DSS v3.2.1: 1.3 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Nodepool boot CMEK disabled Category name in the API: NODEPOOL_BOOT_CMEK_DISABLED	Finding description: Boot disks in this node pool are not encrypted with customer-managed encryption keys (CMEK). This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the bootDiskKmsKey property of node pools for the resource name of your CMEK. Batch scans: Every 6 hours Real-time scans: Yes
Nodepool secure boot disabled Category name in the API: NODEPOOL_SECURE_BOOT_DISABLED	Finding description: Secure Boot is disabled for a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the shieldedInstanceConfig property of the nodeConfig object for the key-value pair "enableSecureBoot": true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.5.7
Over privileged account Category name in the API: OVER_PRIVILEGED_ACCOUNT	Finding description: A service account has overly broad project access in a cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Evaluates the config property of a node pool to check if no service account is specified or if the default service account is used. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.2.1 PCI-DSS v3.2.1: 2.1, 7.1.2 NIST 800-53: AC-6, SC-7 ISO-27001: A.9.2.3
Over privileged scopes Category name in the API: OVER_PRIVILEGED_SCOPES	Finding description: A node service account has broad access scopes. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the access scope listed in the config.oauthScopes property of a node pool is a limited service account access scope: https://www.googleapis.com/auth/devstorage.read_only, https://www.googleapis.com/auth/logging.write, or https://www.googleapis.com/auth/monitoring. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.2.1
Pod security policy disabled Category name in the API: POD_SECURITY_POLICY_DISABLED	Finding description: PodSecurityPolicy is disabled on a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the podSecurityPolicyConfig property of a cluster for the key-value pair, "enabled": false. Additional IAM permissions: roles/container.clusterViewer Additional inputs: Reads cluster information from GKE, because pod security policies are a Beta feature. Kubernetes has officially deprecated PodSecurityPolicy in version 1.21. PodSecurityPolicy will be shut down in version 1.25. For information about alternatives, refer to PodSecurityPolicy deprecation. Batch scans: Every 12 hours Real-time scans: No	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.10.3
Private cluster disabled Category name in the API: PRIVATE_CLUSTER_DISABLED	Finding description: A GKE cluster has a Private cluster disabled. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the enablePrivateNodes field of the privateClusterConfig property is set to false. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.1 CIS GKE 1.0: 6.6.5 PCI-DSS v3.2.1: 1.3.2
Release channel disabled Category name in the API: RELEASE_CHANNEL_DISABLED	Finding description: A GKE cluster is not subscribed to a release channel. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks the releaseChannel property for the key-value pair "channel": UNSPECIFIED. Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.5.4
Web UI enabled Category name in the API: WEB_UI_ENABLED	Finding description: The GKE web UI (dashboard) is enabled. Pricing tier: Premium or Standard Supported assets container.googleapis.com/Cluster Fix this finding	Checks the kubernetesDashboard field of the addonsConfig property for the key-value pair, "disabled": false. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 7.6 CIS GKE 1.0: 6.10.1 PCI-DSS v3.2.1: 6.6
Workload Identity disabled Category name in the API: WORKLOAD_IDENTITY_DISABLED	Finding description: Workload Identity is disabled on a GKE cluster. Pricing tier: Premium Supported assets container.googleapis.com/Cluster Fix this finding	Checks whether the workloadIdentityConfig property of a cluster is set. The detector also checks whether the workloadMetadataConfig property of a node pool is set to GKE_METADATA. Additional IAM permissions: roles/container.clusterViewer Batch scans: Every 6 hours Real-time scans: Yes	CIS GKE 1.0: 6.2.2

Dataproc vulnerability findings

Vulnerabilities of this detector type all relate to Dataproc and belong to the DATAPROC_SCANNER detector type.

Table 5. Dataproc scanner

Detector	Summary	Asset scan settings	Compliance standards
Dataproc image outdated Category name in the API: DATAPROC_IMAGE_OUTDATED	Finding description: A Dataproc cluster was created with a Dataproc image version that is impacted by security vulnerabilities in the Apache Log4j 2 utility (CVE-2021-44228 and CVE-2021-45046). Pricing tier: Premium or Standard Supported assets dataproc.googleapis.com/Cluster Fix this finding	Checks whether the softwareConfig.imageVersion field in the config property of a Cluster is earlier than 1.3.95 or is a subminor image version earlier than 1.4.77, 1.5.53, or 2.0.27. Batch scans: Every 6 hours Real-time scans: Yes

Dataset vulnerability findings

Vulnerabilities of this detector type all relate to BigQuery Dataset configurations, and belong to the DATASET_SCANNER detector type.

Table 6. Dataset scanner

Detector	Summary	Asset scan settings	Compliance standards
BigQuery table CMEK disabled Category name in the API: BIGQUERY_TABLE_CMEK_DISABLED	Finding description: A BigQuery table is not configured to use a customer-managed encryption key (CMEK). This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets bigquery.googleapis.com/Table Fix this finding	Checks whether the kmsKeyName field in the encryptionConfiguration property is empty. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 7.2
Dataset CMEK disabled Category name in the API: DATASET_CMEK_DISABLED	Finding description: A BigQuery dataset is not configured to use a default CMEK. This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets bigquery.googleapis.com/Dataset Fix this finding	Checks whether the kmsKeyName field in the defaultEncryptionConfiguration property is empty. Batch scans: Every 6 hours Real-time scans: No
Public dataset Category name in the API: PUBLIC_DATASET	Finding description: A dataset is configured to be open to public access. Pricing tier: Premium or Standard Supported assets bigquery.googleapis.com/Dataset Fix this finding	Checks the IAM allow policy in resource metadata for the principals allUsers or allAuthenticatedUsers, which grant public access. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 7.1 CIS GCP Foundation 1.2: 7.1 PCI-DSS v3.2.1: 7.1 NIST 800-53: AC-2 ISO-27001: A.8.2.3, A.14.1.3

DNS vulnerability findings

Vulnerabilities of this detector type all relate to Cloud DNS configurations, and belong to the DNS_SCANNER detector type.

Table 7. DNS scanner

Detector	Summary	Asset scan settings	Compliance standards
DNSSEC disabled Category name in the API: DNSSEC_DISABLED	Finding description: DNSSEC is disabled for Cloud DNS zones. Pricing tier: Premium Supported assets dns.googleapis.com/ManagedZone Fix this finding	Checks whether the state field of the dnssecConfig property is set to off. Assets excluded from scans: Cloud DNS zones that are not public Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.3 CIS GCP Foundation 1.1: 3.3 CIS GCP Foundation 1.2: 3.3 ISO-27001: A.8.2.3
RSASHA1 for signing Category name in the API: RSASHA1_FOR_SIGNING	Finding description: RSASHA1 is used for key signing in Cloud DNS zones. Pricing tier: Premium Supported assets dns.googleapis.com/ManagedZone Fix this finding	Checks whether the defaultKeySpecs.algorithm object of the dnssecConfig property is set to rsasha1. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.4, 3.5 CIS GCP Foundation 1.1: 3.4, 3.5 CIS GCP Foundation 1.2: 3.4, 3.5

Firewall vulnerability findings

Vulnerabilities of this detector type all relate to firewall configurations, and belong to the FIREWALL_SCANNER detector type.

Table 8. Firewall scanner

Detector	Summary	Asset scan settings	Compliance standards
Egress deny rule not set Category name in the API: EGRESS_DENY_RULE_NOT_SET	Finding description: An egress deny rule is not set on a firewall. Egress deny rules should be set to block unwanted outbound traffic. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks whether the destinationRanges property in the firewall is set to 0.0.0.0/0 and the denied property contains the key-value pair, "IPProtocol": "all". Additional inputs: Reads egress firewalls for a project from storage Batch scans: Every 6 hours Real-time scans: Yes, but only on project changes, not firewall rule changes	PCI-DSS v3.2.1: 7.2
Firewall rule logging disabled Category name in the API: FIREWALL_RULE_LOGGING_DISABLED	Finding description: Firewall rule logging is disabled. Firewall rule logging should be enabled so you can audit network access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the logConfig property in firewall metadata to see if it's empty or contains the key-value pair "enable": false. Assets excluded from scans: GKE instances, firewall rules created by GKE, Serverless VPC Access Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 10.1, 10.2 NIST 800-53: SI-4 ISO-27001: A.13.1.1
Open Cassandra port Category name in the API: OPEN_CASSANDRA_PORT	Finding description: A firewall is configured to have an open Cassandra port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:7000-7001, 7199, 8888, 9042, 9160, 61620-61621. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open ciscosecure websm port Category name in the API: OPEN_CISCOSECURE_WEBSM_PORT	Finding description: A firewall is configured to have an open CISCOSECURE_WEBSM port that allows generic access. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocol and port: TCP:9090. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open directory services port Category name in the API: OPEN_DIRECTORY_SERVICES_PORT	Finding description: A firewall is configured to have an open DIRECTORY_SERVICES port that allows generic access. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:445 and UDP:445. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open DNS port Category name in the API: OPEN_DNS_PORT	Finding description: A firewall is configured to have an open DNS port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:53 and UDP:53. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open elasticsearch port Category name in the API: OPEN_ELASTICSEARCH_PORT	Finding description: A firewall is configured to have an open ELASTICSEARCH port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:9200, 9300. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open firewall Category name in the API: OPEN_FIREWALL	Finding description: A firewall is configured to be open to public access. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the sourceRanges and allowed properties for one of two configurations: The sourceRanges property contains 0.0.0.0/0 and the allowed property contains a combination of rules that includes any protocol or protocol:port, except the following: icmp tcp:22 tcp:443 tcp:3389 udp:3389 sctp:22 The sourceRanges property contains a combination of IP ranges that includes any non-private IP address and the allowed property contains a combination of rules that permit either all tcp ports or all udp ports. Assets excluded from scans: Firewall rules created by GKE Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1
Open FTP port Category name in the API: OPEN_FTP_PORT	Finding description: A firewall is configured to have an open FTP port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocol and port: TCP:21. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open HTTP port Category name in the API: OPEN_HTTP_PORT	Finding description: A firewall is configured to have an open HTTP port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:80. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open LDAP port Category name in the API: OPEN_LDAP_PORT	Finding description: A firewall is configured to have an open LDAP port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:389, 636 and UDP:389. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open Memcached port Category name in the API: OPEN_MEMCACHED_PORT	Finding description: A firewall is configured to have an open MEMCACHED port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:11211, 11214-11215 and UDP:11211, 11214-11215. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open MongoDB port Category name in the API: OPEN_MONGODB_PORT	Finding description: A firewall is configured to have an open MONGODB port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:27017-27019. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open MySQL port Category name in the API: OPEN_MYSQL_PORT	Finding description: A firewall is configured to have an open MYSQL port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocol and port: TCP:3306. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open NetBIOS port Category name in the API: OPEN_NETBIOS_PORT	Finding description: A firewall is configured to have an open NETBIOS port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:137-139 and UDP:137-139. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open OracleDB port Category name in the API: OPEN_ORACLEDB_PORT	Finding description: A firewall is configured to have an open ORACLEDB port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:1521, 2483-2484 and UDP:2483-2484. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open pop3 port Category name in the API: OPEN_POP3_PORT	Finding description: A firewall is configured to have an open POP3 port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocol and port: TCP:110. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open PostgreSQL port Category name in the API: OPEN_POSTGRESQL_PORT	Finding description: A firewall is configured to have an open PostgreSQL port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:5432 and UDP:5432. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open RDP port Category name in the API: OPEN_RDP_PORT	Finding description: A firewall is configured to have an open RDP port that allows generic access. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Firewall Fix this finding	Checks the allowed property in firewall metadata for the following protocols and ports: TCP:3389 and UDP:3389. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.7 CIS GCP Foundation 1.1: 3.7 CIS GCP Foundation 1.2: 3.7 PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open Redis port Category name in the API: OPEN_REDIS_PORT	Finding description: A firewall is configured to have an open REDIS port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks whether the allowed property in firewall metadata contains the following protocol and port: TCP:6379. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open SMTP port Category name in the API: OPEN_SMTP_PORT	Finding description: A firewall is configured to have an open SMTP port that allows generic access. Pricing tier: Premium Supported assets compute.googleapis.com/Firewall Fix this finding	Checks whether the allowed property in firewall metadata contains the following protocol and port: TCP:25. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open SSH port Category name in the API: OPEN_SSH_PORT	Finding description: A firewall is configured to have an open SSH port that allows generic access. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Firewall Fix this finding	Checks whether the allowed property in firewall metadata contains the following protocols and ports: TCP:22 and SCTP:22. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.6 CIS GCP Foundation 1.1: 3.6 CIS GCP Foundation 1.2: 3.6 PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1
Open Telnet port Category name in the API: OPEN_TELNET_PORT	Finding description: A firewall is configured to have an open TELNET port that allows generic access. Pricing tier: Premium or Standard Supported assets compute.googleapis.com/Firewall Fix this finding	Checks whether the allowed property in firewall metadata contains the following protocol and port: TCP:23. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 1.2.1 NIST 800-53: SC-7 ISO-27001: A.13.1.1

IAM vulnerability findings

Vulnerabilities of this detector type all relate to Identity and Access Management (IAM) configuration, and belong to the IAM_SCANNER detector type.

Table 9. IAM Scanner

Detector	Summary	Asset scan settings	Compliance standards
Admin service account Category name in the API: ADMIN_SERVICE_ACCOUNT	Finding description: A service account has Admin, Owner, or Editor privileges. These roles shouldn't be assigned to user-created service accounts. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM allow policy in resource metadata for any user-created service accounts (indicated by the prefix iam.gserviceaccount.com), that are assigned roles/Owner or roles/Editor, or a role ID that contains admin. Assets excluded from scans: Container Registry service account (containerregistry.iam.gserviceaccount.com) and Security Command Center service account (security-center-api.iam.gserviceaccount.com) Batch scans: Every 6 hours Real-time scans: Yes, unless the IAM update is done on a folder	CIS GCP Foundation 1.0: 1.4 CIS GCP Foundation 1.1: 1.5 CIS GCP Foundation 1.2: 1.5
KMS role separation Category name in the API: KMS_ROLE_SEPARATION	Finding description: Separation of duties is not enforced, and a user exists who has any of the following Cloud Key Management Service (Cloud KMS) roles at the same time: CryptoKey Encrypter/Decrypter, Encrypter, or Decrypter. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks IAM allow policies in resource metadata and retrieves principals assigned any of the following roles at the same time: roles/cloudkms.cryptoKeyEncrypterDecrypter, roles/cloudkms.cryptoKeyEncrypter, and roles/cloudkms.cryptoKeyDecrypter, roles/cloudkms.signer, roles/cloudkms.signerVerifier, roles/cloudkms.publicKeyViewer. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.9 CIS GCP Foundation 1.1: 1.11 NIST 800-53: AC-5 ISO-27001: A.9.2.3, A.10.1.2
Non org IAM member Category name in the API: NON_ORG_IAM_MEMBER	Finding description: There is a user who isn't using organizational credentials. Per CIS GCP Foundations 1.0, currently, only identities with @gmail.com email addresses trigger this detector. Pricing tier: Premium or Standard Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Compares @gmail.com email addresses in the user field in IAM allow policy metadata to a list of approved identities for your organization. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.1 CIS GCP Foundation 1.1: 1.1 CIS GCP Foundation 1.2: 1.1 PCI-DSS v3.2.1: 7.1.2 NIST 800-53: AC-3 ISO-27001: A.9.2.3
Open group IAM member Category name in the API: OPEN_GROUP_IAM_MEMBER	Finding description: A Google Groups account that can be joined without approval is used as an IAM allow policy principal. Pricing tier: Premium or Standard Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM policy in resource metadata for any bindings containing a member (principal) that's prefixed with group. If the group is an open group, Security Health Analytics generates this finding. Additional inputs: Reads Google Groups metadata to check whether the group identified is an open group. Batch scans: Every 6 hours Real-time scans: No
Over privileged service account user Category name in the API: OVER_PRIVILEGED_SERVICE_ACCOUNT_USER	Finding description: A user has the Service Account User or Service Account Token Creator role at the project level, instead of for a specific service account. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM allow policy in resource metadata for any principals assigned roles/iam.serviceAccountUser or roles/iam.serviceAccountTokenCreator at the project level. Assets excluded from scans: Cloud Build service accounts Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.5 CIS GCP Foundation 1.1: 1.6 CIS GCP Foundation 1.2: 1.6 PCI-DSS v3.2.1: 7.1.2 NIST 800-53: AC-6 ISO-27001: A.9.2.3
Primitive roles used Category name in the API: PRIMITIVE_ROLES_USED	Finding description: A user has the basic role, Owner, Writer, or Reader. These roles are too permissive and shouldn't be used. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM allow policy in resource metadata for any principals assigned roles/Owner, roles/Writer, or roles/Reader. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 7.1.2 NIST 800-53: AC-6 ISO-27001: A.9.2.3
Redis role used on org Category name in the API: REDIS_ROLE_USED_ON_ORG	Finding description: A Redis IAM role is assigned at the organization or folder level. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization Fix this finding	Checks the IAM allow policy in resource metadata for principals assigned roles/redis.admin, roles/redis.editor, roles/redis.viewer at the organization or folder level. Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 7.1.2 ISO-27001: A.9.2.3
Service account role separation Category name in the API: SERVICE_ACCOUNT_ROLE_SEPARATION	Finding description: A user has been assigned the Service Account Admin and Service Account User roles. This violates the "Separation of Duties" principle. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM allow policy in resource metadata for any principals assigned both roles/iam.serviceAccountUser and roles/iam.serviceAccountAdmin. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.7 CIS GCP Foundation 1.1: 1.8 CIS GCP Foundation 1.2: 1.8 NIST 800-53: AC-5 ISO-27001: A.9.2.3
Service account key not rotated Category name in the API: SERVICE_ACCOUNT_KEY_NOT_ROTATED	Finding description: A service account key hasn't been rotated for more than 90 days. Pricing tier: Premium Supported assets iam.googleapis.com/ServiceAccountKey Fix this finding	Evaluates the key creation timestamp captured in the validAfterTime property in service accounts key metadata. Assets excluded from scans: Expired service account keys and keys not managed by users Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.6	CIS GCP Foundation 1.1: 1.7	CIS GCP Foundation 1.2: 1.7
User managed service account key Category name in the API: USER_MANAGED_SERVICE_ACCOUNT_KEY	Finding description: A user manages a service account key. Pricing tier: Premium Supported assets iam.googleapis.com/ServiceAccountKey Fix this finding	Checks whether the keyType property in service account key metadata is set to User_Managed. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.3	CIS GCP Foundation 1.1: 1.4	CIS GCP Foundation 1.2: 1.4

KMS vulnerability findings

Vulnerabilities of this detector type all relate to Cloud KMS configurations, and belong to the KMS_SCANNER detector type.

Table 10. KMS scanner

Detector	Summary	Asset scan settings	Compliance standards
KMS key not rotated Category name in the API: KMS_KEY_NOT_ROTATED	Finding description: Rotation isn't configured on a Cloud KMS encryption key. Keys should be rotated within a period of 90 days. Pricing tier: Premium Supported assets cloudkms.googleapis.com/CryptoKey Fix this finding	Checks resource metadata for the existence of rotationPeriod or nextRotationTime properties. Assets excluded from scans: Asymmetric keys and keys with disabled or destroyed primary versions Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 1.8 CIS GCP Foundation 1.1: 1.10 CIS GCP Foundation 1.2: 1.10 PCI-DSS v3.2.1: 3.5 NIST 800-53: SC-12 ISO-27001: A.10.1.2
KMS project has owner Category name in the API: KMS_PROJECT_HAS_OWNER	Finding description: A user has Owner permissions on a project that has cryptographic keys. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM allow policy in project metadata for principals assigned roles/Owner. Additional inputs: Reads cryptokeys for a project from storage, filing findings only for projects with cryptokeys Batch scans: Every 6 hours Real-time scans: Yes, but only on changes to IAM allow policy, not on changes to KMS keys	CIS GCP Foundation 1.1: 1.11 CIS GCP Foundation 1.2: 1.11 PCI-DSS v3.2.1: 3.5 NIST 800-53: AC-6, SC-12 ISO-27001: A.9.2.3, A.10.1.2
KMS public key Category name in the API: KMS_PUBLIC_KEY	Finding description: A Cloud KMS cryptographic key is publicly accessible. Pricing tier: Premium Supported assets cloudkms.googleapis.com/CryptoKey cloudkms.googleapis.com/KeyRing Fix this finding	Checks the IAM allow policy in resource metadata for the principals allUsers or allAuthenticatedUsers, which grant public access. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 1.9 CIS GCP Foundation 1.2: 1.9
Too many KMS users Category name in the API: TOO_MANY_KMS_USERS	Finding description: There are more than three users of cryptographic keys. Pricing tier: Premium Supported assets cloudkms.googleapis.com/CryptoKey Fix this finding	Checks IAM allow policies for key rings, projects, and organizations, and retrieves principals with roles that allow them to encrypt, decrypt or sign data using Cloud KMS keys: roles/owner, roles/cloudkms.cryptoKeyEncrypterDecrypter, roles/cloudkms.cryptoKeyEncrypter, roles/cloudkms.cryptoKeyDecrypter, roles/cloudkms.signer, and roles/cloudkms.signerVerifier. Additional inputs: Reads cryptokey versions for a cryptokey from storage, filing findings only for keys with active versions. The detector also reads key ring, project, and organization IAM allow policies from storage Batch scans: Every 6 hours Real-time scans: Yes	PCI-DSS v3.2.1: 3.5.2 ISO-27001: A.9.2.3

Logging vulnerability findings

Vulnerabilities of this detector type all relate to logging configurations, and belong to the LOGGING_SCANNER detector type.

Table 11. Logging scanner

Detector	Summary	Asset scan settings	Compliance standards
Audit logging disabled Category name in the API: AUDIT_LOGGING_DISABLED	Finding description: Audit logging has been disabled for this resource. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Organization cloudresourcemanager.googleapis.com/Folder cloudresourcemanager.googleapis.com/Project Fix this finding	Checks the IAM allow policy in resource metadata for the existence of an auditLogConfigs object. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 2.1 CIS GCP Foundation 1.1: 2.1 CIS GCP Foundation 1.2: 2.1 PCI-DSS v3.2.1: 10.1, 10.2 NIST 800-53: AC-2, AU-2 ISO-27001: A.12.4.1, A.16.1.7
Bucket logging disabled Category name in the API: BUCKET_LOGGING_DISABLED	Finding description: There is a storage bucket without logging enabled. Pricing tier: Premium Supported assets storage.googleapis.com/Bucket Fix this finding	Checks whether the logBucket field in the bucket's logging property is empty. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 5.3
Locked retention policy not set Category name in the API: LOCKED_RETENTION_POLICY_NOT_SET	Finding description: A locked retention policy is not set for logs. Pricing tier: Premium Supported assets storage.googleapis.com/Bucket Fix this finding	Checks whether the isLocked field in the bucket's retentionPolicy property is set to true. Additional inputs: Reads the log sink (the log filter and log destination) for a bucket to determine whether it is a log bucket Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 2.3 CIS GCP Foundation 1.2: 2.3 PCI-DSS v3.2.1: 10.5 NIST 800-53: AU-11 ISO-27001: A.12.4.2, A.18.1.3
Log not exported Category name in the API: LOG_NOT_EXPORTED	Finding description: There is a resource that doesn't have an appropriate log sink configured. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Retrieves a logSink object in a project, checking that the includeChildren field is set to true, the destination field includes the location to write logs to, and the filter field is populated. Additional inputs: Reads the log sink (the log filter and log destination) for a bucket to determine whether it is a log bucket Batch scans: Every 6 hours Real-time scans: Yes, but only on project changes, not if log export is set up on folder or organization	CIS GCP Foundation 1.0: 2.2 CIS GCP Foundation 1.1: 2.2 CIS GCP Foundation 1.2: 2.2 ISO-27001: A.18.1.3
Object versioning disabled Category name in the API: OBJECT_VERSIONING_DISABLED	Finding description: Object versioning isn't enabled on a storage bucket where sinks are configured. Pricing tier: Premium Supported assets storage.googleapis.com/Bucket Fix this finding	Checks whether the enabled field in the bucket's versioning property is set to true. Assets excluded from scans: Cloud Storage buckets with a locked retention policy Additional inputs: Reads the log sink (the log filter and log destination) for a bucket to determine whether it is a log bucket Batch scans: Every 6 hours Real-time scans: Yes, but only if object versioning changes, not if log buckets are created	CIS GCP Foundation 1.0: 2.3 PCI-DSS v3.2.1: 10.5 NIST 800-53: AU-11 ISO-27001: A.12.4.2, A.18.1.3

Monitoring vulnerability findings

Vulnerabilities of this detector type all relate to monitoring configurations, and belong to the MONITORING_SCANNER type. All Monitoring detector finding properties include:

• The RecommendedLogFilter to use in creating the log metrics.
• The QualifiedLogMetricNames that cover the conditions listed in the recommended log filter.
• TheAlertPolicyFailureReasonsthat indicate if the project does not have alert policies created for any of the qualified log metrics or the existing alert policies don't have the recommended settings.

Table 12. Monitoring scanner

Detector	Summary	Asset scan settings	Compliance standards
Audit config not monitored Category name in the API: AUDIT_CONFIG_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor Audit Configuration changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to protoPayload.methodName="SetIamPolicy" AND protoPayload.serviceData.policyDelta.auditConfigDeltas:*, and if resource.type is specified, that the value is global. The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.5 CIS GCP Foundation 1.1: 2.5 CIS GCP Foundation 1.2: 2.5
Bucket IAM not monitored Category name in the API: BUCKET_IAM_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor Cloud Storage IAM permission changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to resource.type=gcs_bucket AND protoPayload.methodName="storage.setIamPermissions". The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.10 CIS GCP Foundation 1.1: 2.10 CIS GCP Foundation 1.2: 2.10
Custom role not monitored Category name in the API: CUSTOM_ROLE_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor Custom Role changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to resource.type="iam_role" AND (protoPayload.methodName="google.iam.admin.v1.CreateRole" OR protoPayload.methodName="google.iam.admin.v1.DeleteRole" OR protoPayload.methodName="google.iam.admin.v1.UpdateRole"). The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.6 CIS GCP Foundation 1.1: 2.6 CIS GCP Foundation 1.2: 2.6
Firewall not monitored Category name in the API: FIREWALL_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor Virtual Private Cloud (VPC) Network Firewall rule changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to resource.type="gce_firewall_rule" AND (protoPayload.methodName:"compute.firewalls.insert" OR protoPayload.methodName:"compute.firewalls.patch" OR protoPayload.methodName:"compute.firewalls.delete"). The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.7 CIS GCP Foundation 1.1: 2.7 CIS GCP Foundation 1.2: 2.7
Network not monitored Category name in the API: NETWORK_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor VPC network changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to resource.type="gce_network" AND (protoPayload.methodName:"compute.networks.insert" OR protoPayload.methodName:"compute.networks.patch" OR protoPayload.methodName:"compute.networks.delete" OR protoPayload.methodName:"compute.networks.removePeering" OR protoPayload.methodName:"compute.networks.addPeering"). The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.9 CIS GCP Foundation 1.1: 2.9 CIS GCP Foundation 1.2: 2.9
Owner not monitored Category name in the API: OWNER_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor Project Ownership assignments or changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to (protoPayload.serviceName="cloudresourcemanager.googleapis.com") AND (ProjectOwnership OR projectOwnerInvitee) OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="REMOVE" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner") OR (protoPayload.serviceData.policyDelta.bindingDeltas.action="ADD" AND protoPayload.serviceData.policyDelta.bindingDeltas.role="roles/owner"), and if resource.type is specified, that the value is global. The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.4 CIS GCP Foundation 1.1: 2.4 CIS GCP Foundation 1.2: 2.4
Route not monitored Category name in the API: ROUTE_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor VPC network route changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to resource.type="gce_route" AND (protoPayload.methodName:"compute.routes.delete" OR protoPayload.methodName:"compute.routes.insert"). The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.8 CIS GCP Foundation 1.1: 2.8 CIS GCP Foundation 1.2: 2.8
SQL instance not monitored SQL_INSTANCE_NOT_MONITORED	Finding description: Log metrics and alerts aren't configured to monitor Cloud SQL instance configuration changes. Pricing tier: Premium Supported assets cloudresourcemanager.googleapis.com/Project Fix this finding	Checks whether the filter property of the project's LogsMetric resource is set to protoPayload.methodName="cloudsql.instances.update" OR protoPayload.methodName="cloudsql.instances.create" OR protoPayload.methodName="cloudsql.instances.delete", and if resource.type is specified, that the value is global. The detector also searches for a corresponding alertPolicy resource, checking that the conditions and notificationChannels properties are properly configured. Additional IAM permissions: roles/monitoring.alertPolicyViewer Additional inputs: Reads log metrics for the project from storage. Reads Google Cloud's operations suite account information from Google Cloud's operations suite, filing findings only for projects with active accounts Batch scans: Every 12 hours Real-time scans: Yes, but only on project changes, not on log metrics and alert changes	CIS GCP Foundation 1.0: 2.11 CIS GCP Foundation 1.1: 2.11 CIS GCP Foundation 1.2: 2.11

Multi-factor authentication findings

The MFA_SCANNER detector identifies vulnerabilities related to multi-factor authentication for users.

Table 13. Multi-factor authentication scanner

Detector	Summary	Asset scan settings	Compliance standards
MFA not enforced Category name in the API: MFA_NOT_ENFORCED	There are users who aren't using 2-step verification. Pricing tier: Premium or Standard Supported assets cloudresourcemanager.googleapis.com/Organization Fix this finding	Evaluates identity management policies in organizations and user settings for managed accounts in Cloud Identity. Assets excluded from scans: Organization units granted exceptions to the policy Additional inputs: Reads data from Google Workspace Batch scans: Every 12 hours Real-time scans: No	CIS GCP Foundation 1.0: 1.2 CIS GCP Foundation 1.1: 1.2 CIS GCP Foundation 1.2: 1.2 PCI-DSS v3.2.1: 8.3 NIST 800-53: IA-2 ISO-27001: A.9.4.2

Network vulnerability findings

Vulnerabilities of this detector type all relate to an organization's network configurations, and belong to theNETWORK_SCANNERtype.

Table 14. Network scanner

Detector	Summary	Asset scan settings	Compliance standards
Default network Category name in the API: DEFAULT_NETWORK	Finding description: The default network exists in a project. Pricing tier: Premium Supported assets compute.googleapis.com/Network Fix this finding	Checks whether the name property in network metadata is set to default Assets excluded from scans: Projects where Compute Engine API is disabled and Compute Engine resources are in a frozen state Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.1 CIS GCP Foundation 1.1: 3.1 CIS GCP Foundation 1.2: 3.1
DNS logging disabled Category name in the API: DNS_LOGGING_DISABLED	Finding description: DNS logging on a VPC network is not enabled. Pricing tier: Premium Supported assets compute.googleapis.com/Network dns.googleapis.com/Policy Fix this finding	Checks all policies that are associated with a VPC network through the networks[].networkUrl field, and looks for at least one policy that has enableLogging set to true. Assets excluded from scans: Projects where Compute Engine API is disabled and Compute Engine resources are in a frozen state Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 2.12
Legacy network Category name in the API: LEGACY_NETWORK	Finding description: A legacy network exists in a project. Pricing tier: Premium Supported assets compute.googleapis.com/Network Fix this finding	Checks network metadata for existence of the IPv4Range property. Assets excluded from scans: Projects where Compute Engine API is disabled and Compute Engine resources are in a frozen state Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.2 CIS GCP Foundation 1.1: 3.2 CIS GCP Foundation 1.2: 3.2

Organization Policy vulnerability findings

Vulnerabilities of this detector type all relate to configurations of Organization Policy constraints, and belong to the ORG_POLICY type.

Table 15. Org policy scanner

Detector	Summary	Asset scan settings	Compliance standards
Org policy Confidential VM policy Category name in the API: ORG_POLICY_CONFIDENTIAL_VM_POLICY	Finding description: A Compute Engine resource is out of compliance with the constraints/compute.restrictNonConfidentialComputing organization policy. For more information about this org policy constraint, see Enforcing organization policy constraints in Confidential VM. Pricing tier: Premium Supported assets compute.googleapis.com/Instance Fix this finding	Checks whether the enableConfidentialCompute property of a Compute Engine instance is set to true. Assets excluded from scans: GKE instances Additional IAM permissions: permissions/orgpolicy.policy.get Additional inputs: Reads the effective org policy from the org policy service Batch scans: Every 12 hours Real-time scans: No
Org policy location restriction Category name in the API: ORG_POLICY_LOCATION_RESTRICTION	Finding description: A Compute Engine resource is out of compliance with the constraints/gcp.resourceLocations constraint. For more information about this org policy constraint, see Enforcing organization policy constraints. Pricing tier: Premium Supported assets See below Fix this finding	Checks the listPolicy property in the metadata of supported resources for a list of allowed or denied locations. Additional IAM permissions: permissions/orgpolicy.policy.get Additional inputs: Reads the effective org policy from the org policy service Batch scans: Every 12 hours Real-time scans: No
Supported assets for ORG_POLICY_LOCATION_RESTRICTION Compute Engine compute.googleapis.com/Autoscaler compute.googleapis.com/Address compute.googleapis.com/Commitment compute.googleapis.com/Disk compute.googleapis.com/ForwardingRule compute.googleapis.com/HealthCheck compute.googleapis.com/Image compute.googleapis.com/Instance compute.googleapis.com/InstanceGroup compute.googleapis.com/InstanceGroupManager compute.googleapis.com/InterconnectAttachment compute.googleapis.com/NetworkEndpointGroup compute.googleapis.com/NodeGroup compute.googleapis.com/NodeTemplate compute.googleapis.com/PacketMirroring compute.googleapis.com/RegionBackendService compute.googleapis.com/RegionDisk compute.googleapis.com/ResourcePolicy compute.googleapis.com/Reservation compute.googleapis.com/Router compute.googleapis.com/Snapshot compute.googleapis.com/SslCertificate compute.googleapis.com/Subnetwork compute.googleapis.com/TargetHttpProxy compute.google.apis.com/TargetHttpsProxy compute.googleapis.com/TargetInstance compute.googleapis.com/TargetPool compute.googleapis.com/TargetVpnGateway compute.googleapis.com/UrlMap compute.googleapis.com/VpnGateway compute.googleapis.com/VpnTunnel GKE container.googleapis.com/Cluster container.googleapis.com/NodePool Cloud Storage storage.googleapis.com/Bucket Cloud KMS cloudkms.googleapis.com/CryptoKey^1 cloudkms.googleapis.com/CryptoKeyVersion^1 cloudkms.googleapis.com/ImportJob^2 cloudkms.googleapis.com/KeyRing^1 Dataproc dataproc.googleapis.com/Cluster BigQuery bigquery.googleapis.com/Dataset Dataflow dataflow.googleapis.com/Job^3 Cloud SQL sqladmin.googleapis.com/Instance Cloud Composer composer.googleapis.com/Environment Logging logging.googleapis.com/LogBucket Pub/Sub pubsub.googleapis.com/Topic Vertex AI aiplatform.googleapis.com/BatchPredictionJob aiplatform.googleapis.com/CustomJob aiplatform.googleapis.com/DataLabelingJob aiplatform.googleapis.com/Dataset aiplatform.googleapis.com/Endpoint aiplatform.googleapis.com/HyperparameterTuningJob aiplatform.googleapis.com/Model aiplatform.googleapis.com/SpecialistPool aiplatform.googleapis.com/TrainingPipeline Artifact Registry artifactregistry.googleapis.com/Repository ^1 Because Cloud KMS assets cannot be deleted, the asset is not considered out-of-region if the asset's data has been destroyed. ^2 Because Cloud KMS import jobs have a controlled lifecycle and cannot be terminated early, an ImportJob is not considered out-of-region if the job is expired and can no longer be used to import keys. ^3 Because the lifecycle of Dataflow jobs cannot be managed, a Job is not considered out-of-region once it has reached a terminal state (stopped or drained), where it can no longer be used to process data.

Pub/Sub vulnerability findings

Vulnerabilities of this detector type all relate to Pub/Sub configurations, and belong to the PUBSUB_SCANNER type.

Table 16. Pub/Sub scanner

Detector	Summary	Asset scan settings	Compliance standards
Pubsub CMEK disabled Category name in the API: PUBSUB_CMEK_DISABLED	Finding description: A Pub/Sub topic is not encrypted with customer-managed encryption keys (CMEK). This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets pubsub.googleapis.com/Topic Fix this finding	Checks the kmsKeyName field for the resource name of your CMEK. Batch scans: Every 6 hours Real-time scans: Yes

SQL vulnerability findings

Vulnerabilities of this detector type all relate to Cloud SQL configurations, and belong to the SQL_SCANNER type.

Table 17. SQL scanner

Detector	Summary	Asset scan settings	Compliance standards
Auto backup disabled Category name in the API: AUTO_BACKUP_DISABLED	Finding description: A Cloud SQL database doesn't have automatic backups enabled. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the backupConfiguration.enabled property of an Cloud SQL data is set to true. Assets excluded from scans: Cloud SQL replicas Additional inputs: Reads IAM allow policies for ancestors from Security Health Analytics asset storage Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.7 CIS GCP Foundation 1.2: 6.7 NIST 800-53: CP-9 ISO-27001: A.12.3.1
Public SQL instance Category name in the API: PUBLIC_SQL_INSTANCE	Finding description: A Cloud SQL database instance accepts connections from all IP addresses. Pricing tier: Premium or Standard Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the authorizedNetworks property of Cloud SQL instances is set to a single IP address or an IP address range. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 6.2 CIS GCP Foundation 1.1: 6.5 CIS GCP Foundation 1.2: 6.5 PCI-DSS v3.2.1: 1.2.1 NIST 800-53: CA-3, SC-7 ISO-27001: A.8.2.3, A.13.1.3, A.14.1.3
SSL not enforced Category name in the API: SSL_NOT_ENFORCED	Finding description: A Cloud SQL database instance doesn't require all incoming connections to use SSL. Pricing tier: Premium or Standard Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the requireSsl property of the Cloud SQL instance is set to true. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 6.1 CIS GCP Foundation 1.1: 6.4 CIS GCP Foundation 1.2: 6.4 PCI-DSS v3.2.1: 4.1 NIST 800-53: SC-7 ISO-27001: A.8.2.3, A.13.2.1, A.14.1.3
SQL CMEK disabled Category name in the API: SQL_CMEK_DISABLED	Finding description: A SQL database instance is not encrypted with customer-managed encryption keys (CMEK). This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the kmsKeyName field in the diskEncryptionKey object, in instance metadata, for the resource name of your CMEK. Batch scans: Every 6 hours Real-time scans: Yes
SQL contained database authentication Category name in the API: SQL_CONTAINED_DATABASE_AUTHENTICATION	Finding description: The contained database authentication database flag for a Cloud SQL for SQL Server instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair, "name": "contained database authentication", "value": "on" or whether it is enabled by default. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.3.2 CIS GCP Foundation 1.2: 6.3.7
SQL cross DB ownership chaining Category name in the API: SQL_CROSS_DB_OWNERSHIP_CHAINING	Finding description: The cross_db_ownership_chaining database flag for a Cloud SQL for SQL Server instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "cross_db_ownership_chaining", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.3.1 CIS GCP Foundation 1.2: 6.3.2
SQL external scripts enabled Category name in the API: SQL_EXTERNAL_SCRIPTS_ENABLED	Finding description: The external scripts enabled database flag for a Cloud SQL for SQL Server instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "external scripts enabled", "value": "off". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.3.1
SQL local infile Category name in the API: SQL_LOCAL_INFILE	Finding description: The local_infile database flag for a Cloud SQL for MySQL instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "local_infile", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.1.2 CIS GCP Foundation 1.2: 6.1.3
SQL log checkpoints disabled Category name in the API: SQL_LOG_CHECKPOINTS_DISABLED	Finding description: The log_checkpoints database flag for a Cloud SQL for PostgreSQL instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_checkpoints", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.1 CIS GCP Foundation 1.2: 6.2.1
SQL log connections disabled Category name in the API: SQL_LOG_CONNECTIONS_DISABLED	Finding description: The log_connections database flag for a Cloud SQL for PostgreSQL instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_connections", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.2 CIS GCP Foundation 1.2: 6.2.3
SQL log disconnections disabled Category name in the API: SQL_LOG_DISCONNECTIONS_DISABLED	Finding description: The log_disconnections database flag for a Cloud SQL for PostgreSQL instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_disconnections", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.3 CIS GCP Foundation 1.2: 6.2.4
SQL log duration disabled Category name in the API: SQL_LOG_DURATION_DISABLED	Finding description: The log_duration database flag for a Cloud SQL for PostgreSQL instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_duration", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.5
SQL log error verbosity Category name in the API: SQL_LOG_ERROR_VERBOSITY	Finding description: The log_error_verbosity database flag for a Cloud SQL for PostgreSQL instance is not set to default or stricter. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_error_verbosity field is set to default or terse. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.2
SQL log lock waits disabled Category name in the API: SQL_LOG_LOCK_WAITS_DISABLED	Finding description: The log_lock_waits database flag for a Cloud SQL for PostgreSQL instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_lock_waits", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.4 CIS GCP Foundation 1.2: 6.2.6
SQL log min duration statement enabled Category name in the API: SQL_LOG_MIN_DURATION_STATEMENT_ENABLED	Finding description: The log_min_duration_statement database flag for a Cloud SQL for PostgreSQL instance is not set to "-1". Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_min_duration_statement", "value": "-1". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.7 CIS GCP Foundation 1.2: 6.2.16
SQL log min error statement Category name in the API: SQL_LOG_MIN_ERROR_STATEMENT	Finding description: The log_min_error_statement database flag for a Cloud SQL for PostgreSQL instance is not set appropriately. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the log_min_error_statement field of the databaseFlags property is set to one of the following values: debug5, debug4, debug3, debug2, debug1, info, notice, warning, or the default value error. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.5
SQL log min error statement severity Category name in the API: SQL_LOG_MIN_ERROR_STATEMENT_SEVERITY	Finding description: The log_min_error_statement database flag for a Cloud SQL for PostgreSQL instance does not have an appropriate severity level. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the log_min_error_statement field of the databaseFlags property is set to one of the following values: error, log, fatal, or panic. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.14
SQL log min messages Category name in the API: SQL_LOG_MIN_MESSAGES	Finding description: The log_min_messages database flag for a Cloud SQL for PostgreSQL instance is not set to warning. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the log_min_messages field of the databaseFlags property is set to warning. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.13
SQL log executor stats enabled Category name in the API: SQL_LOG_EXECUTOR_STATS_ENABLED	Finding description: The log_executor_status database flag for a Cloud SQL for PostgreSQL instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_executor_status field is set to on. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.11
SQL log hostname enabled Category name in the API: SQL_LOG_HOSTNAME_ENABLED	Finding description: The log_hostname database flag for a Cloud SQL for PostgreSQL instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_hostname field is set to on. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.8
SQL log parser stats enabled Category name in the API: SQL_LOG_PARSER_STATS_ENABLED	Finding description: The log_parser_stats database flag for a Cloud SQL for PostgreSQL instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_parser_stats field is set to on. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.9
SQL log planner stats enabled Category name in the API: SQL_LOG_PLANNER_STATS_ENABLED	Finding description: The log_planner_stats database flag for a Cloud SQL for PostgreSQL instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_planner_stats field is set to on. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.10
SQL log statement Category name in the API: SQL_LOG_STATEMENT	Finding description: The log_statement database flag for a Cloud SQL for PostgreSQL instance is not set to Ddl (all data definition statements). Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_statement field is set to Ddl. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.7
SQL log statement stats enabled Category name in the API: SQL_LOG_STATEMENT_STATS_ENABLED	Finding description: The log_statement_stats database flag for a Cloud SQL for PostgreSQL instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks if the databaseFlags property of instance metadata for the log_statement_stats field is set to on. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.2.12
SQL log temp files Category name in the API: SQL_LOG_TEMP_FILES	Finding description: The log_temp_files database flag for a Cloud SQL for PostgreSQL instance is not set to "0". Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "log_temp_files", "value": "0". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.2.6 CIS GCP Foundation 1.2: 6.2.15
SQL no root password Category name in the API: SQL_NO_ROOT_PASSWORD	Finding description: A Cloud SQL database doesn't have a password configured for the root account. This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the rootPassword property of the root account is empty. Additional IAM permissions: roles/cloudsql.client Additional inputs: Queries live instances Batch scans: Every 6 hours Real-time scans: No	CIS GCP Foundation 1.0: 6.3 CIS GCP Foundation 1.1: 6.1.1 CIS GCP Foundation 1.2: 6.1.1 PCI-DSS v3.2.1: 2.1 NIST 800-53: AC-3 ISO-27001: A.8.2.3, A.9.4.2
SQL public IP Category name in the API: SQL_PUBLIC_IP	Finding description: A Cloud SQL database has a public IP address. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks whether the IP address type of an Cloud SQL database is set to Primary, indicating it is public. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.1: 6.6 CIS GCP Foundation 1.2: 6.6
SQL remote access enabled Category name in the API: SQL_REMOTE_ACCESS_ENABLED	Finding description: The remote access database flag for a Cloud SQL for SQL Server instance is not set to off. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "remote access", "value": "off". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.3.5
SQL skip show database disabled Category name in the API: SQL_SKIP_SHOW_DATABASE_DISABLED	Finding description: The skip_show_database database flag for a Cloud SQL for MySQL instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "skip_show_database", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.1.2
SQL trace flag 3625 Category name in the API: SQL_TRACE_FLAG_3625	Finding description: The 3625 (trace flag) database flag for a Cloud SQL for SQL Server instance is not set to on. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "3625 (trace flag)", "value": "on". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.3.6
SQL user connections configured Category name in the API: SQL_USER_CONNECTIONS_CONFIGURED	Finding description: The user connections database flag for a Cloud SQL for SQL Server instance is configured. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "user connections", "value": "0". Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.3.3
SQL user options configured Category name in the API: SQL_USER_OPTIONS_CONFIGURED	Finding description: The user options database flag for a Cloud SQL for SQL Server instance is configured. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Checks the databaseFlags property of instance metadata for the key-value pair "name": "user options", "value": "" (empty). Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.2: 6.3.4
SQL weak root password Category name in the API: SQL_WEAK_ROOT_PASSWORD	Finding description: A Cloud SQL database has a weak password configured for the root account. This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets sqladmin.googleapis.com/Instance Fix this finding	Compares the password for the root account of your Cloud SQL database to a list of common passwords. Additional IAM permissions: roles/cloudsql.client Additional inputs: Queries live instances Batch scans: Every 6 hours Real-time scans: No

Storage vulnerability findings

Vulnerabilities of this detector type all relate to Cloud Storage Buckets configurations, and belong to theSTORAGE_SCANNERtype.

Table 18. Storage scanner

Detector	Summary	Asset scan settings	Compliance standards
Bucket CMEK disabled Category name in the API: BUCKET_CMEK_DISABLED	Finding description: A bucket is not encrypted with customer-managed encryption keys (CMEK). This detector requires additional configuration to enable. For instructions, see Enable and disable detectors. Pricing tier: Premium Supported assets storage.googleapis.com/Bucket Fix this finding	Checks the encryption field in bucket metadata for the resource name of your CMEK. Batch scans: Every 6 hours Real-time scans: Yes
Bucket policy only disabled Category name in the API: BUCKET_POLICY_ONLY_DISABLED	Finding description: Uniform bucket-level access, previously called Bucket Policy Only, isn't configured. Pricing tier: Premium Supported assets storage.googleapis.com/Bucket Fix this finding	Checks whether the uniformBucketLevelAccess property on a bucket is set to "enabled":false Batch scans: Every 6 hours Real-time scans: Yes
Public bucket ACL Category name in the API: PUBLIC_BUCKET_ACL	Finding description: A Cloud Storage bucket is publicly accessible. Pricing tier: Premium or Standard Supported assets storage.googleapis.com/Bucket Fix this finding	Checks the IAM allow policy of a bucket for public roles, allUsers or allAuthenticatedUsers, with admin or editor privileges. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 5.1 CIS GCP Foundation 1.1: 5.1 CIS GCP Foundation 1.2: 5.1 PCI-DSS v3.2.1: 7.1 NIST 800-53: AC-2 ISO-27001: A.8.2.3, A.14.1.3
Public log bucket Category name in the API: PUBLIC_LOG_BUCKET	Finding description: A storage bucket used as a log sink is publicly accessible. Pricing tier: Premium or Standard Supported assets storage.googleapis.com/Bucket Fix this finding	Checks the IAM allow policy of a bucket for the principals allUsers or allAuthenticatedUsers, which grant public access. Additional inputs: Reads the log sink (the log filter and log destination) for a bucket to determine whether it is a log bucket Batch scans: Every 6 hours Real-time scans: Yes, but only if IAM policy on bucket changes, not if log sink is changed	PCI-DSS v3.2.1: 10.5 NIST 800-53: AU-9 ISO-27001: A.8.2.3, A.12.4.2, A.18.1.3

Subnetwork vulnerability findings

Vulnerabilities of this detector type all relate to an organization's subnetwork configurations, and belong to theSUBNETWORK_SCANNERtype.

Table 19. Subnetwork scanner

Detector	Summary	Asset scan settings	Compliance standards
Flow logs disabled Category name in the API: FLOW_LOGS_DISABLED	Finding description: There is a VPC subnetwork that has flow logs disabled. Pricing tier: Premium Supported assets compute.googleapis.com/Subnetwork Fix this finding	Checks whether the enableFlowLogs property of Compute Engine subnetworks is missing or set to false. Assets excluded from scans: Serverless VPC Access, load balancer subnetworks Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.9 CIS GCP Foundation 1.1: 3.8 CIS GCP Foundation 1.2: 3.8 PCI-DSS v3.2.1: 10.1, 10.2 NIST 800-53: SI-4 ISO-27001: A.13.1.1
Private Google access disabled Category name in the API: PRIVATE_GOOGLE_ACCESS_DISABLED	Finding description: There are private subnetworks without access to Google public APIs. Pricing tier: Premium Supported assets storage.googleapis.com/Bucket compute.googleapis.com/Subnetwork Fix this finding	Checks whether the privateIpGoogleAccess property of Compute Engine subnetworks is set to false. Batch scans: Every 6 hours Real-time scans: Yes	CIS GCP Foundation 1.0: 3.8

Web Security Scanner findings

Important: Managed scans are only available in Security Command Center Premium tier.

Web Security Scanner custom and managed scans identify the following finding types. In the Standard tier, Web Security Scanner supports custom scans of deployed applications with public URLs and IPs that aren't behind a firewall.

Table 20. Web Security Scanner findings

Category	Finding description	OWASP 2017 Top 10	OWASP 2021 Top 10
Accessible Git repository Category name in the API: ACCESSIBLE_GIT_REPOSITORY	A Git repository is exposed publicly. To resolve this finding, remove unintentional public access to the GIT repository. Pricing tier: Standard Fix this finding	A5	A01
Accessible SVN repository Category name in the API: ACCESSIBLE_SVN_REPOSITORY	An SVN repository is exposed publicly. To resolve this finding, remove public unintentional access to the SVN repository. Pricing tier: Standard Fix this finding	A5	A01
Cacheable password input Category name in the API: CACHEABLE_PASSWORD_INPUT	Passwords entered on the web application can be cached in a regular browser cache instead of a secure password storage. Pricing tier: Premium Fix this finding	A3	A04
Clear text password Category name in the API: CLEAR_TEXT_PASSWORD	Passwords are being transmitted in clear text and can be intercepted. To resolve this finding, encrypt the password transmitted over the network. Pricing tier: Standard Fix this finding	A3	A02
Insecure allow origin ends with validation Category name in the API: INSECURE_ALLOW_ORIGIN_ENDS_WITH_VALIDATION	A cross-site HTTP or HTTPS endpoint validates only a suffix of the Origin request header before reflecting it inside the Access-Control-Allow-Origin response header. To resolve this finding, validate that the expected root domain is part of the Origin header value before reflecting it in the Access-Control-Allow-Origin response header. For subdomain wildcards, prepend the dot to the root domain—for example, .endsWith(".google.com"). Pricing tier: Premium Fix this finding	A5	A01
Insecure allow origin starts with validation Category name in the API: INSECURE_ALLOW_ORIGIN_STARTS_WITH_VALIDATION	A cross-site HTTP or HTTPS endpoint validates only a prefix of the Origin request header before reflecting it inside the Access-Control-Allow-Origin response header. To resolve this finding, validate that the expected domain fully matches the Origin header value before reflecting it in the Access-Control-Allow-Origin response header—for example, .equals(".google.com"). Pricing tier: Premium Fix this finding	A5	A01
Invalid content type Category name in the API: INVALID_CONTENT_TYPE	A resource was loaded that doesn't match the response's Content-Type HTTP header. To resolve this finding, set X-Content-Type-Options HTTP header with the correct value. Pricing tier: Standard Fix this finding	A6	A05
Invalid header Category name in the API: INVALID_HEADER	A security header has a syntax error and is ignored by browsers. To resolve this finding, set HTTP security headers correctly. Pricing tier: Standard Fix this finding	A6	A05
Mismatching security header values Category name in the API: MISMATCHING_SECURITY_HEADER_VALUES	A security header has duplicated, mismatching values, which result in undefined behavior. To resolve this finding, set HTTP security headers correctly. Pricing tier: Standard Fix this finding	A6	A05
Misspelled security header name Category name in the API: MISSPELLED_SECURITY_HEADER_NAME	A security header is misspelled and is ignored. To resolve this finding, set HTTP security headers correctly. Pricing tier: Standard Fix this finding	A6	A05
Mixed content Category name in the API: MIXED_CONTENT	Resources are being served over HTTP on an HTTPS page. To resolve this finding, make sure that all resources are served over HTTPS. Pricing tier: Standard Fix this finding	A6	A05
Outdated library Category name in the API: OUTDATED_LIBRARY	A library was detected that has known vulnerabilities. To resolve this finding, upgrade libraries to a newer version. Pricing tier: Standard Fix this finding	A9	A06
Server side request forgery Category name in the API: SERVER_SIDE_REQUEST_FORGERY	A server-side request forgery (SSRF) vulnerability was detected. To resolve this finding, use an allowlist to limit the domains and IP addresses that the web application can make requests to. Pricing tier: Standard Fix this finding	Not applicable	A10
Session ID leak Category name in the API: SESSION_ID_LEAK	When making a cross-domain request, the web application includes the user's session identifier in its Referer request header. This vulnerability gives the receiving domain access to the session identifier, which can be used to impersonate or uniquely identify the user. Pricing tier: Premium Fix this finding	A2	A07
SQL injection Category name in the API: SQL_INJECTION	A potential SQL injection vulnerability was detected. To resolve this finding, use parameterized queries to prevent user inputs from influencing the structure of the SQL query. Pricing tier: Premium Fix this finding	A1	A03
Struts insecure deserialization Category name in the API: STRUTS_INSECURE_DESERIALIZATION	The use of a vulnerable version of Apache Struts was detected. To resolve this finding, upgrade Apache Struts to the latest version. Pricing tier: Premium Fix this finding	A8	A08
XSS Category name in the API: XSS	A field in this web application is vulnerable to a cross-site scripting (XSS) attack. To resolve this finding, validate and escape untrusted user-supplied data. Pricing tier: Standard Fix this finding	A7	A03
XSS angular callback Category name in the API: XSS_ANGULAR_CALLBACK	A user-provided string isn't escaped and AngularJS can interpolate it. To resolve this finding, validate and escape untrusted user-supplied data handled by Angular framework. Pricing tier: Standard Fix this finding	A7	A03
XSS error Category name in the API: XSS_ERROR	A field in this web application is vulnerable to a cross-site scripting attack. To resolve this finding, validate and escape untrusted user-supplied data. Pricing tier: Standard Fix this finding	A7	A03
XXE reflected file leakage Category name in the API: XXE_REFLECTED_FILE_LEAKAGE	An XML External Entity (XXE) vulnerability was detected. This vulnerability can cause the web application to leak a file on the host. To resolve this finding, configure your XML parsers to disallow external entities. Pricing tier: Premium Fix this finding	A4	A05

CIS benchmarks

The Center for Internet Security (CIS) includes the following benchmarks that Web Security Scanner or Security Health Analytics detectors, currently, don't support:

Table 21. CIS benchmarks

Category	Finding description	CIS GCP Foundation 1.0	NIST 800-53	ISO-27001
Basic authentication enabled Category name in the API: BASIC_AUTHENTICATION_ENABLED	IAM or client certificate authentication should be enabled on Kubernetes Clusters.	7.10
Client cert authentication disabled Category name in the API: CLIENT_CERT_AUTHENTICATION_DISABLED	Kubernetes Clusters should be created with Client Certificate enabled.	7.12
Labels not used Category name in the API: LABELS_NOT_USED	Labels can be used to break down billing information.	7.5
Public storage object Category name in the API: PUBLIC_STORAGE_OBJECT	Storage object ACL should not grant access to **allUsers**.	5.2
SQL broad root login Category name in the API: SQL_BROAD_ROOT_LOGIN	Root access to a SQL database should be limited to allowlisted trusted IPs.	6.4

Rapid Vulnerability Detection findings and remediations

Rapid Vulnerability Detection detects weak credentials, incomplete software installations, and other critical vulnerabilities that have a high likelihood of being exploited. The service automatically discovers network endpoints, protocols, open ports, network services, and installed software packages.

Rapid Vulnerability Detection findings are early warnings of vulnerabilities that we recommend you fix immediately.

For information about how to view the findings, see Reviewing findings in Security Command Center.

Rapid Vulnerability Detection scans identify the following finding types.

Table 22. Rapid Vulnerability Detection findings and remediations

Finding type	Finding description	OWASP top 10 codes
Weak credential findings
WEAK_CREDENTIALS	This detector checks for weak credentials using ncrack brute force methods. Supported services: SSH, RDP, FTP, WordPress, TELNET, POP3, IMAP, VCS, SMB, SMB2, VNC, SIP, REDIS, PSQL, MYSQL, MSSQL, MQTT, MONGODB, WINRM, DICOM Remediation: Enforce a strong password policy. Create unique credentials for your services and avoid using dictionary words in passwords.	2021   A07 2017   A2
Exposed interface findings
ELASTICSEARCH_API_EXPOSED	The Elasticsearch API lets callers perform arbitrary queries, write and execute scripts, and add additional documents to the service. Remediation: Remove direct access to the Elasticsearch API by routing requests through an application, or limit access to authenticated users only. For more information, see Security settings in Elasticsearch.	2021   A01, A05 2017   A5, A6
EXPOSED_GRAFANA_ENDPOINT	In Grafana 8.0.0 to 8.3.0, users can access without authentication an endpoint that has a directory traversal vulnerability that allows any user to read any file on the server without authentication. For more information, see CVE-2021-43798. Remediation: Patch Grafana or upgrade Grafana to a later version. For more information, see Grafana path traversal.	2021   A06, A07 2017   A2, A9
EXPOSED_METABASE	Versions x.40.0 to x.40.4 of Metabase, an open source data analytics platform, contain a vulnerability in the custom GeoJSON map support and potential local file inclusion, including environment variables. URLs were not validated prior to being loaded. For more information, see CVE-2021-41277. Remediation: Upgrade to maintenance releases 0.40.5 or later or 1.40.5 or later. For more information, see GeoJSON URL validation can expose server files and environment variables to unauthorized users.	2021   A06 2017   A3, A9
EXPOSED_SPRING_BOOT_ACTUATOR_ENDPOINT	This detector checks whether sensitive Actuator endpoints of Spring Boot applications are exposed. Some of the default endpoints, like /heapdump, might expose sensitive information. Other endpoints, like /env, might lead to remote code execution. Currently, only /heapdump is checked. Remediation: Disable access to sensitive Actuator endpoints. For more information, see Securing HTTP Endpoints.	2021   A01, A05 2017   A5, A6
HADOOP_YARN_UNAUTHENTICATED_RESOURCE_MANAGER_API	This detector checks whether the Hadoop Yarn ResourceManager API, which controls the computation and storage resources of a Hadoop cluster, is exposed and allows unauthenticated code execution. Remediation: Use access control lists with the API.	2021   A01, A05 2017   A5, A6
JAVA_JMX_RMI_EXPOSED	The Java Management Extension (JMX) allows remote monitoring and diagnostics for Java applications. Running JMX with unprotected Remote Method Invocation endpoint allows any remote users to create a javax.management.loading.MLet MBean and use it to create new MBeans from arbitrary URLs. Remediation: To properly configure remote monitoring, see Monitoring and Management Using JMX Technology.	2021   A01, A05 2017   A5, A6
JUPYTER_NOTEBOOK_EXPOSED_UI	This detector checks whether an unauthenticated Jupyter Notebook is exposed. Jupyter allows remote code execution by design on the host machine. An unauthenticated Jupyter Notebook puts the hosting VM at risk of remote code execution. Remediation: Add token authentication to your Jupyter Notebook server, or use more recent versions of Jupyter Notebook that use token authentication by default.	2021   A01, A05 2017   A5, A6
KUBERNETES_API_EXPOSED	The Kubernetes API is exposed, and can be accessed by unauthenticated callers. This allows arbitrary code execution on the Kubernetes cluster. Remediation: Require authentication for all API requests. For more information, see the Kubernetes API Authenticating guide.	2021   A01, A05 2017   A5, A6
UNFINISHED_WORDPRESS_INSTALLATION	This detector checks whether a WordPress installation is unfinished. An unfinished WordPress installation exposes the /wp-admin/install.php page, which allows attacker to set the admin password and, possibly, compromise the system. Remediation: Complete the WordPress installation.	2021   A05 2017   A6
UNAUTHENTICATED_JENKINS_NEW_ITEM_CONSOLE	This detector checks for an unauthenticated Jenkins instance by sending a probe ping to the /view/all/newJob endpoint as an anonymous visitor. An authenticated Jenkins instance shows the createItem form, which allows the creation of arbitrary jobs that could lead to remote code execution. Remediation: Follow Jenkins' guide on managing security to block unauthenticated access.	2021   A01, A05 2017   A5, A6
Vulnerable software findings
APACHE_HTTPD_RCE	A flaw was found in Apache HTTP Server 2.4.49 that allows an attacker to use a path traversal attack to map URLs to files outside the expected document root and see the source of interpreted files, like CGI scripts. This issue is known to be exploited in the wild. This issue affects Apache 2.4.49 and 2.4.50 but not earlier versions. For more information about this vulnerability, see: CVE record CVE-2021-41773 Apache HTTP Server 2.4 vulnerabilities Remediation: Protect files outside of the document root by configuring the "require all denied" directive in the Apache HTTP Server.	2021   A01, A06 2017   A5, A9
APACHE_HTTPD_SSRF	Attackers can craft a URI to the Apache web server that causes mod_proxy to forward the request to an origin server that is chosen by the attacker. This issue affects Apache HTTP server 2.4.48 and earlier. For more information about this vulnerability, see: CVE record CVE-2021-40438 Apache HTTP Server 2.4 vulnerabilities Remediation: Upgrade the Apache HTTP server to a later version.	2021   A06, A10 2017   A9
CONSUL_RCE	Attackers can execute arbitrary code on a Consul server because the Consul instance is configured with -enable-script-checks set to true and the Consul HTTP API is unsecured and accessible over the network. In Consul 0.9.0 and earlier, script checks are on by default. For more information, see Protecting Consul from RCE Risk in Specific Configurations. To check for this vulnerability, Rapid Vulnerability Detection registers a service on the Consul instance by using the /v1/health/service REST endpoint, which then executes one of the following: A curl command to a remote server outside of the network. An attacker can use the curl command to exfiltrate data from the server. A printf command. Rapid Vulnerability Detection then verifies the output of the command by using the /v1/health/service REST endpoint. After the check, Rapid Vulnerability Detection cleans up and deregisters the service by using the /v1/agent/service/deregister/ REST endpoint. Remediation: Set enable-script-checks to false in the Console instance configuration.	2021   A05, A06 2017   A6, A9
DRUID_RCE	Apache Druid includes the ability to execute user-provided JavaScript code embedded in various types of requests. This functionality is intended for use in high-trust environments, and is disabled by default. However, in Druid 0.20.0 and earlier, it is possible for an authenticated user to send a specially-crafted request that forces Druid to run user-provided JavaScript code for that request, regardless of server configuration. This can be leveraged to execute code on the target machine with the privileges of the Druid server process. For more information, see CVE-2021-25646 Detail. Remediation: Upgrade Apache Druid to later version.	2021   A05, A06 2017   A6, A9
DRUPAL_RCE This category includes two vulnerabilities in Drupal. Multiple findings of this type can indicate more than one vulnerability.	Drupal versions before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1 are vulnerable to remote code execution on Form API AJAX requests. Remediation: Upgrade to alternate Drupal versions.	2021   A06 2017   A9
	Drupal versions 8.5.x before 8.5.11 and 8.6.x before 8.6.10 are vulnerable to remote code execution when either the RESTful Web Service module or the JSON:API is enabled. This vulnerability can be exploited by an unauthenticated attacker using a custom POST request. Remediation: Upgrade to alternate Drupal versions.	2021   A06 2017   A9
FLINK_FILE_DISCLOSURE	A vulnerability in Apache Flink versions 1.11.0, 1.11.1, and 1.11.2 lets attackers read any file on the local filesystem of the JobManager through the REST interface of the JobManager process. Access is restricted to files accessible by the JobManager process. Remediation: If your Flink instances are exposed, upgrade to Flink 1.11.3 or 1.12.0.	2021   A01, A05, A06 2017   A5, A6, A9
GITLAB_RCE	In GitLab Community Edition (CE) and Enterprise Edition (EE) versions 11.9 and later, GitLab does not properly validate image files that are passed to a file parser. An attacker can exploit this vulnerability for remote command execution. Remediation: Upgrade to GitLab CE or EE release 13.10.3, 13.9.6, and 13.8.8 or later. For more information, see Action needed by self-managed customers in response to CVE-2021-22205.	2021   A06 2017   A9
GoCD_RCE	In GoCD 21.2.0 and earlier, there is an endpoint that can be accessed without authentication. This endpoint has a directory traversal vulnerability that allows a user to read any file on the server without authentication. Remediation: Upgrade to version 21.3.0 or later. For more information, see Release notes of GoCD 21.3.0.	2021   A06, A07 2017   A2, A9
JENKINS_RCE	Jenkins versions 2.56 and earlier, and 2.46.1 LTS and earlier are vulnerable to remote code execution. This vulnerability can be triggered by an unauthenticated attacker using a malicious serialized Java object. Remediation: Install an alternate Jenkins version.	2021   A06, A08 2017   A8, A9
JOOMLA_RCE This category includes two vulnerabilities in Joomla. Multiple findings of this type can indicate more than one vulnerability.	Joomla versions 1.5.x, 2.x, and 3.x before 3.4.6 are vulnerable to remote code execution. This vulnerability can be triggered with a crafted header containing serialized PHP objects. Remediation: Install an alternate Joomla version.	2021   A06, A08 2017   A8, A9
	Joomla versions 3.0.0 through 3.4.6 are vulnerable to remote code execution. This vulnerability can be triggered by sending a POST request that contains a crafted serialized PHP object. Remediation: Install an alternate Joomla version.	2021   A06 2017   A9
LOG4J_RCE	In Apache Log4j2 2.14.1 and earlier, JNDI features that are used in configurations, log messages, and parameters do not protect against attacker-controlled LDAP and other JNDI related endpoints. For more information, see CVE-2021-44228. Remediation: For remediation information, see Apache Log4j Security Vulnerabilities.	2021   A06 2017   A9
MANTISBT_PRIVILEGE_ESCALATION	MantisBT through version 2.3.0 allows arbitrary password reset and unauthenticated admin access by supplying an empty confirm_hash value to verify.php. Remediation: Update MantisBT to a newer version or follow the Mantis instructions to apply a critical security fix.	2021   A06 2017   A9
OGNL_RCE	Confluence Server and Data Center instances contain an OGNL injection vulnerability that allows an unauthenticated attacker to execute arbitrary code. For more information, see CVE-2021-26084. Remediation: For remediation information, see Confluence Server Webwork OGNL injection - CVE-2021-26084.	2021   A03 2017   A1
OPENAM_RCE	OpenAM server 14.6.2 and earlier and ForgeRock AM server 6.5.3 and earlier have a Java deserialization vulnerability in the jato.pageSession parameter on multiple pages. The exploitation does not require authentication, and remote code execution can be triggered by sending a single crafted /ccversion/* request to the server. The vulnerability exists due to the usage of Sun ONE Application. For more information, see CVE-2021-35464. Remediation: Upgrade to a more recent version. For information about the ForgeRock remediation, see AM Security Advisory #202104.	2021   A06 2017   A9
ORACLE_WEBLOGIC_RCE	Certain versions of the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Console) contain a vulnerability, including versions 10.3.6.0.0, 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. This easily exploitable vulnerability allows an unauthenticated attacker with network access via HTTP to compromise an Oracle WebLogic Server. Successful attacks of this vulnerability can result in a takeover of Oracle WebLogic Server. For more information, see CVE-2020-14882. Remediation: For patch information, see Oracle Critical Patch Update Advisory - October 2020.	2021   A06, A07 2017   A2, A9
PHPUNIT_RCE	PHPUnit versions prior to 5.6.3 allow remote code execution with a single unauthenticated POST request. Remediation: Upgrade to newer PHPUnit versions.	2021: A05 2017: A6
PHP_CGI_RCE	PHP versions before 5.3.12, and versions 5.4.x before 5.4.2, when configured as a CGI script, allow remote code execution. The vulnerable code does not properly handle query strings that lack an = (equals sign) character. This lets attackers add command line options that are executed on the server. Remediation: Install an alternate PHP version.	2021   A05, A06 2017   A6, A9
PORTAL_RCE	Deserialization of untrusted data in Liferay Portal versions prior to 7.2.1 CE GA2 allows remote attackers to execute arbitrary code through JSON web services. Remediation: Upgrade to newer Liferay Portal versions.	2021   A06, A08 2017   A8, A9
REDIS_RCE	If a Redis instance does not require authentication to execute admin commands, attackers might be able to execute arbitrary code. Remediation: Configure Redis to require authentication.	2021   A01, A05 2017   A5, A6
SOLR_FILE_EXPOSED	Authentication is not enabled in Apache Solr, an open source search server. When Apache Solr does not require authentication, an attacker can directly craft a request to enable a specific configuration, and eventually implement a server-side request forgery (SSRF) or read arbitrary files. Remediation: Upgrade to alternate Apache Solr versions.	2021   A07, A10 2017   A2
SOLR_RCE	Apache Solr versions 5.0.0 through Apache Solr 8.3.1 are vulnerable to remote code execution through the VelocityResponseWriter if params.resource.loader.enabled is set to true. This allows attackers to create a parameter that contains a malicious Velocity template. Remediation: Upgrade to alternate Apache Solr versions.	2021   A06 2017   A9
STRUTS_RCE This category includes three vulnerabilities in Apache Struts. Multiple findings of this type can indicate more than one vulnerability.	Apache Struts versions before 2.3.32 and 2.5.x before 2.5.10.1 are vulnerable to remote code execution. The vulnerability can be triggered by an unauthenticated attacker providing a crafted Content-Type header. Remediation: Install an alternate Apache Struts version.	2021   A06 2017   A9
	The REST plugin in Apache Struts versions 2.1.1 through 2.3.x before 2.3.34 and 2.5.x before 2.5.13 are vulnerable to remote code execution when deserializing crafted XML payloads. Remediation: Install an alternate Apache Struts version.	2021   A06, A08 2017   A8, A9
	Apache