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

From Azure Console

1. Go to Azure Database for PostgreSQL servers
2. For each database, under Settings, select Server parameters
3. Search for log_checkpoints and set its value to ON
4. Click Save

Using Azure Command Line Interface

Use the below command to update the configuration for log_checkpoints.

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

Using PowerShell

Update-AzPostgreSqlConfiguration -ResourceGroupName <resourceGroupName> -ServerName <serverName> -Name log_checkpoints -Value on

Default value

By default, log_checkpoints is set to ON.

References

1. https://learn.microsoft.com/en-us/rest/api/postgresql/configurations/listbyserver
2. https://learn.microsoft.com/en-us/azure/postgresql/howto-configure-server-parameters-using-portal
3. https://learn.microsoft.com/en-us/azure/security/benchmarks/security-controls-v2-logging-threat-detection#lt-4-enable-logging-for-azure-resources

Service-wide remediation

Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.

Azure

Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.

Operational rollout

1. Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
2. Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
3. Re-scan and track approved exceptions with an owner and expiry date.