Connectivity services answer an availability and performance question: is the network up, is it fast enough, does it fail over cleanly when a circuit drops. MPLS design, SD-WAN deployment, load balancing, and bandwidth optimisation all sit here. A well-run connectivity engagement produces a network that works reliably. It says nothing, by itself, about whether that network is segmented, monitored, or defensible against someone already inside it.

NCA ECC-2:2024's Cybersecurity Defence domain names system and network security as an explicit control area, separate from connectivity or infrastructure uptime. This covers segmentation (critical systems isolated onto their own network zones rather than reachable from anywhere), firewall management (rule sets reviewed against real traffic rather than left as originally configured), and intrusion detection and prevention (tuned to catch anomalous activity rather than running on default thresholds that generate noise nobody reads).

A network can be fast, reliable, and fully redundant, everything a connectivity engagement promises, and still be a flat network where a single compromised device can reach the finance server, the HR system, and everything else without crossing a control boundary. This is precisely the scenario NCA ECC's network security control area exists to catch, and it is invisible to a connectivity-focused review because connectivity and security are answering different questions.

Segmentation decisions get made during network design, which is why connectivity and network security work often happen close together even though they are distinct deliverables. A well-designed SD-WAN deployment can build segmentation in from the start; a retrofit onto an existing flat network is more work but is the more common starting point for an organisation that built connectivity first and is now closing the security gap.