Added prortected assets definitions

> Explain the overall architecture and relationship among the parts of the products. Use diagrams if that is helpful.

Network management system is often deployed in a star pattern, where all command and control functionality is focused on a centralized set of services, that are providing all required functionality.

Depending on the connected element design and degree of autonomy, the element can often operate fully without constant connectivity to a NMS. In larger network deployments, the connectivity can start to erode over time, if there is no adjustments made to the routing or other operation parameters.

![Product overview and architecture](./media/2025-07-30_system.drawio.png)

Network Management System is operated by a user, or by a program interfacing an API.

The main functionality of a NMS is to interface and manage Routers and Modems.

More about assets in [Annex C.1 Assets](#c1-assets) and [Annex C.2 Data](#c11-data)

## 4.4 Use cases

> Create a list of representative use cases, each one representing a different threat profile. If the threat profile is the same for two use cases, then it is basically the same use case for the purposes of the present document. Use cases should include both intended and reasonably foreseeable use/misuse. Use cases don't include industrial operations, automotive, transport, marine, airplane, medical, military, national security, etc.

## C.1 Assets

-   access to the management interface

NMS protects systems that are relying on network connectivity to perform its daily operations.

**Business continuity**

-   market reach information

-   Business-critical processes

-   manufacturing

-   finance

-   healthcare

-   Compliance evidence if form of logs and reports

**Incident response capability**

-   ability to detect, diagnose, and remediate outages

**Network inventory and topology**

-   network inventory

-   network topology

-   market reach information

-   network segmentation policies

-   firewall rules

**Connected devices**

-   access to the management interface

-   connected devices updates, patches

-   keys can be generated or imported through the keymanagement modules

-   CORBA access, grcp

-

-   keys can be generated or imported through the keymanagement modules

### C.1.1 Data

> What data is stored on the product?

The stored data depends on what functions the NMS has available and what the intend use is.

The stored data can be, but is not limited to:

-   Device monitoring data

-   Credentials

<mark>FIXME more kinds of data</mark>

-   Backups

-   Performance logs

-   Syslogs for forensic investigations

-   Sensitive monitoring data

    -   NetFlow information

    -   Packet captures

    -   Protocol analysis information

The manufacturer shall follow the CRAs pricibles of implementing high level of cybersecurity of products [CRA Resictal 11] <a href="#_ref_i.1">[i.1]</a>. The protection duty extends to third party integrations regardless of the market status of the component. [CRA Resictal 34] <a href="#_ref_i.1">[i.1]</a>.

### C.1.2 Product functions