@@ -218,8 +218,8 @@ For the purposes of the present document, the following terms apply:
1.**machine user:** virtual user used to access the system programming interfaces
1.**component:** software or hardware intended for integration into an electronic information system
1.**Application Programming Interface (API):** interface used to communicate with the running program
1.**Log**: A log is a record of an operational event by the user that allows to investigate which user has done what and with what result.
1.**Trace**: A trace is a record of a system status including abnormal, failure, or incident event with all related data that can be gathered, to enable for the investigation respectively analysis of the root cause for that event.
1.**log**: record of an operational event
1.**trace**: record of a system status with all relevant data that can be gathered
## 3.2 Abbreviations
@@ -296,7 +296,7 @@ This list of use cases is an informative resource for manufacturers to simplify
Manufacturer shall declare in the technical documentation the security profile for which their products are intended to be evaluated.
An NMS is a centralized product controlling at least partially connected NEs. Despite its central positioning, an NMS can be aggregated out of several components, including but not to limited end-to-end management systems, dedicated configuration management systems, or controllers for software-defined networking as described in chapter 1.2.
An NMS is a product controlling at least partially connected devices with network access. Despite its central positioning, an NMS can be aggregated out of several components, including but not to limited end-to-end management systems, dedicated configuration management systems, or controllers for software-defined networking as described in chapter 1.2.
An aggregated NMS implements further essential components for operation that are out of scope of the present standards. Those can be, as inconclusive examples, an OS that acts as abstraction layer for the system(s) that host the NMS, or further special networking interfaces.
@@ -328,15 +328,19 @@ The affected Service Requesting Users base is small like in:
The main focus of an IoT network is often data collection, whereas the NMS usually visualizes the collected data metrics to the end-user. The NMS-analysis of the data metrics can be automated including the triggering of warnings, alarms, or even actions based on discovered abnormal events. The NMS has limited computational capacities and consumes a low amount of power.
The NMS controls the configuration of the connected NEs. As a minimum, the NMS maintains (i) an inventory of devices that are part of the managed network, and (ii) establishes a trust-based relation between itself and the device. The latter can be used for secured identification, authentication and communication with other applications on the device.
The NMS collects the meta traffic data and management related data from the NEs, or forwards those to other systems for data collection and storage.
All transmitted data from the NEs to the NMS and vice versa is cryptographically protected with authentication of the endpoints, and with integrity and confidentiality protection.
The NMS controls the configuration of the connected devices. As a minimum, the NMS maintains
1. an inventory of devices that are part of the managed network,
1. establishes and maintains a trust-based relation between itself and the device.
The latter can be used for secured identification, authentication and communication with other applications on the device.
The NMS collects the meta traffic data and management related data from the devices, or forwards those to other systems for data collection and storage.
All transmitted data from the devices to the NMS and vice versa is cryptographically protected with authentication of the endpoints, and with integrity and confidentiality protection.
In dependency of the host system capabilities, the NMS can also be remote accessible.
The NMS’s and the NEs can store pre-installed keys, identity confirming certificates, or unique serial numbers. These credentials serve for the initialization of the trusted relationship between the NMS, the NEs and, if applicable, with the IoT device business logic.
The NMS’s and the devices can store pre-installed keys, identity confirming certificates, or unique serial numbers. These credentials serve for the initialization of the trusted relationship between the NMS, the devices and, if applicable, with the IoT device business logic.
The establishment of a trusted relationship requires key initialisation respectively key enrolment or establishment. That requires physical access or proximity to the IoT device. The user can pair the IoT device with the NMS with Bluetooth mechanisms or with a physical cable connection.
Once the trusted relationship has been established, the NMS can provide cryptographically protected configuration and update services to the NEs at runtime. Depending on the initial NMS and NE configurations, the NE can either request its configuration from the NMS, or the NMS can push the configuration to the NE. Both can be operated with a remote accessing authorized user to the NMS.
Once the trusted relationship has been established, the NMS can provide cryptographically protected configuration and update services to the devices at runtime. Depending on the initial NMS and NE configurations, the device can either request its configuration from the NMS, or the NMS can push the configuration to the device.
One of the NMS minimum functions is generating, keeping and maintaining a network inventory. New devices extent the inventory and the NMS holds information about the connectivity capabilities for each connected device.
@@ -411,8 +415,8 @@ The risk factors identified by the risk assessment in Annex C are grouped into r
- **[EXP-L-1]** NIS2 important or essential entity
- Access to network used for communication between elements
-**[ACC-L-0]**The management network is physically isolated from public networks with strong physical access control procedures
-**[ACC-L-1]** Like L-0, but the management network has a single physical connection to public networks and strong internal segmentation and access controls that limit spread of compromise
-**[ACC-L-0]**Network physically isolated from public networks with strong physical access control procedures
-**[ACC-L-1]** Like L-0, but network has a single physical connection to public networks and strong internal segmentation and access controls that limit spread of compromise
-**[ACC-L-2]** Private network with multiple connections to public networks filtered by firewalls, no internal segmentation
-**[ACC-L-3]** Everything else
@@ -446,7 +450,7 @@ All products with digital elements have a common set of requirements that shall
Following list of essential functions keep the NMS self-secure and correct functioning during its operation in its intended environment.
- Network element configuration and change management
-Credential based access control with subsequent corresponding authorization
-The NMS will use the apropriate level of access controll to maintain identity and actions each system actor can take
- Performance metrics assuring that the operation of the network is in the nominal levels
- Fault detection, reaction and recovery from fail state
- Functional resilience in terms of maintaining correct operation under abnormal network conditions, e.g., connection loss to NEs.
@@ -459,17 +463,8 @@ Following list of essential functions keep the NMS self-secure and correct funct
- Produce logs and traces for security and operational analysis
## 4.8 Operational Environment
The manufacturer shall describe the core requirements for the operational environment (OE). The actual protection required is linked to the criticality of the use case, and with that the OE requirements can be mapped to [SUR-L-x].
The OE for [SRU-L-0] shall ensure:
to be defined......
The OE for [SRU-L-1] shall ensure:
to be defined......
The OE for [SRU-L-2] shall ensure:
• Always available basic services the NMS requires for operation: power supply, climate control, environmental impact protection against weather, fire, earthquake, other physical impact
• Available network connections to the digital services the NMS requires or can require for operation: certificate and signature validation, backup server, logging server, timestamp server
• Physical access control to ensure access by authorized staff only
• Authorized staff shall be trained and qualified on the NMS, trusted, operate without malicious intent and act according the NMS user guidelines
The technical requirements of the present document apply under the environmental profile for operation of the product with digital elements, which shall be in accordance with its intended use. The product with digital elements shall comply with all the technical requirements of the present document at all times when operating within the boundary limits of the operational environmental profile defined by its intended use.
## 4.9 Users
@@ -588,7 +583,7 @@ Technical requirements:
-**[REQ-TECH-0]** An network management system shall implement appropriate cryptographic libraries to allow the protection to the requirements of the forseeable use.
-**[REQ-TECH-1]** The product is shipped without undocumented interfaces.
-**[REQ-TECH-2]** An administrative actions shall be recorded as an event.
-**[REQ-TECH-2]** Any administrative action shall be recorded for audit purposes.
-**[REQ-TECH-3]** A secure channel is used in transport.
-**[REQ-TECH-4]** Cryptographic keys can be changed.
-**[REQ-TECH-5]** All system components are synchronized to the same time.
<mark>AMS: Luka and Bruno are working on this. Skip for now.</mark>
-**[REQ-LOG-0]** Administrator actions and the data from the event detection are recorded into a write only service or endpoint.
-**[REQ-LOG-0]** Adminstrative actions like logs, traces and events are recorded into a write only service or endpoint.
-**[REQ-LOG-1]** The write only log or tracing storage is deployed outside of the system deployment context.
-**[REQ-LOG-2]** The system shall operate an event detection that includes security operations by the administration, logs such events and, if applicable, reports this to an external SIEM system.
-**[REQ-LOG-3]** The log file of events shall be protected from unauthorized access, modification,be backup-ed, and is optionally confidentiality protected.
-**[REQ-LOG-4]** If records land on a SIEM system, the SIEM shall protect the received event data appropriately in terms of access, integrity and confidentiality.
-**[REQ-LOG-5]** SIEM transfer format, field attributes and event descriptions are available as part of the technical documentation.
-**[REQ-LOG-6]** Deviation in clock consistency is reported forward as a SIEM event. <mark>Should this be in monitoring?</mark>
-**[REQ-LOG-2]** The system reports relevant administrative operations forward to an external SIEM system.
-**[REQ-LOG-3a]** The log file of events shall be protected from unauthorized access, modification,
-**[REQ-LOG-3b]** be backup-ed,
-**[REQ-LOG-3c]** and is confidentiality protected.
-**[REQ-LOG-4]** SIEM transfer format, field attributes and event descriptions are available as part of the technical documentation.
Manfacturer shall implement logging system features listed in the table below.
@@ -768,10 +764,10 @@ Manfacturer shall implement logging system features listed in the table below.
