CIS Google Cloud Platform Foundation Benchmark v1.2.0/Networking/36 of 83
3.9Ensure no HTTPS or SSL proxy load balancers permit SSL policies with weak cipher suites
Control family: Networking
Control description
Secure Sockets Layer (SSL) policies determine what port Transport Layer Security (TLS) features clients are permitted to use when connecting to load balancers. To prevent usage of insecure features, SSL policies should use (a) at least TLS 1.2 with the MODERN profile; or (b) the RESTRICTED profile, because it effectively requires clients to use TLS 1.2 regardless of the chosen minimum TLS version; or (3) a CUSTOM profile that does not support any of the following features:
```
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
```
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
An SSL policy decides which TLS versions and cipher suites an HTTPS or SSL proxy load balancer will agree to. The default policy still accepts old versions and weak RSA key exchange ciphers. Every such load balancer uses a policy with TLS 1.2 as the minimum and the MODERN or RESTRICTED profile, or a CUSTOM profile without the weak suites.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree the TLS standard for public endpoints: TLS 1.2 or later and the MODERN or RESTRICTED profile.
- Check with owners of old clients that they can connect before the change.
Evidence
- The TLS standard for load balancers
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks create a strong SSL policy in Network Security, attach it to each load balancer's HTTPS or SSL front end, and watch with Security Command Center.
Task 1Create a strong SSL policy
- Sign in to the Google Cloud console at console.cloud.google.com and open Network Security > SSL policies.
- Choose Create policy and give it a name such as tls12-modern.
- Set Minimum TLS version to TLS 1.2 and Profile to Modern or Restricted.
- Choose Create.
- Check it: the policy is listed with the minimum version and profile you chose.
Task 2Attach the policy to each HTTPS or SSL proxy load balancer
- Open Network services > Load balancing, choose the Target proxies tab, and note the proxies the finding names.
- Open each load balancer and choose Edit, then Frontend configuration.
- For each HTTPS or SSL frontend, set SSL policy to the new policy and choose Done.
- Choose Update.
- Check it: Network Security > SSL policies shows each load balancer in the policy's In use by column.
Task 3Keep it checked with the Security Health Analytics finding WEAK_SSL_POLICY
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category WEAK_SSL_POLICY with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and attach a strong policy to the proxy it names.
- Check it: after the next Security Health Analytics scan, no active WEAK_SSL_POLICY finding remains.
Evidence
- The SSL policy, showing TLS 1.2 and its profile, and the load balancers using it
- Security Command Center, with no active WEAK_SSL_POLICY finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.