# Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server

- Source: https://support.icompaas.com/support/solutions/articles/62000229886-ensure-server-parameter-log-connections-is-set-to-on-for-postgresql-database-server
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Azure Compliance / Control / Check](https://support.icompaas.com/support/solutions/folders/62000168797)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

The log\_connections server parameter in PostgreSQL controls whether the database logs successful client connection attempts. Enabling this parameter allows database administrators to monitor who is connecting to the server, from which IP addresses, and when. This is critical for auditing, security monitoring, and identifying unauthorized access attempts in Azure PostgreSQL Database Servers (Single or Flexible).

  

Rationale:

-   Security Monitoring: Logging connections provides visibility into client access patterns and helps detect unusual or suspicious activity.
    
-   Audit & Compliance: Supports regulatory requirements and internal policies for database access auditing (e.g., GDPR, HIPAA, PCI-DSS).
    
-   Troubleshooting: Helps diagnose connectivity issues by providing a record of all successful connections.
    

  

Impact:

-   Provides an audit trail of all connections to the PostgreSQL server.
    
-   Supports compliance and security reporting.
    
-   Enhances visibility into database access and operational activity.
    
-   Logging each connection increases log volume, which could impact storage usage if not managed.
    
-   Minimal performance overhead is associated with logging; usually negligible for most workloads.
    

  

Default Value:

For Azure Database for PostgreSQL (Single and Flexible Servers), the default value for log\_connections is ON.

  

Pre-requisites:

-   Global Administrator or Security Administrator permissions.
    
-   Must be Azure Database for PostgreSQL – Flexible Server (or Single Server if the parameter is supported).
    

  

Test Plan:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for and open the Azure Database for PostgreSQL
    
3.  Select the target PostgreSQL server
    
4.  From the left menu, select Server parameters
    
5.  Search for the parameter log\_connections
    
6.  Verify log\_connections is set to ON
    
7.  If log\_connections is not set to ON, follow the implementation steps
    

![](https://support.icompaas.com/assets/kb/cc1b8bdf8c5fe829.png)

Implementation Steps:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for your Azure Database for PostgreSQL server.
    
3.  On the left-hand menu, under the Settings section, select server parameters.
    

  

                                       ![](https://support.icompaas.com/assets/kb/29d4351d2e924eb1.png)

4.  Search for log\_connections. 
    
5.  Set the log\_connections value to ON
    

![](https://support.icompaas.com/assets/kb/01c3b614d52e1b15.png)

  

6.  Save the changes
    

  

Backout Plan:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for your Azure Database for PostgreSQL server.
    
3.  On the left-hand menu, under the Settings section, select server parameters.
    
4.  Search for log\_connections.
    
5.  Set the log\_connections value to OFF.
    
6.  Save the changes
    

  

Reference:

-   [https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-logging](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-logging)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.