> 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/appsec-gcp-53.md).

# GCP PostgreSQL instance database flag log\_disconnections is disabled misconfiguration detected in co

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_53                      |
| Category - Subcategory | Logging - Disabled or missing        |
| Provider               | GCP                                  |
| Severity               | LOW                                  |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | 05244425-d5d0-4055-a461-198000dd1b25 |

## Impact

Enabling the *log\_disconnections* database flag logs the end of each session, including the session duration. PostgreSQL does not log session details by default, including duration and session end details. Enabling the *log\_disconnections* database flag creates log entries at the end of each session, useful when troubleshooting issues and determining unusual activity across a time period. The *log\_disconnections* and *log\_connections* work hand in hand and usually the pair would be enabled/disabled together. We recommended you set the *log\_disconnections* flag for a PostgreSQL instance to *On*.

## How to Fix

*Resource:* google\_sql\_database\_instance

* *Arguments:* database\_version = "POSTGRES\_\* " settings::database\_flags: key:"log\_disconnections", value: by default set to "off" \[source,go]

***

resource "google\_sql\_database\_instance" "default" { name = "master-instance" database\_version = "POSTGRES\_11" region = "us-central1"

settings {

* database\_flags {
* name = "log\_disconnections"
* value = "on" } } }

***


---

# 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/appsec-gcp-53.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.