> 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-30.md).

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

## Rule Details

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

## Impact

This rule is examining whether logging is enabled for Dialogflow CX agents. Dialogflow CX is a sophisticated conversational AI tool that can be used to build and manage virtual agents. If logging isn't enabled, it would be challenging to track interactions, troubleshoot issues, or monitor the performance and usage of these virtual agents. This could potentially lead to a loss of critical data, failure to adhere to certain compliance requirements, and a lack of visibility over the system. Hence, it's regarded as a poor practice not to have logging enabled for Dialogflow CX agents.

## How to Fix

*Resource:* google\_dialogflow\_cx\_agent

* *Arguments:* enable\_stackdriver\_logging

## To fix the issue, introduce the `enable_stackdriver_logging` field in your `google_dialogflow_cx_agent` \[source,go]

resource and set it to `true`:

## The above code is secure because it enables Stackdriver logging for the Google Dialogflow CX agent, ensuring all interactions and events are logged and monitored, which is essential for troubleshooting, auditing and security purposes. This aligns with the security best practices, compliance requirements and can help identify potential security concerns or performance issues at an early stage. resource "google\_dialogflow\_cx\_agent" "agent" { ... 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-30.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.