@@ -90,6 +90,13 @@ This includes, but is not limited to, Mobile Device Management systems and Softw
NMS intended for use in the industrial OT (Operational Technology)[\[i.18\]](#_ref_i.18) domain are excluded from the scope of the present document.
An NMS is a product controlling at least partially connected devices with network access.
Despite its central positioning, an NMS can be an aggregate of several components, including but not limited to: end-to-end management systems, dedicated configuration management systems, or controllers for software-defined networking.
NMS can be composed of several components or can implement additional functions that are outside the scope of the present document.
> Example: Aggregate product design would be an implementation where the operating system acts as an abstraction layer for the system(s) that host the NMS, or the networking interfaces.
# 2 References
## 2.1 Normative references
@@ -803,16 +810,15 @@ The term subject should not be mismatched with product users or with service req
## 4.6 Use Cases
This list of use cases is a resource for manufacturers to simplify the selection of a set of cybersecurity requirements.
The purpose of a use case is to create defined sets of technical requirements (Clause 5) that may be used to treat the risks found by the manufacturer's independent cybersecurity risk analysis.
Manufacturer's technical documentation may benefit from including or referring to these use cases.
Use cases are defined by their risk factor levels. The risk factor levels are used by the informative Security Analysis in Annex B to select the group of technical requirements associated with that use case.
An NMS is a product controlling at least partially connected elements with network access. Despite its central positioning, an NMS can be an aggregate of several components, including but not limited to: end-to-end management systems, dedicated configuration management systems, or controllers for software-defined networking as described in [1 Scope](#1-scope).
Specific use cases are identified by their use case IDs, which are constructed in the following manner:
NMS can be composed of several components or can implement additional functions that are outside the scope of the present standards.
One example of this type of aggregate product design would be an implementation where the operating system acts as an abstraction layer for the system(s) that host the NMS, or the networking interfaces.
**UC-\[X\]-\[WORD\]**
### 4.6.1 (UC-1-HOME) Home network deployment
Where "X" is a number and "WORD" is a short word that serves to remind the reader of one or more examples.
