@@ -219,8 +219,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
**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.
**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**: 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.
## 3.2 Abbreviations
@@ -289,6 +289,8 @@ NMS’ can interface with PKI and SIEM systems if it is justified by the require
The main functionality of an NMS is to interface and interact with routers, modems and switches.
More about assets in [Annex C.1 Assets](#c1-assets) and [Annex C.2 Data](#c11-data).
## 4.4 Use cases
This list of use cases is an informative resource for manufacturers to simplify the selection of a set of cybersecurity requirements. Each use case is mapped to a security profile, which is a collection of risks and the cybersecurity requirements necessary to mitigate them.
@@ -452,7 +454,10 @@ Following list of essential functions keep the NMS self-secure and correct funct
- 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.
- Functional resilience in case of (i) loss of connectivity to connected NEs totally or partially, (ii) to required network services for example time stamps and backup, and (iii) power off.
- Functional resilience in case of
1. loss of connectivity to connected NEs totally or partially,
1. to required network services for example time stamps and backup, and
1. power off.
- Dynamic routing and switching control based on requests. Used extensively with Software Defined Networks.
- Device discovery, inventory building and depending on the use case topology map generation.
- Produce logs and traces for security and operational analysis
