6.8: Network segmentation

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

1. The relevant entities shall segment systems into networks or zones in accordance with the results of the risk assessment referred to in point 2.1. They shall segment their systems and networks from third parties’ systems and networks.

2. For that purpose, the relevant entities shall:

  1. consider the functional, logical and physical relationship, including location, between trustworthy systems and services;
  2. grant access to a network or zone based on an assessment of its security requirements;
  3. keep systems that are critical to the relevant entities operation or to safety in secured zones;
  4. deploy a demilitarised zone within their communication networks to ensure secure communication originating from or destined to their networks;
  5. restrict access and communications between and within zones to those necessary for the operation of the relevant entities or for safety;
  6. separate the dedicated network for administration of network and information systems from the relevant entities’ operational network;
  7. segregate network administration channels from other network traffic;
  8. separate the production systems for the relevant entities’ services from systems used in development and testing, including backups.

3. The relevant entities shall review and, where appropriate, update network segmentation at planned intervals and when significant incidents or significant changes to operations or risks.

This requirement is part of the framework:  
NIS2 Implementing Regulation
Best practices
How to implement:
6.8: Network segmentation
This policy on
6.8: Network segmentation
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.

1. The relevant entities shall segment systems into networks or zones in accordance with the results of the risk assessment referred to in point 2.1. They shall segment their systems and networks from third parties’ systems and networks.

2. For that purpose, the relevant entities shall:

  1. consider the functional, logical and physical relationship, including location, between trustworthy systems and services;
  2. grant access to a network or zone based on an assessment of its security requirements;
  3. keep systems that are critical to the relevant entities operation or to safety in secured zones;
  4. deploy a demilitarised zone within their communication networks to ensure secure communication originating from or destined to their networks;
  5. restrict access and communications between and within zones to those necessary for the operation of the relevant entities or for safety;
  6. separate the dedicated network for administration of network and information systems from the relevant entities’ operational network;
  7. segregate network administration channels from other network traffic;
  8. separate the production systems for the relevant entities’ services from systems used in development and testing, including backups.

3. The relevant entities shall review and, where appropriate, update network segmentation at planned intervals and when significant incidents or significant changes to operations or risks.

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
6.8: Network segmentation
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
6.8: Network segmentation
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Network security and segregation
Critical
High
Normal
Low
4
requirements
Technical cyber security
Network security

Network security and segregation

This task helps you comply with the following requirements

Performing traffic filtering between network segments
Critical
High
Normal
Low
Detailed procedures for the management, control and segmentation of networks
Critical
High
Normal
Low

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.