Azure Policy Regulatory Compliance controls for Azure Database for PostgreSQL
APPLIES 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.
Azure Security Benchmark
The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure 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 - Azure 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.0 |
| 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 |
| 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 |
Azure Security Benchmark v1
The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. To see how this service completely maps to the Azure 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 - Azure Security Benchmark.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Network Security | 1.1 | Protect resources using Network Security Groups or Azure Firewall on your Virtual Network | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 |
| Data Protection | 4.4 | Encrypt all sensitive information in transit | Enforce SSL connection should be enabled for PostgreSQL database servers | 1.0.1 |
| Data Recovery | 9.1 | Ensure regular automated back ups | Geo-redundant backup should be enabled for Azure Database for PostgreSQL | 1.0.1 |
| Data Recovery | 9.2 | Perform complete system backups and backup any customer managed keys | Geo-redundant backup should be enabled for Azure Database for PostgreSQL | 1.0.1 |
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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 | CIS Microsoft Azure Foundations Benchmark recommendation 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 |
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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.0 |
| 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.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 servers | 2.0.0 |
| 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.
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.
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 |
New Zealand ISM Restricted
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - New Zealand ISM Restricted. For more information about this compliance standard, see New Zealand ISM Restricted.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Infrastructure | INF-9 | 10.8.35 Security Architecture | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 |
| Cryptography | CR-3 | 17.1.46 Reducing storage and physical transfer requirements | PostgreSQL servers should use customer-managed keys to encrypt data at rest | 1.0.4 |
| Cryptography | CR-14 | 17.9.25 Contents of KMPs | PostgreSQL servers should use customer-managed keys to encrypt data at rest | 1.0.4 |
| Gateway security | GS-2 | 19.1.11 Using Gateways | Public network access should be disabled for PostgreSQL servers | 2.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.
NZ ISM Restricted v3.5
To review how the available Azure Policy built-ins for all Azure services map to this compliance standard, see Azure Policy Regulatory Compliance - NZ ISM Restricted v3.5. For more information about this compliance standard, see NZ ISM Restricted v3.5.
| Domain | Control ID | Control title | Policy (Azure portal) |
Policy version (GitHub) |
|---|---|---|---|---|
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Disconnections should be logged for PostgreSQL database servers. | 1.0.0 |
| Access Control and Passwords | NZISM Security Benchmark AC-18 | 16.6.9 Events to be logged | Log connections should be enabled for PostgreSQL database servers | 1.0.0 |
| Cryptography | NZISM Security Benchmark CR-15 | 17.9.25 Contents of KMPs | PostgreSQL servers should use customer-managed keys to encrypt data at rest | 1.0.4 |
| Gateway security | NZISM Security Benchmark GS-2 | 19.1.11 Using Gateways | Public network access should be disabled for PostgreSQL servers | 2.0.0 |
| Infrastructure | NZISM Security Benchmark INF-9 | 10.8.35 Security Architecture | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 |
| Information security monitoring | NZISM Security Benchmark ISM-4 | 6.2.6 Resolving vulnerabilities | Enforce SSL connection should be enabled for PostgreSQL database servers | 1.0.1 |
| Network security | NZISM Security Benchmark NS-7 | 18.4.7 Intrusion Detection and Prevention strategy (IDS/IPS) | Connection throttling should be enabled for PostgreSQL database servers | 1.0.0 |
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 | RBI IT Framework 3.1.g | Trails-3.1 | Disconnections should be logged for PostgreSQL database servers. | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.g | Trails-3.1 | Log checkpoints should be enabled for PostgreSQL database servers | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.g | Trails-3.1 | Log connections should be enabled for PostgreSQL database servers | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 3.1.g | Trails-3.1 | Log duration should be enabled for PostgreSQL database servers | 1.0.0 |
| Information and Cyber Security | RBI IT Framework 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 | RBI IT Framework 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 | RBI IT Framework 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 | RBI IT Framework 5.2 | Coverage-5.2 | Geo-redundant backup should be enabled for Azure Database for PostgreSQL | 1.0.1 |
| Business Continuity Planning | RBI IT Framework 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 | RBI IT Framework 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 | RBI IT Framework 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 | |
| Secure Mail And Messaging Systems | Secure Mail And Messaging Systems-10.2 | Enforce SSL connection should be enabled for PostgreSQL database servers | 1.0.1 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | Enforce SSL connection should be enabled for PostgreSQL database servers | 1.0.1 | |
| Incident Response & Management | Recovery From Cyber - Incidents-19.5 | Geo-redundant backup should be enabled for Azure Database for PostgreSQL | 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 | |
| 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 | |
| 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 | |
| Metrics | Metrics-21.1 | PostgreSQL servers should use customer-managed keys to encrypt data at rest | 1.0.4 | |
| Advanced Real-Timethreat Defenceand Management | Advanced Real-Timethreat Defenceand Management-13.4 | PostgreSQL servers should use customer-managed keys to encrypt data at rest | 1.0.4 | |
| Anti-Phishing | Anti-Phishing-14.1 | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 | |
| 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.0 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Public network access should be disabled for PostgreSQL flexible servers | 3.0.0 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Public network access should be disabled for PostgreSQL servers | 2.0.0 | |
| Anti-Phishing | Anti-Phishing-14.1 | Public network access should be disabled for PostgreSQL servers | 2.0.0 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Public network access should be disabled for PostgreSQL servers | 2.0.0 | |
| Data Leak Prevention Strategy | Data Leak Prevention Strategy-15.2 | Public network access should be disabled for PostgreSQL servers | 2.0.0 | |
| Patch/Vulnerability & Change Management | Patch/Vulnerability & Change Management-7.7 | Public network access should be disabled for PostgreSQL servers | 2.0.0 |
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 | RMiT 10.16 | Cryptography - 10.16 | Enforce SSL connection should be enabled for PostgreSQL database servers | 1.0.1 |
| Cryptography | RMiT 10.16 | Cryptography - 10.16 | Infrastructure encryption should be enabled for Azure Database for PostgreSQL servers | 1.0.0 |
| Cryptography | RMiT 10.19 | Cryptography - 10.19 | PostgreSQL servers should use customer-managed keys to encrypt data at rest | 1.0.4 |
| Network Resilience | RMiT 10.33 | Network Resilience - 10.33 | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 |
| Cloud Services | RMiT 10.49 | Cloud Services - 10.49 | Connection throttling should be enabled for PostgreSQL database servers | 1.0.0 |
| Cloud Services | RMiT 10.51 | Cloud Services - 10.51 | Geo-redundant backup should be enabled for Azure Database for PostgreSQL | 1.0.1 |
| Cloud Services | RMiT 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) | RMiT 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) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Disconnections should be logged for PostgreSQL database servers. | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Disconnections should be logged for PostgreSQL database servers. | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Log checkpoints should be enabled for PostgreSQL database servers | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Log checkpoints should be enabled for PostgreSQL database servers | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Log connections should be enabled for PostgreSQL database servers | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Log connections should be enabled for PostgreSQL database servers | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Log duration should be enabled for PostgreSQL database servers | 1.0.0 |
| Security Operations Centre (SOC) | RMiT 11.18 | Security Operations Centre (SOC) - 11.18 | Log duration should be enabled for PostgreSQL database servers | 1.0.0 |
| Control Measures on Cybersecurity | RMiT 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 | RMiT Appendix 5.6 | Control Measures on Cybersecurity - Appendix 5.6 | Public network access should be disabled for PostgreSQL flexible servers | 3.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.6 | Control Measures on Cybersecurity - Appendix 5.6 | Public network access should be disabled for PostgreSQL servers | 2.0.0 |
| Control Measures on Cybersecurity | RMiT Appendix 5.7 | Control Measures on Cybersecurity - Appendix 5.7 | Private endpoint should be enabled for PostgreSQL servers | 1.0.2 |
Next steps
- Learn more about Azure Policy Regulatory Compliance.
- See the built-ins on the Azure Policy GitHub repo.
Feedback
Submit and view feedback for