fixup! Add use case 4.6.2.3: Server and host fleet lifecycle management

The NMS can be deployed as a single instance for a small estate, or scaled with intermediate proxies or hubs that cache content and relay commands to hosts in remote sites or segmented networks, following the [distributed deployment](#421-network-architecture) pattern.

The upstream software content source — and, depending on the product, subscription, licensing, or usage reporting — is commonly external to the product and is then a [remote data processing solution](#44-distribution-of-security-functions), to which the provisions of [Annex R](#annex-r-normative-additional-provisions-for-products-relying-on-remote-data-processing-solutions-rdps) apply.

Because the NMS holds privileged, often root-equivalent, control over the installed software and configuration of every managed host, a compromise of the NMS or of its content delivery path has a blast radius spanning the entire fleet, comparable to a supply-chain compromise.

Because the NMS holds privileged, often root-equivalent, control over the installed software and configuration of every managed host, a compromise of the NMS or of its content delivery path has an impact radius potentially spanning the entire fleet.

The integrity and authenticity of delivered content and configuration, the strength of host enrolment and authentication, and the isolation of the management plane are therefore the dominant risk factors in this use case.

The applicable risk tier follows the risk factors of the [security analysis](#annex-b-informative-security-analysis), in particular the criticality of the managed hosts and the complexity of the managed elements; the criticality scales with the role of the managed hosts, ranging from a small office estate to servers underpinning critical infrastructure.

> NOTE: This use case concerns the system that manages the hosts. The delivery and lifecycle management of host software is a function of the NMS and is in scope; the intrinsic security of the operating systems running on the managed hosts is addressed by ETSI EN 304 626 [\[i.5\]](#_ref_i.5).

> NOTE: This use case concerns the system that manages the hosts. The intrinsic security of the operating systems running on the managed hosts is addressed by ETSI EN 304 626 [\[i.5\]](#_ref_i.5).

#### 4.6.3 Alternative deployments