Commit e3ccfc6a authored by Santeri Toikka's avatar Santeri Toikka
Browse files

Started with OpsEnv definition

parent 884067ca
Loading
Loading
Loading
Loading
+14 −0
Original line number Diff line number Diff line
@@ -398,6 +398,20 @@ Following list of essential functions keep the NMS self-secure and correct funct

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.

>Distributed element design
>
>Editor's Note: Unclear and to discuss: what is distributed and where? Are elements also outside a defined operational environment? If so then further security requirements apply.

>Isolated management system design
>
>Editor's Note: What is an isolated design? That needs a clarification. Does that mean a generalized serial NMS product, procured as standalone?

When management system is deployed on shared resources, the resource hierarchy, dependencies and control boundaries becomes a points of interest.

>Pocket deployments with high independency
>
>Editor's Note: What is a pocket deployment? That needs a clarification. Does that mean deployment in a from public networks isolated closed network?

## 4.9 Users

Human users of the system are natural persons, trained and qualified at NMS administrators, and authorised to manage the NMS and the connected managed elements. Administrators typically access the system through a HTTPS GUI, console, or by VPN connection.