compliance controls are associated with this Policy definition 'Log connections should be enabled for PostgreSQL database servers' (eb6f77b9-bd53-4e35-a23d-7f65d5f0e442)
| Control Domain |
Control |
Name |
MetadataId |
Category |
Title |
Owner |
Requirements |
Description |
Info |
Policy# |
| CIS_Azure_1.1.0 |
4.14 |
CIS_Azure_1.1.0_4.14 |
CIS Microsoft Azure Foundations Benchmark recommendation 4.14 |
4 Database Services |
Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server |
Shared |
The customer is responsible for implementing this recommendation. |
Enable 'log_connections' on 'PostgreSQL Servers'. |
link |
5 |
| CIS_Azure_1.3.0 |
4.3.4 |
CIS_Azure_1.3.0_4.3.4 |
CIS Microsoft Azure Foundations Benchmark recommendation 4.3.4 |
4 Database Services |
Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server |
Shared |
The customer is responsible for implementing this recommendation. |
Enable 'log_connections' on 'PostgreSQL Servers'. |
link |
5 |
| CIS_Azure_1.4.0 |
4.3.3 |
CIS_Azure_1.4.0_4.3.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 4.3.3 |
4 Database Services |
Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server |
Shared |
The customer is responsible for implementing this recommendation. |
Enable 'log_connections' on 'PostgreSQL Servers'. |
link |
5 |
| CIS_Azure_2.0.0 |
4.3.3 |
CIS_Azure_2.0.0_4.3.3 |
CIS Microsoft Azure Foundations Benchmark recommendation 4.3.3 |
4.3 |
Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server |
Shared |
n/a |
Enable `log_connections` on `PostgreSQL Servers`.
Enabling `log_connections` helps PostgreSQL Database to log attempted connection to the server, as well as successful completion of client authentication. Log data can be used to identify, troubleshoot, and repair configuration errors and suboptimal performance. |
link |
5 |
| NZ_ISM_v3.5 |
AC-18 |
NZ_ISM_v3.5_AC-18 |
NZISM Security Benchmark AC-18 |
Access Control and Passwords |
16.6.9 Events to be logged |
Customer |
n/a |
The events to be logged are key elements in the monitoring of the security posture of systems and contributing to reviews, audits, investigations and incident management. |
link |
19 |
| RBI_ITF_NBFC_v2017 |
3.1.g |
RBI_ITF_NBFC_v2017_3.1.g |
RBI IT Framework 3.1.g |
Information and Cyber Security |
Trails-3.1 |
|
n/a |
The IS Policy must provide for a IS framework with the following basic tenets:
Trails- NBFCs shall ensure that audit trails exist for IT assets satisfying its business requirements including regulatory and legal requirements, facilitating audit, serving as forensic evidence when required and assisting in dispute resolution. If an employee, for instance, attempts to access an unauthorized section, this improper activity should be recorded in the audit trail. |
link |
39 |
| RMiT_v1.0 |
11.18 |
RMiT_v1.0_11.18 |
RMiT 11.18 |
Security Operations Centre (SOC) |
Security Operations Centre (SOC) - 11.18 |
Shared |
n/a |
The SOC must be able to perform the following functions:
(a) log collection and the implementation of an event correlation engine with parameter-driven use cases such as Security Information and Event Management (SIEM);
(b) incident coordination and response;
(c) vulnerability management;
(d) threat hunting;
(e) remediation functions including the ability to perform forensic artifact handling, malware and implant analysis; and
(f) provision of situational awareness to detect adversaries and threats including threat intelligence analysis and operations, and monitoring indicators of compromise (IOC). This includes advanced behavioural analysis to detect signature-less and file-less malware and to identify anomalies that may pose security threats including at endpoints and network layers. |
link |
14 |