> Should you need a step-by-step guide for drafting an ETSI deliverable, please consult the " [Principles for Drafting ETSI Deliverables](https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Principles_for_drafting_ETSI_deliverables.pdf)" document. Otherwise you may contact us at [edithelp@etsi.org](mailto:edithelp@etsi.org).
Association à but non lucratif enregistrée à la<br/>
Sous-préfecture de Grasse (06) N° w061004871<br/>
</div>
<br/>
@@ -88,7 +86,6 @@ All rights reserved.<br />
# Contents
# Intellectual Property Rights
## Essential patents
@@ -97,14 +94,12 @@ IPRs essential or potentially essential to normative deliverables may have been
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.
## Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
**DECT™** , **PLUGTESTS™** , **UMTS™** and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. **3GPP™** , **LTE™** and **5G ™** logo are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. **oneM2M™** logo is a trademark of ETSI registered for the benefit of its Members and of the oneM2M Partners. **GSM**® and the GSM logo are trademarks registered and owned by the GSM Association.
# Foreword
> DRAFT FOREWORD - DO NOT CONSIDER THE CONTENT
@@ -132,7 +127,6 @@ The Technical Body may propose different dates to the default ones (3, 6, 18). T
The Technical Body should advise the ETSI Secretariat if the above default national transposition dates are inappropriate for the particular standard.
# Modal verbs terminology
In the present document "**shall** ", "**shall not** ", "**should** ", "**should not** ", "**may** ", "**need not** ", "**will** ", "**will not** ", "**can** " and "**cannot** are to be interpreted as described in clause 3.2 of the [ETSI Drafting Rules](https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules)(Verbal forms for the expression of provisions).
@@ -189,7 +183,6 @@ The following referenced documents are necessary for the application of the pres
References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.
@@ -364,9 +357,9 @@ There can be multple devices in the same network, and the NMS provides supportin
## 4.5 Security levels
> List the security levels and the use cases that correspond to them.
The security level requirements reflects the intented deployment of the NMS.
The functionality requirements are cumulative.
High risk deployment shall implement the lower risk functionalities.
> The security level requirements reflects the intented deployment of the NMS.
> The functionality requirements are cumulative.
> High risk deployment shall implement the lower risk functionalities.
@@ -435,16 +428,15 @@ The technical requirements of the present document apply under the environmental
The following security functionalities are handled by other systems:
* Secure update of firmware and/or device driver
***Identity management systems** that provide mechanisms for authentication or authorisation and that may also provide mechanisms for the lifecycle management of identity credentials
***Virtual Private Network** that provide access to a restricted-use logical computer network that is constructed from the system resources of a physical or virtual network
***Security information and event management systems** that collect data from multiple sources, analyse and correlate that data and present it as actionable information for security-related purposes unless it is considered to be integral part of the NMS product features
***Physical and virtual network interfaces**
***Operating systems** that provide an abstract interface of the underlying hardware and control the execution of software
***Routers, modems and switches** that establish and control the flow of data between different networks
<mark> Should this be in: * Provision of cryptographic keys? Is a generic NMS provisioning cryptographic keys to the managed devices?</mark>
- Secure update of firmware and/or device driver
-**Identity management systems** that provide mechanisms for authentication or authorisation and that may also provide mechanisms for the lifecycle management of identity credentials
-**Virtual Private Network** that provide access to a restricted-use logical computer network that is constructed from the system resources of a physical or virtual network
-**Security information and event management systems** that collect data from multiple sources, analyse and correlate that data and present it as actionable information for security-related purposes unless it is considered to be integral part of the NMS product features
-**Physical and virtual network interfaces**
-**Operating systems** that provide an abstract interface of the underlying hardware and control the execution of software
-**Routers, modems and switches** that establish and control the flow of data between different networks
<mark> Should this be in: \* Provision of cryptographic keys? Is a generic NMS provisioning cryptographic keys to the managed devices?</mark>
## 4.10 Support period
@@ -589,7 +581,6 @@ The annex shall have a table for a clear indication of correspondence between no
**It should be evaluated - on the basis of the legal requirements supported and other information given in a harmonised standard - how detailed correspondence can be indicated between the normative elements of the harmonised standard and the legal requirements aimed to be covered. However, where this correspondence is expressed in too general terms, it could lead to a situation where the Commission cannot assess whether the Harmonised Standard satisfies the requirements, which it aims to cover, and subsequently publication of its references in the OJEU according to Article 10(6) of the Regulation is significantly delayed or is not possible at all.**
> **EXAMPLE for a table:**
**Table A.1: Relationship between the present document and<br />the requirements of EU Regulation 2024/2847**<aname="table_A.1"></a>
