📝 Azure PostgreSQL Flexible Server log_retention_days Parameter is less than 4 days 🟢

• Contextual name: 📝 Flexible Server log_retention_days Parameter is less than 4 days 🟢
• ID: /ce/ca/azure/postgresql-database/flexible-server-log-retention-days-parameter-over-4-days
• Located in: 📁 Azure PostgreSQL Database

Flags

• 🟢 Policy with categories
• 🟢 Policy with type
• 🟢 Production policy

Our Metadata

• Policy Type: COMPLIANCE_POLICY
• Policy Category:
  • RELIABILITY
  • PERFORMANCE

Similar Policies

• Cloud Conformity
  • Check for PostgreSQL Log Retention Period
• Internal
  • dec-x-0c82d775

Similar Internal Rules

Rule	Policies	Flags
✉️ dec-x-0c82d775	1

Logic

• 🧠 prod.logic.yaml 🟢
  • 📕 Azure PostgreSQL Server
  • 🔌 Azure PostgreSQL Server - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Ensure logfiles.retention_days on PostgreSQL flexible servers is set to an appropriate value.

Rationale

Configuring logfiles.retention_days determines the duration in days that Azure Database for PostgreSQL retains log files. Query and error logs can be used to identify, troubleshoot, and repair configuration errors and sub-optimal performance.

Impact

Configuring this setting will result in logs being retained for the specified number of days. If this is configured on a high traffic server, the log may grow quickly to occupy a large amount of disk space. In this case you may want to set this to a lower number.

Audit

From Azure Portal

1. From Azure Home select the Portal Menu.
2. Go to Azure Database for PostgreSQL flexible servers.
3. For each database, under Settings, click Server parameters.
4. In the filter bar, type logfiles.retention_days.
5. Ensure that the VALUE is between 4 and 7 (inclusive).

From Azure CLI

Ensure logfiles.retention_days value is greater than 3:

... [see more](description.md)

Remediation

Open File

Remediation

From Azure Portal

1. From Azure Home select the Portal Menu.
2. Go to Azure Database for PostgreSQL flexible servers.
3. For each database, under Settings, click Server parameters.
4. In the filter bar, type logfiles.retention_days.
5. Input a value between 4 and 7 (inclusive).
6. Click Save.

From Azure CLI

Use the below command to update logfiles.retention_days configuration:

az postgres flexible-server parameter set --resource-group <resourceGroup> --server-name <serverName> --name logfiles.retention_days --value <4-7>

From Powershell

Use the below command to update logfiles.retention_days configuration:

Update-AzPostgreSqlFlexibleServerConfiguration -ResourceGroupName <resourceGroup> -ServerName <serverName> -Name logfiles.retention_days -Value <4-7>

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS Azure v1.3.0 → 💼 4.3.7 Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server - Level 1 (Automated)		1	1
💼 CIS Azure v1.4.0 → 💼 4.3.6 Ensure server parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server - Level 1 (Automated)		1	1
💼 CIS Azure v1.5.0 → 💼 4.3.6 Ensure Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server - Level 1 (Automated)		1	1
💼 CIS Azure v2.0.0 → 💼 4.3.6 Ensure Server Parameter 'logretentiondays' is greater than 3 days for PostgreSQL Database Server - Level 1 (Automated)		1	1
💼 CIS Azure v2.1.0 → 💼 4.3.6 Ensure Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database Server - Level 1 (Automated)		1	1
💼 CIS Azure v3.0.0 → 💼 5.2.4 Ensure server parameter 'logfiles.retention_days' is greater than 3 days for PostgreSQL flexible server (Automated)			1
💼 Cloudaware Framework → 💼 Logging and Monitoring Configuration			50
💼 FedRAMP High Security Controls → 💼 AC-6(9) Log Use of Privileged Functions (M)(H)		7	24
💼 FedRAMP High Security Controls → 💼 AU-6 Audit Record Review, Analysis, and Reporting (L)(M)(H)	6	21	28
💼 FedRAMP High Security Controls → 💼 AU-11 Audit Record Retention (L)(M)(H)		17	19
💼 FedRAMP High Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)	2		63
💼 FedRAMP High Security Controls → 💼 CM-3 Configuration Change Control (M)(H)	4		22
💼 FedRAMP High Security Controls → 💼 SI-4(20) Privileged Users (H)		47	49
💼 FedRAMP Low Security Controls → 💼 AU-6 Audit Record Review, Analysis, and Reporting (L)(M)(H)			25
💼 FedRAMP Low Security Controls → 💼 AU-11 Audit Record Retention (L)(M)(H)			19
💼 FedRAMP Low Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)			63
💼 FedRAMP Moderate Security Controls → 💼 AC-6(9) Log Use of Privileged Functions (M)(H)			24
💼 FedRAMP Moderate Security Controls → 💼 AU-6 Audit Record Review, Analysis, and Reporting (L)(M)(H)	2		28
💼 FedRAMP Moderate Security Controls → 💼 AU-11 Audit Record Retention (L)(M)(H)			19
💼 FedRAMP Moderate Security Controls → 💼 AU-12 Audit Record Generation (L)(M)(H)			63
💼 FedRAMP Moderate Security Controls → 💼 CM-3 Configuration Change Control (M)(H)	2		18
💼 ISO/IEC 27001:2013 → 💼 A.12.4.1 Event logging		16	19
💼 ISO/IEC 27001:2013 → 💼 A.14.1.1 Information security requirements analysis and specification		6	6
💼 ISO/IEC 27001:2022 → 💼 8.6 Capacity management		3	3
💼 NIST CSF v1.1 → 💼 DE.AE-2: Detected events are analyzed to understand attack targets and methods		19	24
💼 NIST CSF v1.1 → 💼 DE.AE-3: Event data are collected and correlated from multiple sources and sensors		19	38
💼 NIST CSF v1.1 → 💼 DE.CM-1: The network is monitored to detect potential cybersecurity events		19	42
💼 NIST CSF v1.1 → 💼 DE.CM-3: Personnel activity is monitored to detect potential cybersecurity events		21	27
💼 NIST CSF v1.1 → 💼 DE.CM-7: Monitoring for unauthorized personnel, connections, devices, and software is performed		19	24
💼 NIST CSF v1.1 → 💼 DE.DP-4: Event detection information is communicated		30	33
💼 NIST CSF v1.1 → 💼 ID.SC-4: Suppliers and third-party partners are routinely assessed using audits, test results, or other forms of evaluations to confirm they are meeting their contractual obligations		16	19
💼 NIST CSF v1.1 → 💼 PR.IP-2: A System Development Life Cycle to manage systems is implemented		6	9
💼 NIST CSF v1.1 → 💼 PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy		17	32
💼 NIST CSF v1.1 → 💼 RS.AN-1: Notifications from detection systems are investigated		19	24
💼 NIST CSF v1.1 → 💼 RS.CO-2: Incidents are reported consistent with established criteria		20	23
💼 NIST CSF v2.0 → 💼 DE.AE-02: Potentially adverse events are analyzed to better understand associated activities			29
💼 NIST CSF v2.0 → 💼 DE.AE-03: Information is correlated from multiple sources			44
💼 NIST CSF v2.0 → 💼 DE.AE-06: Information on adverse events is provided to authorized staff and tools			33
💼 NIST CSF v2.0 → 💼 DE.AE-07: Cyber threat intelligence and other contextual information are integrated into the analysis			38
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events			110
💼 NIST CSF v2.0 → 💼 DE.CM-03: Personnel activity and technology usage are monitored to find potentially adverse events			79
💼 NIST CSF v2.0 → 💼 DE.CM-06: External service provider activities and services are monitored to find potentially adverse events			29
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events			123
💼 NIST CSF v2.0 → 💼 GV.SC-07: The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship			26
💼 NIST CSF v2.0 → 💼 ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked			25
💼 NIST CSF v2.0 → 💼 ID.RA-10: Critical suppliers are assessed prior to acquisition			26
💼 NIST CSF v2.0 → 💼 RC.CO-04: Public updates on incident recovery are shared using approved methods and messaging			23
💼 NIST CSF v2.0 → 💼 RS.CO-02: Internal and external stakeholders are notified of incidents			31
💼 NIST CSF v2.0 → 💼 RS.MA-02: Incident reports are triaged and validated			25
💼 NIST SP 800-53 Revision 5 → 💼 AC-6(9) Least Privilege _ Log Use of Privileged Functions		16	17
💼 NIST SP 800-53 Revision 5 → 💼 AU-12 Audit Record Generation	4	46	63
💼 NIST SP 800-53 Revision 5 → 💼 CM-3 Configuration Change Control	8	16	22
💼 SOC 2 → 💼 CC5.2-3 Establishes Relevant Security Management Process Controls Activities		16	36
💼 SOC 2 → 💼 CC7.1-2 Monitors Infrastructure and Software		9	12