[LEGACY] Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL single server

Overview

Enable log_connections on PostgreSQL Database Servers.

Rationale

Enabling log_connections helps the PostgreSQL Database log attempted connections to the server and successful client authentications. Log data can be used to identify, troubleshoot, and repair configuration errors and sub-optimal performance.

Default value

By default, log_connections is set to on (enabled).

Remediation guidance

Remediate from Azure Portal

Open the server using the Open in Azure button
Under Settings, click Server parameters.
In the filter bar, type log_connections.
Set log_connections to ON.
Click Save.

Remediate from Azure CLI

Use the below command to update log_connections configuration.

az postgres server configuration set --resource-group <resourceGroupName> --server-name <serverName> --name log_connections --value on

Remediate from PowerShell

Use the below command to update log_connections configuration.

Update-AzPostgreSqlConfiguration -ResourceGroupName  -ServerName  -Name log_connections -Value on

Multiple Remediation Paths

Azure

SERVICE-WIDE (RECOMMENDED when many resources are affected): Assign Azure Policy initiatives at management group/subscription scope and trigger remediation tasks.

az policy assignment create --name <assignment-name> --scope /subscriptions/<subscription-id> --policy-set-definition <initiative-id>
az policy remediation create --name <remediation-name> --policy-assignment <assignment-id>

ASSET-LEVEL: Apply the resource-specific remediation steps above to the listed non-compliant resources.

PREVENTIVE: Embed Azure Policy checks into landing zones and IaC workflows to block or auto-remediate drift.

References for Service-Wide Patterns

Azure Policy overview: https://learn.microsoft.com/en-us/azure/governance/policy/overview
Azure Policy remediation: https://learn.microsoft.com/en-us/azure/governance/policy/how-to/remediate-resources
Azure Policy initiative structure: https://learn.microsoft.com/en-us/azure/governance/policy/concepts/initiative-definition-structure

Operational Rollout Workflow

Use this sequence to reduce risk and avoid repeated drift.

1. Contain at Service-Wide Scope First (Recommended)

Azure: assign policy initiatives at management group/subscription scope and run remediation tasks.

az policy assignment create --name <assignment-name> --scope /subscriptions/<subscription-id> --policy-set-definition <initiative-id>
az policy remediation create --name <remediation-name> --policy-assignment <assignment-id>

2. Remediate Existing Affected Assets

Execute the control-specific Console/CLI steps documented above for each flagged resource.
Prioritize internet-exposed and production assets first.

3. Validate and Prevent Recurrence

Re-scan after each remediation batch.
Track exceptions with owner and expiry date.
Add preventive checks in IaC/CI pipelines.

Query logic

These are the stored checks tied to this control.

Server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server

Connectors

Microsoft Azure

Covered asset types

PostgreSQLServer

Expected check: eq []

{
  postgreSqlServers(
    where: {
      configurations_SOME: { name: "log_connections", value_MATCHES: "(?i)off" }
    }
  ) {
    ...AssetFragment
  }
}