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

# GCP PostgreSQL instance database flag log\_parser\_stats is not set to off misconfiguration detected i

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_15                     |
| Category - Subcategory | Logging - Disabled or missing        |
| Provider               | GCP                                  |
| Severity               | LOW                                  |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | 5072e3b8-0767-433b-9b06-d2003ba13650 |

## Impact

This rule is checking to verify if the 'log\_parser\_stats' flag in the PostgreSQL database is set to 'off'. This flag, when turned on, logs statistical information about query parsing and rewriting. While this might be useful for debugging, it can generate a vast amount of log data significantly consuming disk space, and may potentially lead to performance degradation. Therefore, for optimal performance and saving resources, it is generally recommended to set the 'log\_parser\_stats' flag to 'off' in a production environment.

## How to Fix

*Resource:* google\_sql\_database\_instance

* *Arguments:* settings.database\_flags

To fix the issue, you should ensure that the 'log\_parser\_stats' flag for your PostgreSQL database is set to 'off'. Here is an example of how to do it in your Terraform file:

## The above code is secure because the 'log\_parser\_stats' flag is explicitly set to 'off'. The 'log\_parser\_stats' flag in PostgreSQL enables detailed statistics for the parser stage of query execution, including the number of created and used tokens and the number of created and used parse nodes. Logging these statistics can have a significant performance impact. So, having this flag off helps in reducing the overhead of unnecessary logging, decreasing the chance of slowed performance of your PostgreSQL database. \[source,go]

resource "google\_sql\_database\_instance" "default" { name = "database" region = "us-central1"

database\_version = "POSTGRES\_11"

## settings { database\_flags { name = "log\_parser\_stats" value = "off" } } }


---

# 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-15.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.