> 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/appsec2-gcp-10.md).

# GCP Cloud Function HTTP trigger is not secured misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_10                     |
| Category - Subcategory | Public Exposure - APIs               |
| Provider               | GCP                                  |
| Severity               | MEDIUM                               |
| Framework              | Terraform                            |
| Mapped CSPM/KSPM Rule  | ff6a26a5-f036-4d3a-a650-d5de1d568bab |

## Impact

This rule identifies GCP Cloud Functions for which the HTTP trigger is not secured. When you configure HTTP functions to be triggered only with HTTPS, user requests will be redirected to use the HTTPS protocol, which is more secure. It is recommended to set the 'Require HTTPS' for configuring HTTP triggers while deploying your function.

## How to Fix

## \[source,go]

resource "google\_cloudfunctions\_function" "pass" { name = "function-test" description = "My function" runtime = "nodejs16"

## available\_memory\_mb = 128 source\_archive\_bucket = google\_storage\_bucket.bucket.name source\_archive\_object = google\_storage\_bucket\_object.archive.name trigger\_http = true https\_trigger\_security\_level = "SECURE\_ALWAYS" timeout = 60 entry\_point = "helloGET" labels = { my-label = "my-label-value" } }


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.