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

# Logging for Dialogflow CX webhooks is disabled misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_31              |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | GCP                           |
| Severity               | MEDIUM                        |
| Framework              | Terraform, Terraform Plan     |

## Impact

This rule is checking to see if logging is enabled for Dialogflow CX webhooks. Dialogflow CX is a conversational AI platform that can be used to create virtual agents, IVR systems, and chatbots. Webhooks provide a way to deliver data to other applications, therefore logging for these webhooks is essential.

Not having logging enabled for Dialogflow CX webhooks could lead to several problems. For instance, without logging, it becomes extremely difficult to debug issues or understand the performance and usage patterns of your webhooks. Additionally, this may expose the system to security threats as potential malicious activities or breaches cannot be traced or understood. Therefore, enabling logging is an important best practice for monitoring and maintaining the security, performance and reliability of the system.

## How to Fix

*Resource:* google\_dialogflow\_cx\_webhook

* *Arguments:* enable\_stackdriver\_logging

To fix the issue, you should enable logging for Dialogflow CX webhooks in the Google Cloud Platform.

## In the above secure Terraform code, `enable_stackdriver_logging` is set to `true`. This ensures that logging is enabled for Dialogflow CX webhooks, which helps in monitoring and debugging. Compliance with this policy will decrease the chance of data loss, unauthorized access, or downtime. \[source,go]

## resource "google\_dialogflow\_cx\_webhook" "default" { ... enable\_stackdriver\_logging = true }


---

# 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/logging/appsec2-gcp-31.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.