> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec-gcp-4.md).

# GCP HTTPS Load balancer is set with SSL policy having TLS version 1.1 or lower misconfiguration dete

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_4                             |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | GCP                                        |
| Severity               | MEDIUM                                     |
| Framework              | Terraform, Terraform Plan                  |

## Impact

Secure Sockets Layer (SSL) policies determine what port Transport Layer Security (TLS) features clients are permitted to use when connecting to load balancers. SSL policies control the features of SSL in Google Cloud SSL proxy load balancer and external HTTP(S) load balancers. By default, HTTP(S) Load Balancing and SSL Proxy Load Balancing use a set of SSL features that provides good security and wide compatibility. To prevent usage of insecure features, SSL policies should use one of the following three options:

. At least TLS 1.2 with the MODERN profile; + or

. The RESTRICTED profile, because it effectively requires clients to use TLS 1.2 regardless of the chosen minimum TLS version; + or

. 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: they distribute traffic from the Internet to a GCP network. + GCP customers can configure load balancer SSL policies with a minimum TLS version (1.0, 1.1, or 1.2) that clients can use to establish a connection, along with a profile (Compatible, Modern, Restricted, or Custom) that specifies permissible and insecure cipher suites. + It is easy for customers to configure a load balancer without knowing they are permitting outdated cipher suites. + It is possible to define SSL policies to control the features of SSL that your load balancer negotiates with clients. + An SSL policy can be configured to determine the minimum TLS version and SSL features that are enabled in the load balancer. + We recommend you select TLS 1.2 as the minimum TLS version supported.

## How to Fix

*Resource:* google\_compute\_ssl\_policy

* *Arguments:* profile = MODERN
* *Resource:* google\_compute\_ssl\_policy
* *Arguments:* profile = CUSTOM custom\_features = \[] //Option 1 \[source,go]

***

resource "google\_compute\_ssl\_policy" "modern-profile" { name = "nonprod-ssl-policy"

* profile = "MODERN"
* min\_tls\_version = "TLS\_1\_2" }

//Option 2 resource "google\_compute\_ssl\_policy" "custom-profile" { name = "custom-ssl-policy"

* profile = "CUSTOM" min\_tls\_version = "TLS\_1\_2"
* custom\_features = \["TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384", "TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384"] }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/public-exposure/appsec-gcp-4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.