Azure Policy Regulatory Compliance controls for Azure Database for PostgreSQL

APPLIES TO: Azure Database for PostgreSQL - Single Server

Important

Azure Database for PostgreSQL - Single Server is on the retirement path. We strongly recommend that you upgrade to Azure Database for PostgreSQL - Flexible Server. For more information about migrating to Azure Database for PostgreSQL - Flexible Server, see What's happening to Azure Database for PostgreSQL Single Server?.

Regulatory Compliance in Azure Policy provides Microsoft created and managed initiative definitions, known as built-ins, for the compliance domains and security controls related to different compliance standards. This page lists the compliance domains and security controls for Azure Database for PostgreSQL. You can assign the built-ins for a security control individually to help make your Azure resources compliant with the specific standard.

The title of each built-in policy definition links to the policy definition in the Azure portal. Use the link in the Policy Version column to view the source on the Azure Policy GitHub repo.

Important

Each control is associated with one or more Azure Policy definitions. These policies might help you assess compliance with the control. However, there often isn't a one-to-one or complete match between a control and one or more policies. As such, Compliant in Azure Policy refers only to the policies themselves. This doesn't ensure that you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between controls and Azure Policy Regulatory Compliance definitions for these compliance standards can change over time.

CIS Microsoft Azure Foundations Benchmark 1.1.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.1.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
4 Database Services 4.12 Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server Log checkpoints should be enabled for PostgreSQL database servers 1.0.0
4 Database Services 4.13 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
4 Database Services 4.14 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server Log connections should be enabled for PostgreSQL database servers 1.0.0
4 Database Services 4.15 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server Disconnections should be logged for PostgreSQL database servers. 1.0.0
4 Database Services 4.17 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server Connection throttling should be enabled for PostgreSQL database servers 1.0.0

CIS Microsoft Azure Foundations Benchmark 1.3.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CIS Microsoft Azure Foundations Benchmark 1.3.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
4 Database Services 4.3.1 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
4 Database Services 4.3.3 Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server Log checkpoints should be enabled for PostgreSQL database servers 1.0.0
4 Database Services 4.3.4 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server Log connections should be enabled for PostgreSQL database servers 1.0.0
4 Database Services 4.3.5 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server Disconnections should be logged for PostgreSQL database servers. 1.0.0
4 Database Services 4.3.6 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server Connection throttling should be enabled for PostgreSQL database servers 1.0.0

CIS Microsoft Azure Foundations Benchmark 1.4.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for CIS v1.4.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
4 Database Services 4.3.1 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
4 Database Services 4.3.2 Ensure Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server Log checkpoints should be enabled for PostgreSQL database servers 1.0.0
4 Database Services 4.3.3 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server Log connections should be enabled for PostgreSQL database servers 1.0.0
4 Database Services 4.3.4 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server Disconnections should be logged for PostgreSQL database servers. 1.0.0
4 Database Services 4.3.5 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server Connection throttling should be enabled for PostgreSQL database servers 1.0.0

CIS Microsoft Azure Foundations Benchmark 2.0.0

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for CIS v2.0.0. For more information about this compliance standard, see CIS Microsoft Azure Foundations Benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
4.3 4.3.1 Ensure 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database Server Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
4.3 4.3.2 Ensure Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server Log checkpoints should be enabled for PostgreSQL database servers 1.0.0
4.3 4.3.3 Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server Log connections should be enabled for PostgreSQL database servers 1.0.0
4.3 4.3.4 Ensure server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database Server Disconnections should be logged for PostgreSQL database servers. 1.0.0
4.3 4.3.5 Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server Connection throttling should be enabled for PostgreSQL database servers 1.0.0
4.3 4.3.7 Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled Public network access should be disabled for PostgreSQL flexible servers 3.0.1
4.3 4.3.7 Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled Public network access should be disabled for PostgreSQL servers 2.0.1
4.3 4.3.8 Ensure 'Infrastructure double encryption' for PostgreSQL Database Server is 'Enabled' Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0

CMMC Level 3

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - CMMC Level 3. For more information about this compliance standard, see Cybersecurity Maturity Model Certification (CMMC).

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC.1.001 Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). Public network access should be disabled for PostgreSQL flexible servers 3.0.1
Access Control AC.1.001 Limit information system access to authorized users, processes acting on behalf of authorized users, and devices (including other information systems). Public network access should be disabled for PostgreSQL servers 2.0.1
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. Public network access should be disabled for PostgreSQL flexible servers 3.0.1
Access Control AC.1.002 Limit information system access to the types of transactions and functions that authorized users are permitted to execute. Public network access should be disabled for PostgreSQL servers 2.0.1
Access Control AC.2.016 Control the flow of CUI in accordance with approved authorizations. Public network access should be disabled for PostgreSQL flexible servers 3.0.1
Access Control AC.2.016 Control the flow of CUI in accordance with approved authorizations. Public network access should be disabled for PostgreSQL servers 2.0.1
Configuration Management CM.3.068 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. Public network access should be disabled for PostgreSQL flexible servers 3.0.1
Configuration Management CM.3.068 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services. Public network access should be disabled for PostgreSQL servers 2.0.1
Recovery RE.2.137 Regularly perform and test data back-ups. Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Recovery RE.3.139 Regularly perform complete, comprehensive and resilient data backups as organizationally-defined. Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Public network access should be disabled for PostgreSQL flexible servers 3.0.1
System and Communications Protection SC.1.175 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection SC.3.177 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI. Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Public network access should be disabled for PostgreSQL flexible servers 3.0.1
System and Communications Protection SC.3.183 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection SC.3.185 Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System and Communications Protection SC.3.190 Protect the authenticity of communications sessions. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System and Communications Protection SC.3.191 Protect the confidentiality of CUI at rest. Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0

FedRAMP High

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP High. For more information about this compliance standard, see FedRAMP High.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-4 Information Flow Enforcement Public network access should be disabled for PostgreSQL servers 2.0.1
Access Control AC-17 Remote Access Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-17 (1) Automated Monitoring / Control Private endpoint should be enabled for PostgreSQL servers 1.0.2
Contingency Planning CP-6 Alternate Storage Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-6 (1) Separation From Primary Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-9 Information System Backup Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
System And Communications Protection SC-7 Boundary Protection Private endpoint should be enabled for PostgreSQL servers 1.0.2
System And Communications Protection SC-7 Boundary Protection Public network access should be disabled for PostgreSQL servers 2.0.1
System And Communications Protection SC-7 (3) Access Points Private endpoint should be enabled for PostgreSQL servers 1.0.2
System And Communications Protection SC-7 (3) Access Points Public network access should be disabled for PostgreSQL servers 2.0.1
System And Communications Protection SC-8 Transmission Confidentiality And Integrity Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System And Communications Protection SC-8 (1) Cryptographic Or Alternate Physical Protection Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System And Communications Protection SC-12 Cryptographic Key Establishment And Management PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
System And Communications Protection SC-28 Protection Of Information At Rest Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
System And Communications Protection SC-28 (1) Cryptographic Protection Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0

FedRAMP Moderate

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - FedRAMP Moderate. For more information about this compliance standard, see FedRAMP Moderate.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-4 Information Flow Enforcement Public network access should be disabled for PostgreSQL servers 2.0.1
Access Control AC-17 Remote Access Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-17 (1) Automated Monitoring / Control Private endpoint should be enabled for PostgreSQL servers 1.0.2
Contingency Planning CP-6 Alternate Storage Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-6 (1) Separation From Primary Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-9 Information System Backup Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
System And Communications Protection SC-7 Boundary Protection Private endpoint should be enabled for PostgreSQL servers 1.0.2
System And Communications Protection SC-7 Boundary Protection Public network access should be disabled for PostgreSQL servers 2.0.1
System And Communications Protection SC-7 (3) Access Points Private endpoint should be enabled for PostgreSQL servers 1.0.2
System And Communications Protection SC-7 (3) Access Points Public network access should be disabled for PostgreSQL servers 2.0.1
System And Communications Protection SC-8 Transmission Confidentiality And Integrity Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System And Communications Protection SC-8 (1) Cryptographic Or Alternate Physical Protection Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System And Communications Protection SC-12 Cryptographic Key Establishment And Management PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
System And Communications Protection SC-28 Protection Of Information At Rest Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
System And Communications Protection SC-28 (1) Cryptographic Protection Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0

HIPAA HITRUST 9.2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - HIPAA HITRUST 9.2. For more information about this compliance standard, see HIPAA HITRUST 9.2.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
08 Network Protection 0809.01n2Organizational.1234-01.n 0809.01n2Organizational.1234-01.n 01.04 Network Access Control Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
08 Network Protection 0810.01n2Organizational.5-01.n 0810.01n2Organizational.5-01.n 01.04 Network Access Control Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
08 Network Protection 0811.01n2Organizational.6-01.n 0811.01n2Organizational.6-01.n 01.04 Network Access Control Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
08 Network Protection 0812.01n2Organizational.8-01.n 0812.01n2Organizational.8-01.n 01.04 Network Access Control Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
08 Network Protection 0814.01n1Organizational.12-01.n 0814.01n1Organizational.12-01.n 01.04 Network Access Control Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
09 Transmission Protection 0947.09y2Organizational.2-09.y 0947.09y2Organizational.2-09.y 09.09 Electronic Commerce Services Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
14 Third Party Assurance 1450.05i2Organizational.2-05.i 1450.05i2Organizational.2-05.i 05.02 External Parties Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
16 Business Continuity & Disaster Recovery 1618.09l1Organizational.45-09.l 1618.09l1Organizational.45-09.l 09.05 Information Back-Up Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
16 Business Continuity & Disaster Recovery 1623.09l2Organizational.4-09.l 1623.09l2Organizational.4-09.l 09.05 Information Back-Up Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
16 Business Continuity & Disaster Recovery 1626.09l3Organizational.5-09.l 1626.09l3Organizational.5-09.l 09.05 Information Back-Up Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1

Microsoft Cloud for Sovereignty Baseline Confidential Policies

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for MCfS Sovereignty Baseline Confidential Policies. For more information about this compliance standard, see Microsoft Cloud for Sovereignty Policy portfolio.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
SO.3 - Customer-Managed Keys SO.3 Azure products must be configured to use Customer-Managed Keys when possible. PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4

Microsoft cloud security benchmark

The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Microsoft cloud security benchmark, see the Azure Security Benchmark mapping files.

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Microsoft cloud security benchmark.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Network Security NS-2 Secure cloud services with network controls Private endpoint should be enabled for PostgreSQL servers 1.0.2
Network Security NS-2 Secure cloud services with network controls Public network access should be disabled for PostgreSQL servers 2.0.1
Identity Management IM-1 Use centralized identity and authentication system A Microsoft Entra administrator should be provisioned for PostgreSQL servers 1.0.1
Data Protection DP-3 Encrypt sensitive data in transit Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Data Protection DP-5 Use customer-managed key option in data at rest encryption when required PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
Logging and Threat Detection LT-1 Enable threat detection capabilities Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers 1.0.0
Logging and Threat Detection LT-2 Enable threat detection for identity and access management Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers 1.0.0
Incident Response IR-3 Detection and analysis - create incidents based on high-quality alerts Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers 1.0.0
Backup and Recovery BR-1 Ensure regular automated backups Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Backup and Recovery BR-2 Protect backup and recovery data Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Incident Response AIR-5 Detection and analysis - prioritize incidents Azure Defender for SQL should be enabled for unprotected PostgreSQL flexible servers 1.0.0

NIST SP 800-171 R2

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-171 R2. For more information about this compliance standard, see NIST SP 800-171 R2.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control 3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems). Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control 3.1.12 Monitor and control remote access sessions. Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control 3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions. Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control 3.1.14 Route remote access via managed access control points. Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control 3.1.3 Control the flow of CUI in accordance with approved authorizations. Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control 3.1.3 Control the flow of CUI in accordance with approved authorizations. Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection 3.13.1 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Private endpoint should be enabled for PostgreSQL servers 1.0.2
System and Communications Protection 3.13.1 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems. Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection 3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems. PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
System and Communications Protection 3.13.16 Protect the confidentiality of CUI at rest. Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
System and Communications Protection 3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. Private endpoint should be enabled for PostgreSQL servers 1.0.2
System and Communications Protection 3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems. Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection 3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. Private endpoint should be enabled for PostgreSQL servers 1.0.2
System and Communications Protection 3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks. Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection 3.13.6 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception). Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection 3.13.8 Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Media Protection 3.8.9 Protect the confidentiality of backup CUI at storage locations. Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1

NIST SP 800-53 Rev. 4

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 4. For more information about this compliance standard, see NIST SP 800-53 Rev. 4.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-4 Information Flow Enforcement Public network access should be disabled for PostgreSQL servers 2.0.1
Access Control AC-17 Remote Access Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-17 (1) Automated Monitoring / Control Private endpoint should be enabled for PostgreSQL servers 1.0.2
Contingency Planning CP-6 Alternate Storage Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-6 (1) Separation From Primary Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-9 Information System Backup Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
System And Communications Protection SC-7 Boundary Protection Private endpoint should be enabled for PostgreSQL servers 1.0.2
System And Communications Protection SC-7 Boundary Protection Public network access should be disabled for PostgreSQL servers 2.0.1
System And Communications Protection SC-7 (3) Access Points Private endpoint should be enabled for PostgreSQL servers 1.0.2
System And Communications Protection SC-7 (3) Access Points Public network access should be disabled for PostgreSQL servers 2.0.1
System And Communications Protection SC-8 Transmission Confidentiality And Integrity Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System And Communications Protection SC-8 (1) Cryptographic Or Alternate Physical Protection Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System And Communications Protection SC-12 Cryptographic Key Establishment And Management PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
System And Communications Protection SC-28 Protection Of Information At Rest Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
System And Communications Protection SC-28 (1) Cryptographic Protection Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0

NIST SP 800-53 Rev. 5

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NIST SP 800-53 Rev. 5. For more information about this compliance standard, see NIST SP 800-53 Rev. 5.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Access Control AC-4 Information Flow Enforcement Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-4 Information Flow Enforcement Public network access should be disabled for PostgreSQL servers 2.0.1
Access Control AC-17 Remote Access Private endpoint should be enabled for PostgreSQL servers 1.0.2
Access Control AC-17 (1) Monitoring and Control Private endpoint should be enabled for PostgreSQL servers 1.0.2
Contingency Planning CP-6 Alternate Storage Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-6 (1) Separation from Primary Site Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Contingency Planning CP-9 System Backup Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
System and Communications Protection SC-7 Boundary Protection Private endpoint should be enabled for PostgreSQL servers 1.0.2
System and Communications Protection SC-7 Boundary Protection Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection SC-7 (3) Access Points Private endpoint should be enabled for PostgreSQL servers 1.0.2
System and Communications Protection SC-7 (3) Access Points Public network access should be disabled for PostgreSQL servers 2.0.1
System and Communications Protection SC-8 Transmission Confidentiality and Integrity Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System and Communications Protection SC-8 (1) Cryptographic Protection Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
System and Communications Protection SC-12 Cryptographic Key Establishment and Management PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
System and Communications Protection SC-28 Protection of Information at Rest Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
System and Communications Protection SC-28 (1) Cryptographic Protection Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0

NL BIO Cloud Theme

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for NL BIO Cloud Theme. For more information about this compliance standard, see Baseline Information Security Government Cybersecurity - Digital Government (digitaleoverheid.nl).

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
U.03 - Business Continuity services U.03 Information processing facilities should be implemented with sufficient redundancy to meet continuity requirements. Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
U.05.1 Data protection - Cryptographic measures U.05.1 Data transport is secured with cryptography where key management is carried out by the CSC itself if possible. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
U.05.2 Data protection - Cryptographic measures U.05.2 Data stored in the cloud service shall be protected to the latest state of the art. Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
U.05.2 Data protection - Cryptographic measures U.05.2 Data stored in the cloud service shall be protected to the latest state of the art. PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
U.07.1 Data separation - Isolated U.07.1 Permanent isolation of data is a multi-tenant architecture. Patches are realized in a controlled manner. Public network access should be disabled for PostgreSQL servers 2.0.1
U.11.1 Cryptoservices - Policy U.11.1 In the cryptography policy, at least the subjects in accordance with BIO have been elaborated. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
U.11.2 Cryptoservices - Cryptographic measures U.11.2 In case of PKIoverheid certificates use PKIoverheid requirements for key management. In other situations use ISO11770. Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
U.11.3 Cryptoservices - Encrypted U.11.3 Sensitive data is always encrypted, with private keys managed by the CSC. Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
U.11.3 Cryptoservices - Encrypted U.11.3 Sensitive data is always encrypted, with private keys managed by the CSC. PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4

Reserve Bank of India - IT Framework for NBFC

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - Reserve Bank of India - IT Framework for NBFC. For more information about this compliance standard, see Reserve Bank of India - IT Framework for NBFC.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Information and Cyber Security 3.1.g Trails-3.1 Disconnections should be logged for PostgreSQL database servers. 1.0.0
Information and Cyber Security 3.1.g Trails-3.1 Log checkpoints should be enabled for PostgreSQL database servers 1.0.0
Information and Cyber Security 3.1.g Trails-3.1 Log connections should be enabled for PostgreSQL database servers 1.0.0
Information and Cyber Security 3.1.g Trails-3.1 Log duration should be enabled for PostgreSQL database servers 1.0.0
Information and Cyber Security 3.1.h Public Key Infrastructure (PKI)-3.1 Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Information and Cyber Security 3.1.h Public Key Infrastructure (PKI)-3.1 Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
Information and Cyber Security 3.1.h Public Key Infrastructure (PKI)-3.1 PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
IS Audit 5.2 Coverage-5.2 Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Business Continuity Planning 6 Business Continuity Planning (BCP) and Disaster Recovery-6 Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Business Continuity Planning 6.2 Recovery strategy / Contingency Plan-6.2 Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Business Continuity Planning 6.3 Recovery strategy / Contingency Plan-6.3 Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1

Reserve Bank of India IT Framework for Banks v2016

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RBI ITF Banks v2016. For more information about this compliance standard, see RBI ITF Banks v2016 (PDF).

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Secure Mail And Messaging Systems Secure Mail And Messaging Systems-10.1 Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Advanced Real-Timethreat Defenceand Management Advanced Real-Timethreat Defenceand Management-13.3 Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Maintenance, Monitoring, And Analysis Of Audit Logs Maintenance, Monitoring, And Analysis Of Audit Logs-16.1 Log duration should be enabled for PostgreSQL database servers 1.0.0
Metrics Metrics-21.1 PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
Patch/Vulnerability & Change Management Patch/Vulnerability & Change Management-7.7 Private endpoint should be enabled for PostgreSQL servers 1.0.2
Data Leak Prevention Strategy Data Leak Prevention Strategy-15.2 Public network access should be disabled for PostgreSQL flexible servers 3.0.1
Patch/Vulnerability & Change Management Patch/Vulnerability & Change Management-7.7 Public network access should be disabled for PostgreSQL servers 2.0.1

RMIT Malaysia

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - RMIT Malaysia. For more information about this compliance standard, see RMIT Malaysia.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
Cryptography 10.16 Cryptography - 10.16 Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Cryptography 10.16 Cryptography - 10.16 Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers 1.0.0
Cryptography 10.19 Cryptography - 10.19 PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
Network Resilience 10.33 Network Resilience - 10.33 Private endpoint should be enabled for PostgreSQL servers 1.0.2
Cloud Services 10.49 Cloud Services - 10.49 Connection throttling should be enabled for PostgreSQL database servers 1.0.0
Cloud Services 10.51 Cloud Services - 10.51 Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Cloud Services 10.53 Cloud Services - 10.53 PostgreSQL servers should use customer-managed keys to encrypt data at rest 1.0.4
Data Loss Prevention (DLP) 11.15 Data Loss Prevention (DLP) - 11.15 Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Security Operations Centre (SOC) 11.18 Security Operations Centre (SOC) - 11.18 Disconnections should be logged for PostgreSQL database servers. 1.0.0
Security Operations Centre (SOC) 11.18 Security Operations Centre (SOC) - 11.18 Log checkpoints should be enabled for PostgreSQL database servers 1.0.0
Security Operations Centre (SOC) 11.18 Security Operations Centre (SOC) - 11.18 Log connections should be enabled for PostgreSQL database servers 1.0.0
Security Operations Centre (SOC) 11.18 Security Operations Centre (SOC) - 11.18 Log duration should be enabled for PostgreSQL database servers 1.0.0
Control Measures on Cybersecurity Appendix 5.6 Control Measures on Cybersecurity - Appendix 5.6 PostgreSQL server should use a virtual network service endpoint 1.0.2
Control Measures on Cybersecurity Appendix 5.6 Control Measures on Cybersecurity - Appendix 5.6 Public network access should be disabled for PostgreSQL flexible servers 3.0.1
Control Measures on Cybersecurity Appendix 5.6 Control Measures on Cybersecurity - Appendix 5.6 Public network access should be disabled for PostgreSQL servers 2.0.1
Control Measures on Cybersecurity Appendix 5.7 Control Measures on Cybersecurity - Appendix 5.7 Private endpoint should be enabled for PostgreSQL servers 1.0.2

SWIFT CSP-CSCF v2021

To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance details for SWIFT CSP-CSCF v2021. For more information about this compliance standard, see SWIFT CSP CSCF v2021.

Domain Control ID Control title Policy
(Azure portal)
Policy version
(GitHub)
SWIFT Environment Protection 1.1 SWIFT Environment Protection Private endpoint should be enabled for PostgreSQL servers 1.0.2
Reduce Attack Surface and Vulnerabilities 2.6 Operator Session Confidentiality and Integrity Enforce SSL connection should be enabled for PostgreSQL database servers 1.0.1
Detect Anomalous Activity to Systems or Transaction Records 6.3 Database Integrity Disconnections should be logged for PostgreSQL database servers. 1.0.0
Detect Anomalous Activity to Systems or Transaction Records 6.3 Database Integrity Geo-redundant backup should be enabled for Azure Database for PostgreSQL 1.0.1
Detect Anomalous Activity to Systems or Transaction Records 6.3 Database Integrity Public network access should be disabled for PostgreSQL servers 2.0.1

Next steps