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_retention_days' is greater than 3 days for PostgreSQL Database Server

Framework Reference: A.8.15 (Logging) Integration: Azure – PostgreSQL Server

Why this matters

Log files are a critical source of visibility into the behavior and health of your PostgreSQL server. Retaining these logs for at least 4 days ensures you can identify misconfigurations, troubleshoot incidents, and investigate suspicious activity effectively.

The default setting of 3 days may not be sufficient for forensic analysis or long-term monitoring—especially in high-traffic environments. Raising this threshold helps improve your security posture and audit readiness.

What this check does

This Auto Check verifies that:

  • The PostgreSQL server parameter log_retention_days is set to at least 4 days (i.e., greater than 3).
  • It applies to both single server and flexible server deployments in Azure.
  • The check passes if the configured value is between 4 and 7 days, inclusive.

How to fix it

You can update the log_retention_days parameter using the Azure Portal, CLI, or PowerShell.

Azure Portal:

  1. Go to Azure Database for PostgreSQL servers.
  2. Select your server and navigate to Server parameters.
  3. Search for log_retention_days.
  4. Set the value to a number between 4 and 7.
  5. Save the configuration.

Azure CLI:

az postgres server configuration set \  --resource-group <resourceGroupName> \  --server-name <serverName> \  --name log_retention_days \  --value 4

PowerShell:

Update-AzPostgreSqlConfiguration `  -ResourceGroupName "<ResourceGroupName>" `  -ServerName "<ServerName>" `  -Name "log_retention_days" `  -Value 4

Replace the placeholder values with those relevant to your environment.

Exceptions

If log data is exported to an external SIEM or retained elsewhere for longer periods, this check may be marked as Not Applicable. In such cases, appropriate documentation must be maintained.

Further resources

Configure server parameters in Azure PostgreSQL

Azure REST API: List PostgreSQL configurations

Azure Security Benchmark: Logging and Threat Detection

PowerShell: Get PostgreSQL Configuration

PowerShell: Update PostgreSQL Configuration

Was this article helpful?

Powered by Product Fruits