Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossarySupport and Bug Reporting
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidance
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: GCPAuto Checks: AzureEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
Verify that Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database ServerVerify that server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_connections' is set to 'ON' for PostgreSQL Database ServerVerify that 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database ServerVerify that Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database ServerVerify that Activity Log Alert exists for Create Policy AssignmentVerify that Activity Log Alert exists for Create or Update Public IP Address ruleVerify that Activity Log Alert exists for Delete SQL Server Firewall RuleVerify that Activity Log Alert exists for Create or Update SQL Server Firewall RuleVerify that Activity Log Alert exists for Delete Network Security GroupVerify that the storage account containing the container with activity logs is encrypted with Customer Managed KeyVerify that Activity Log Alert exists for Delete Policy AssignmentVerify that Activity Log Alert exists for Create or Update Network Security GroupVerify that Diagnostic Setting captures appropriate categoriesVerify that Activity Log Alert exists for Create or Update Security SolutionVerify that Activity Log Alert exists for Delete Public IP Address ruleVerify that logging for Azure AppService 'HTTP logs' is enabledVerify that logging for Azure Key Vault is 'Enabled'Verify that the Expiration Date is set for all Keys in RBAC Key VaultsEnable Role Based Access Control for Azure Key VaultVerify that Private Endpoints are Used for Azure Key VaultVerify that the Key Vault is RecoverableVerify that HTTP(S) access from the Internet is evaluated and restricted

Verify that server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server

Framework Reference: A.8.20 Integration: Azure – PostgreSQL Server

Why this matters

The log_connections parameter controls whether PostgreSQL logs each incoming connection attempt, including successful authentications. Enabling this setting ensures that both legitimate access and potential unauthorized attempts are recorded in your query and error logs.

Without connection logging enabled, it becomes significantly harder to identify brute-force login attempts, misconfigurations, or usage anomalies that may impact system security and performance. This setting is a foundational part of any audit-ready logging configuration.

What this check does

This Auto Check verifies whether the PostgreSQL server parameter log_connections is enabled.

Check Logic:
Passes if:

log_connections is explicitly set to on.

Fails if:

log_connections is unset, null, or set to off.

Applies to:

  • Azure PostgreSQL Single Server
  • Azure PostgreSQL Flexible Server
  • The check inspects the parameter via Azure’s configuration API and expects an exact value of on.

How to fix it

You can enable the log_connections parameter using the Azure Portal, CLI, or PowerShell.

Azure Portal:

  1. Navigate to Azure Database for PostgreSQL servers.
  2. Select the server instance and go to Server parameters.
  3. Locate the log_connections parameter.
  4. Set it to ON.
  5. Save the changes.

Azure CLI:

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

PowerShell:

Update-AzPostgreSqlConfiguration `  -ResourceGroupName "<ResourceGroupName>" `  -ServerName "<ServerName>" `  -Name "log_connections" `  -Value "on"

Substitute the placeholder values with those specific to your Azure deployment.

Exceptions

There are no recommended exceptions for this setting. Even in high-traffic environments, connection logging should remain enabled. If disabled, justification must be documented and approved by security stakeholders, along with compensating controls for connection-level visibility.

Further resources

Was this article helpful?

Powered by Product Fruits