3.2.3: Log management and review

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

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:

  1. relevant outbound and inbound network traffic;
  2. creation, modification or deletion of users of the relevant entities’ network and information systems and extension of the permissions;
  3. access to systems and applications;
  4. authentication-related events;
  5. all privileged access to systems and applications, and activities performed by administrative accounts;
  6. access or changes to critical configuration and backup files;
  7. event logs and logs from security tools, such as antivirus, intrusion detection systems or firewalls;
  8. use of system resources, as well as their performance;
  9. physical access to facilities;
  10. access to and use of their network equipment and devices;
  11. activation, stopping and pausing of the various logs;
  12. environmental events.

This requirement is part of the framework:  
NIS2 Implementing Regulation
Best practices
How to implement:
3.2.3: Log management and review
This policy on
3.2.3: Log management and review
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

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:

  1. relevant outbound and inbound network traffic;
  2. creation, modification or deletion of users of the relevant entities’ network and information systems and extension of the permissions;
  3. access to systems and applications;
  4. authentication-related events;
  5. all privileged access to systems and applications, and activities performed by administrative accounts;
  6. access or changes to critical configuration and backup files;
  7. event logs and logs from security tools, such as antivirus, intrusion detection systems or firewalls;
  8. use of system resources, as well as their performance;
  9. physical access to facilities;
  10. access to and use of their network equipment and devices;
  11. activation, stopping and pausing of the various logs;
  12. environmental events.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
3.2.3: Log management and review
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
3.2.3: Log management and review
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Defining events that need to be logged
Critical
High
Normal
Low
Logging and review of admin and security logs
Critical
High
Normal
Low
Deployment and regular analysis of security system logs
Critical
High
Normal
Low
57
requirements
Technical cyber security
Security systems and logging

Deployment and regular analysis of security system logs

This task helps you comply with the following requirements

Process for identifying and responding to system log faults
Critical
High
Normal
Low
4
requirements
Technical cyber security
Security systems and logging

Process for identifying and responding to system log faults

This task helps you comply with the following requirements

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.