Google Cloud
TMA-GCP-3.11
Ensure No HTTPS or SSL Proxy Load Balancers Permit SSL Policies With Weak Cipher Suites
Описание
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 Load balancers are used to efficiently distribute traffic across multiple servers. Both SSL proxy and HTTPS load balancers are external load balancers, meaning they distribute traffic from the Internet to a GCP network. GCP customers can configure load balancer SSL p...
Как проверяется
Метод проверки: Ручная проверка
From Google Cloud Console 1. See all load balancers by visiting https://console.cloud.google.com/net- services/loadbalancing/loadBalancers/list. 2. For each load balancer for SSL (Proxy) or HTTPS, click on its name to go the Load balancer details page. 3. Ensure that each target proxy entry in the Frontend table has an SSL Policy configured. 4. Click on each SSL policy to go to its SSL policy details page. 5. Ensure that the SSL policy satisfies one of the following conditions: - has a Min TLS set to TLS 1.2 and Profile set to Modern profile, or - has Profile set to Restricted. Note that a Restricted profile effectively requires clients to use TLS 1.2 regardless of the chosen minimum TLS version, or - has Profile set to Custom and the following features are all disabled: 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 From Google Cloud CLI 1. List all TargetHttpsProxies and TargetSslProxies. gcloud compute target-https-proxies list gcloud compute target-ssl-proxies list 2. For each target proxy, list its properties: gcloud compute target-https-proxies describe TARGET_HTTPS_PRO...
Как исправляется
Метод исправления: Рекомендация или патч инфраструктуры
From Google Cloud Console If the TargetSSLProxy or TargetHttpsProxy does not have an SSL policy configured, create a new SSL policy. Otherwise, modify the existing insecure policy. 1. Navigate to the SSL Policies page by visiting: https://console.cloud.google.com/net-security/sslpolicies 2. Click on the name of the insecure policy to go to its SSL policy details page. 3. Click EDIT. 4. Set Minimum TLS version to TLS 1.2. 5. Set Profile to Modern or Restricted. 6. Alternatively, if teh user selects the profile Custom, make sure that the following features are disabled: 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 From Google Cloud CLI 1. For each insecure SSL policy, update it to use secure cyphers: gcloud compute ssl-policies update NAME [--profile COMPATIBLE|MODERN|RESTRICTED|CUSTOM] --min-tls-version 1.2 [--custom-features FEATURES] 2. If the target proxy has a GCP default SSL policy, use the following command corresponding to the proxy type to update it. gcloud compute target-ssl-proxies update TARGET_SSL_PROXY_NAME --ssl-policy SSL_POLICY_NAME gcloud compute target-http...
Свойства
- Операционные системы
- Любая
- Теги
- cloudgcptls
- Источник
- CIS Google Cloud Platform Foundation Benchmark v5.0.0 - 3.11 Ensure No HTTPS or SSL Proxy Load Balancers Permit SSL Policies With Weak Cipher Suites