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

- Source: https://support.icompaas.com/support/solutions/articles/62000229889-ensure-server-parameter-connection-throttling-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 PostgreSQL parameter connection\_throttling enables throttling of excessive connection attempts and logs repeated failed connections coming from the same source. When enabled, PostgreSQL can detect “connection storms” or brute-force authentication patterns and throttle them to protect server stability. In Azure PostgreSQL (Single and Flexible Servers), this parameter is important for preventing misuse, monitoring abnormal behavior, and maintaining availability under load or malicious activity.

  

Rationale:

-   Helps detect and limit brute-force attacks or credential-stuffing attempts.
    
-   Prevents connection floods that may be caused by compromised applications or malicious users.
    
-   Adds visibility into repeated failed connection attempts.
    

  

Impact:

-   Enhanced protection against connection-based DoS attacks.
    
-   Reduced the risk of saturation of backend processes under heavy connection storms.
    
-   Improved audit visibility into repeated connection failures.
    
-   Stabilizes the database under malformed application behavior.
    

  

Default Value:

-   For Azure Database for PostgreSQL Flexible Server, the default for connection\_throttling is typically OFF.
    

  

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 Flexible Server
    
3.  Select the target PostgreSQL server
    
4.  From the left menu, under settings, select Server parameters
    
5.  Search for the parameter connection\_throttle.enable
    
6.  Verify the parameter value is set to ON
    
7.  If connection\_throttle.enable is not set to ON, follow the implementation steps
    

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

  

Implementation Plan:

1.  Log in to the Azure Portal.
    
2.  Search for your Azure Database for PostgreSQL server (Single or Flexible).
    
3.  On the left-hand menu, under the Settings section, select server parameters.
    

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

4.  Search for connection\_throttling. Change the value to ON.
    

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

5.  Save the changes.
    

  

Backout Plan:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for and open the PostgreSQL Flexible Server
    
3.  From the left menu, select Server parameters
    
4.  Search for the parameter connection\_throttle.enable
    
5.  Set the value to OFF
    
6.  Click Save to apply the change
    

  

Reference:

-   [https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/param-connections-authentication-connection-settings?pivots=postgresql-17](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/param-connections-authentication-connection-settings?pivots=postgresql-17)

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