+3.2. Monitoring and logging
---+3.2.1. The relevant entities shall lay down procedures and use tools to monitor and log activities …
---+3.2.2. To the extent feasible, monitoring shall be automated and carried out either continuously or …
---+3.2.3. Based on the procedures referred to in point 3.2.1, the relevant entities shall maintain …
---+3.2.4. The logs shall be regularly reviewed for any unusual or unwanted trends. Where appropriate …
---+3.2.5. The relevant entities shall maintain and back up logs for a predefined period and shall …
---+3.2.6. To the extent feasible, the relevant entities shall ensure that all systems have …
---+3.2.7. The procedures as well as the list of assets that are being logged shall be reviewed and …
|
3.2. Monitoring and logging
3.2. Monitoring and logging
1. Przegląd
| Tytuł |
Regulacja |
|
3.2.1. The relevant entities shall lay down procedures and use tools to monitor and log activities …
|
|
3.2.1.
|
The relevant entities shall lay down procedures and use tools to monitor and log activities on their network and information systems to detect events that could be considered as incidents and respond accordingly to mitigate the impact.
|
|
|
3.2.2. To the extent feasible, monitoring shall be automated and carried out either continuously or …
|
|
3.2.2.
|
To the extent feasible, monitoring shall be automated and carried out either continuously or in periodic intervals, subject to business capabilities. The relevant entities shall implement their monitoring activities in a way which minimises false positives and false negatives.
|
|
|
3.2.3. Based on the procedures referred to in point 3.2.1, the relevant entities shall maintain …
|
|
3.2.3.
|
Based on the procedures referred to in point 3.2.1, the relevant entities shall maintain, document, and review logs. The relevant entities shall establish a list of assets to be subject to logging based on the results of the risk assessment carried out pursuant to point 2.1. Where appropriate, logs shall include:
|
(a)
|
relevant outbound and inbound network traffic;
|
|
(b)
|
creation, modification or deletion of users of the relevant entities’ network and information systems and extension of the permissions;
|
|
(c)
|
access to systems and applications;
|
|
(d)
|
authentication-related events;
|
|
(e)
|
all privileged access to systems and applications, and activities performed by administrative accounts;
|
|
(f)
|
access or changes to critical configuration and backup files;
|
|
(g)
|
event logs and logs from security tools, such as antivirus, intrusion detection systems or firewalls;
|
|
(h)
|
use of system resources, as well as their performance;
|
|
(i)
|
physical access to facilities;
|
|
(j)
|
access to and use of their network equipment and devices;
|
|
(k)
|
activation, stopping and pausing of the various logs;
|
|
(l)
|
environmental events.
|
|
|
|
3.2.4. The logs shall be regularly reviewed for any unusual or unwanted trends. Where appropriate …
|
|
3.2.4.
|
The logs shall be regularly reviewed for any unusual or unwanted trends. Where appropriate, the relevant entities shall lay down appropriate values for alarm thresholds. If the laid down values for alarm threshold are exceeded, an alarm shall be triggered, where appropriate, automatically. The relevant entities shall ensure that, in case of an alarm, a qualified and appropriate response is initiated in a timely manner.
|
|
|
3.2.5. The relevant entities shall maintain and back up logs for a predefined period and shall …
|
|
3.2.5.
|
The relevant entities shall maintain and back up logs for a predefined period and shall protect them from unauthorised access or changes.
|
|
|
3.2.6. To the extent feasible, the relevant entities shall ensure that all systems have …
|
|
3.2.6.
|
To the extent feasible, the relevant entities shall ensure that all systems have synchronised time sources to be able to correlate logs between systems for event assessment. The relevant entities shall establish and keep a list of all assets that are being logged and ensure that monitoring and logging systems are redundant. The availability of the monitoring and logging systems shall be monitored independent of the systems they are monitoring.
|
|
|
3.2.7. The procedures as well as the list of assets that are being logged shall be reviewed and …
|
|
3.2.7.
|
The procedures as well as the list of assets that are being logged shall be reviewed and, where appropriate, updated at regular intervals and after significant incidents.
|
|
,
1.1 Odwołania
1.2 Zidentyfikowane wymagania
1.3 Powiązane normy
2. Zidentyfikowane wymagania
Wymagania
| Źródło |
Wymaganie |
3. Powiązane normy
Powiązane zgłoszenia
|