Added UC-9-RESEARCH, UC-10-AIRGAP and UC-11-WATER; Added use-case... (0f2c47ec) · Commits · STAN4CRA / EN 304 621 Network Management Systems

EN-304-621.md

+225 −26

Original line number	Diff line number	Diff line
		@@ -820,6 +820,8 @@ Specific use cases are identified by their use case IDs, which are constructed i

		Where "X" is a number and "WORD" is a short word that serves to remind the reader of one or more examples.

		### 4.6.1 UC-1-HOME: Home NMS

		![Figure 4.6.1-1: Home network deployment](./media/2025-08-10_homenetwork.drawio.png)

		Figure 4.6.1-1: Home network deployment
		@@ -843,7 +845,24 @@ Metrics from the managed elements within the home network can be forwarded to th
		In many deployments, the NMS provides actual configuration control and visualization of the collected metric data with an additional service or alternate piece of software.
		That is mostly a browser, but sometimes also other possibilities are deployed, such as a command-line interface.

		### 4.6.2 (UC-2-ENTER) Enterprise network
		* Goal: Manage network configuration for a small number of home devices
		* Examples: Home network manager, mesh network management
		* Function: Connect home devices to the local network and to the public network
		* Network connectivity: Filtered private network

		**Table

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| Medium \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Low \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Low \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Low \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Low \|
		\| RF-NUM \| Number of elements \| Low \|
		\| RF-ADMIN \| Administration skill \| High \|

		### 4.6.2 UC-2-ENTER-\*: Enterprise network

		![Figure 4.6.2-1: Enterprise network](./media/2025-08-10_office.drawio.png)

		@@ -874,7 +893,46 @@ While many small businesses can perform the credential cleanup on former employe
		Additionally, entities within this context may store and work with extremely personal and sensitive data, such as a medical facility's patient records or a bank that needs to secure financial data.
		The type of deployment and actions of the service requesting users are not important to the NMS, except to the degree that the NMS must ensure that the system has the features, hardware, and security to match operational needs.

		### 4.6.3 (UC-3-TELCO) Telecommunications network
		The use-cases UC-2-ENTER-S, UC-2-ENTER-M and UC-2-ENTER-L reflects the size of the enterprise.

		Table 4.6.2-1: UC-2-ENTER-S classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Low \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Low \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Low \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Low \|
		\| RF-NUM \| Number of elements \| Low \|
		\| RF-ADMIN \| Administration skill \| High \|

		Table 4.6.2-2: UC-2-ENTER-M classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Medium \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Medium \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Medium \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Medium \|
		\| RF-NUM \| Number of elements \| Medium \|
		\| RF-ADMIN \| Administration skill \| Medium \|

		Table 4.6.2-3: UC-2-ENTER-L classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Medium \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Medium \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Medium \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Medium \|
		\| RF-NUM \| Number of elements \| High \|
		\| RF-ADMIN \| Administration skill \| Low \|


		### 4.6.3 UC-3-TELCO: Telecommunications network

		![Figure 4.6.3-1: Telecommunications network](./media/2025-08-10_telco.drawio.png)

		@@ -893,11 +951,24 @@ In telecommunications deployments of NMS it is common to provide an in-house Pub
		The number of these managed machines, number of CA's, and how the CA's are used is dependent on the design of the network.
		Alternatively, even at telecommunications scale, NMS can even provide its own certificates and form an independent and segregated trust domain.

		### 4.6.4 Software defined network management
		* Goal: Manage telecommunications infrastructure
		* Examples: National phone and data telecommunications provider, virtual telco
		* Function: Manage network topology and device configuration
		* Network connectivity: Public

		The following two use cases in sub-chapters consider such deployment and other complex deployments primarily by focusing two approaches.
		Table 4.6.3-1: UC-3-TELCO classification

		#### 4.6.4.1 (UC-4-SDN) Logical network deployment without physical hardware
		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| High \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| High \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| High \|
		\| RF-SENS_FUN \| Sensitivity of functions \| High \|
		\| RF-NUM \| Number of elements \| High \|
		\| RF-ADMIN \| Administration skill \| Low \|

		### 4.6.4 UC-4-SDN: Logical network deployment without physical hardware

		A traditional simple network design has a single device listening on incoming connections from a public network facing port and allows selected traffic to pass through to subnets behind the device.
		A mesh network can be a set of these devices, physical or virtual, where multiple subnetworks are interconnected together, and the routing design is many-to-many instead of point-to-point.
		@@ -905,13 +976,25 @@ While it is often possible to manage the individual node configuration, and the

		![From classic gateway to mesh networking](./media/4_logical_network_deployment.drawio.png)

		Figure 4.6.4.1-1: From classic gateway to mesh networking
		Figure 4.6.4-1: From classic gateway to mesh networking

		Mesh network routing can be made more accurate, if the services are listed as routing targets, and the subjects who would like to have connectivity to those targets are identified.
		Combining the known locations of services and subjects connectivity grants, a custom routing table can be calculated for each subject.
		This custom routing table can be enforced on the network side by an added layer of control, that either provisions configuration changes to connected nodes firewalls, or provides other mechanisms to assert the authority of the connection.

		#### 4.6.4.2 (UC-5-HYBRID) Physical network deployment with RDPS
		Table 4.6.4-1: UC-4-SDN classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| High \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| High \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| High \|
		\| RF-SENS_FUN \| Sensitivity of functions \| High \|
		\| RF-NUM \| Number of elements \| High \|
		\| RF-ADMIN \| Administration skill \| Low \|

		### 4.6.5 UC-5-HYBRID: Physical network deployment with RDPS

		When almost everything can be software, the minimum still remains: the user needs to have some form of User Equipment to be able to connect.
		This Network Interface can be a radio in the cellphone, a WiFi Access Point in the living room, or a router with SFP+ ports serving the local datacenter.
		@@ -919,9 +1002,9 @@ How much the network structure has autonomy on control and local network routing

		Inter-networking architecture with RDPS participating in the routing transforms a physical deployment into a logical deployment in the convergence point, which is the device installed into the site.

		![Figure 4.6.4.2-1: Maximum RDPS involvement](./media/2026-04-14_rdps_max.drawio.png)
		![Figure 4.6.5-1: Maximum RDPS involvement](./media/2026-04-14_rdps_max.drawio.png)

		Figure 4.6.4.2-1: Maximum RDPS involvement
		Figure 4.6.5-1: Maximum RDPS involvement

		In the figure above, the maximum RDPS involvement, the network handles the connection like a hot potato: it is handed over to the RDPS immediately or as soon as possible.
		The local network is used as little as possible, and even the home office routing can take a detour through RDPS in order to provide an auditable trail of how the remote working employee is using the network.
		@@ -929,9 +1012,9 @@ The local network is used as little as possible, and even the home office routin
		Technologies like 5G slicing, enable for the flexibility of the closest point of return in respect to re-routing back to the user network: It could be the nearest base station or even the a forward proxy server server on the other side of the world.
		These two scenarios result in a different user experience where the latter would most likely show as slow and unresponsive service, but both are valid designs that can be deployed.

		![Figure 4.6.4.2-2: Medium RDPS involvement](./media/2026-04-14_rdps_mid.drawio.png)
		![Figure 4.6.5-2: Medium RDPS involvement](./media/2026-04-14_rdps_mid.drawio.png)

		Figure 4.6.4.2-2: Medium RDPS involvement
		Figure 4.6.5-2: Medium RDPS involvement

		Medium RDPS involvement is a common hybrid setup, where the company already has older assets that are grown into the enterprise, and are kept around as there is little or no need to change the infrastructure.
		Part of the network design is created with virtual assets, that could be the new IT infrastructure for the latest acquired company, while the still significant portion of networking assets are tied to the headquarters datacenter.
		@@ -940,9 +1023,9 @@ Control structures are different, device management strategies are varying, and
		The balance of owned assets and bought services is often selected due to ease of deployment, while the partial reliance on headquarters datacenter offers resilience towards major outages in the connectivity.
		The end result might not be optimal, but often acceptable in the eyes of company risk management.

		![Figure 4.6.4.2-3: Minimal RDPS involvement](./media/2026-04-14_rdps_min.drawio.png)
		![Figure 4.6.5-3: Minimal RDPS involvement](./media/2026-04-14_rdps_min.drawio.png)

		Figure 4.6.4.2-3: Minimal RDPS involvement
		Figure 4.6.5-3: Minimal RDPS involvement

		In a minimal RDPS involvement, all of the relevant infrastructure is not fulfilling the RDPS definition, and can be deployed to an underground infrastructure spanning multiple locations for example.
		Interconnection between the sites is either owned, or leased from a provider.
		@@ -951,11 +1034,23 @@ Some links can be through dedicated IP/MPLS tunnels, while some could be impleme

		While system updates are critical for the product, the installation is fully independent and no functionality is relying on the RDPS connectivity. The system updates can be delivered with a removable medium, if no connectivity to software repositories is available.

		### 4.6.5 (UC-6-IOT) IoT network with monitoring data collection
		Table 4.6.5-1: UC-5-HYBRID classification

		![Figure 4.6.5-1: IoT network with monitoring data collection](./media/2025-08-10_iot.drawio.png)
		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| High \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| High \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| High \|
		\| RF-SENS_FUN \| Sensitivity of functions \| High \|
		\| RF-NUM \| Number of elements \| High \|
		\| RF-ADMIN \| Administration skill \| Low \|

		Figure 4.6.5-1: IoT network with monitoring data collection
		### 4.6.6 UC-6-IOT: IoT network with monitoring data collection

		![Figure 4.6.6-1: IoT network with monitoring data collection](./media/2025-08-10_iot.drawio.png)

		Figure 4.6.6-1: IoT network with monitoring data collection

		Contemporary advancements in microcontroller features and related platforms used to build IoT devices blur the distinction between a simple device and a complex computation node, often reducing the description of a device as "IoT" to a branding decision from the manufacturer.

		@@ -975,7 +1070,24 @@ Beyond collecting data from connected devices and preparing data metrics, the NM
		1. Establishes trust between the system and the devices.
		2. Maintain an inventory of devices that are part of the managed network.

		### 4.6.6 (UC-7-ICT) ICT Network Elements
		* Goal: Manage large fleet of IoT devices
		* Examples: NMS for network-connected washing machines or toasters
		* Function: Manage network configuration for a large fleet of appliances
		* Network connectivity: Public network

		Table 4.6.6-1: UC-6-IOT classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Low \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Low \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Medium \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Low \|
		\| RF-NUM \| Number of elements \| High \|
		\| RF-ADMIN \| Administration skill \| Medium \|

		### 4.6.7 UC-7-ICT: ICT Network Elements

		The ICT Element management is an enterprise-focused system to control and manage the configuration of the connected enterprise application on the ICT Elements.
		An ICT Element can encompass anything from routers, modems, switches up to mobile devices, tablets, smart phones, laptops, desktop PCs to servers.
		@@ -1009,9 +1121,9 @@ The NMS operating the configuration of the enterprise owned parts usually also e
		The mobile device management must not be mismatched with the management functions that are subject to the radio network management functionality that ensures connectivity and performance with the RAN.
		These requirements are handled with the EN 304 642 network functions [\[i.17\]](#_ref_i.17).

		![Figure 4.6.6-1: Multiple Network Management Systems](./media/2026-06-22_ict_element.drawio.png)
		![Figure 4.6.7-1: Multiple Network Management Systems](./media/2026-06-22_ict_element.drawio.png)

		Figure 4.6.6-1: Multiple Network Management Systems
		Figure 4.6.7-1: Multiple Network Management Systems

		ICT Elements can have four managing entities at the same time as illustrated in the figure above:

		@@ -1037,7 +1149,19 @@ ICT Elements can have four managing entities at the same time as illustrated in

		In all cases, application rights are managed and controlled, as the device management remains subject of the enterprise NMS, as the ICT elements are and remain in ownership of the enterprise.

		### 4.6.7 (UC-8-FLEET) Server and host fleet lifecycle management
		Table 4.6.7-1: UC-7-ICT classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| High \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Medium \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Medium \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Medium \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Medium \|
		\| RF-NUM \| Number of elements \| Medium \|
		\| RF-ADMIN \| Administration skill \| Medium \|

		### 4.6.8 UC-8-FLEET: Fleet management

		![Figure 4.6.7-1: Fleet management](./media/fleet_management.drawio.png)

		@@ -1069,6 +1193,81 @@ The integrity and authenticity of delivered content and configuration, the stren

		> NOTE: This use case concerns the system that manages the hosts. The intrinsic security of the operating systems running on the managed hosts is addressed by ETSI EN 304 626 [\[i.15\]](#_ref_i.15).

		* Goal: Manage network configuration in a controlled homogenous fleet of devices
		* Examples: Servers in a data center, phones in a test lab
		* Function: Configure network of managed elements, maintain simple network topology
		* Network connectivity: Filtered private

		Table 4.6.8-1: UC-8-FLEET classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| Medium \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Medium \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Low \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| High \|
		\| RF-SENS_FUN \| Sensitivity of functions \| High \|
		\| RF-NUM \| Number of elements \| Medium \|
		\| RF-ADMIN \| Administration skill \| Low \|

		### 4.6.9 UC-9-RESEARCH: Research NMS

		* Goal: Provide minimum functionality for research or training
		* Examples: Simple NMS for a collection of containers used for research or training
		* Function: Configure network on simulated managed elements or operate a laboratory
		* Network connectivity: Isolated private network

		Table 4.6.9-1: UC-9-RESEARCH classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| Low \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Low \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Low \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| Low \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Low \|
		\| RF-NUM \| Number of elements \| Low \|
		\| RF-ADMIN \| Administration skill \| Low \|

		### 4.6.10 UC-10-AIRGAP: Airgapped secure facility

		* Goal: Control network configuration in an isolated network
		* Examples: Malware research lab, highly sensitive software development facility
		* Function: Configure devices and network configuration in highly controlled environment
		* Network connectivity: Isolated private

		Table 4.6.10-1: UC-10-AIRGAP classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| Low \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Low \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Low \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| High \|
		\| RF-SENS_FUN \| Sensitivity of functions \| High \|
		\| RF-NUM \| Number of elements \| High \|
		\| RF-ADMIN \| Administration skill \| Low \|

		### 4.6.11 UC-11-WATER: Management of distributed infrastructure

		* Goal: Manage connectivity to widely scattered infrastructure devices of an important entity.
		* Examples: Network configuration of water pumps and waste management entities.
		* Function: Configure network of managed elements with occasional network topology changes.
		* Network connectivity: Public

		Table 4.6.11-1: UC-11-WATER classification

		\| ID \| Risk factor \| Classification \|
		\| --------------- \| --------------------------- \| -------------- \|
		\| RF-ACC_ASSETS \| Accessibility to product \| Medium \|
		\| RF-COMPLEX_CONF \| Complexity of configuration \| Medium \|
		\| RF-COMPLEX_FUN \| Complexity of functions \| Medium \|
		\| RF-SENS_ASSETS \| Sensitivity of elements \| High \|
		\| RF-SENS_FUN \| Sensitivity of functions \| Medium \|
		\| RF-NUM \| Number of elements \| Medium \|
		\| RF-ADMIN \| Administration skill \| Medium \|


		# 5 Technical requirements for the Products

		## 5.1 Introduction - Applicability of the requirements
		@@ -1086,7 +1285,7 @@ High requirement level shall implement all requirements in the defined set of re
		Table 5.1-1: Mapping of all use-cases to requirement sets

		\| Use-case \| Requirement set \| required level \|
		\|:------------\|-----------------\|-----------------\|
		\| :---------- \| --------------- \| --------------- \|
		\| UC-1-HOME, \| CYB_GENERAL \| low \|
		\| UC-2-ENTER \| CYB_GENERAL \| low/medium/high \|
		\| UC-3-TELCO \| CYB_GENERAL \| high \|
		@@ -1246,9 +1445,9 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
		These requirements apply to the product, regardless of the product's use case and without variation for different tiers or risk.

		* AAC_AUTH-1 The product shall support identity management through at least one of the following approaches:
		* integration of the product into an external state-of-the-art Identity Management System, or
		* integration of an external Identity Management System into the product, or
		* a dedicated Identity Management module built into the product.
		1. integration of the product into an external state-of-the-art Identity Management System, or
		2. integration of an external Identity Management System into the product, or
		3. a dedicated Identity Management module built into the product.
		* AAC_AUTH-2 The product shall not allow for default credentials or keys to be used to identify subjects.
		* AAC_AUTH-3 The product shall use multi‑factor authentication to authenticate system users.
		* AAC_AUTH-4 The product shall limit a system user’s session validity duration via a configurable setting that shall initially be limited to a default of, at maximum, one day.