A connectivity matrix is a table that shows which systems, networks or hosts are allowed to communicate with each other. It is used in network design and security review to map permitted paths, ports and protocols, and to spot unexpected lateral connectivity or missing segmentation.
What a connectivity matrix shows
A connectivity matrix is a compact way to show permitted communication relationships between systems, networks, or hosts. It turns an otherwise hidden set of firewall rules, routing allowances, and trust assumptions into a readable map, which helps teams see where traffic is intentionally allowed and where policy may be inconsistent or missing.
Used well, it acts as a design and review tool rather than a runtime control. It does not enforce segmentation by itself, but it reveals whether the intended network boundaries are actually reflected in the approved paths, ports, and protocols.
Why it matters in network security design
The main value of a connectivity matrix is that it makes lateral reachability visible. In segmented environments, even one unexpected allowance can create a path from a low-trust zone to a more sensitive system, so the matrix becomes a practical way to compare intended architecture with actual communication permissions.
It is especially useful during architecture reviews, cloud landing zone design, mergers, and environment changes, when trust relationships tend to accumulate faster than they are documented. By listing who can talk to whom, the matrix exposes hidden dependencies that may otherwise survive long after the original business need has disappeared.
What belongs in the matrix
A useful matrix normally captures source and destination, direction of traffic, and the protocol or port used. Many teams also annotate the business purpose, data sensitivity, environment boundary, and ownership so reviewers can tell whether an allowed path is justified or simply inherited from an older design.
The stronger the documentation around each row and column, the more useful the matrix becomes for review and change control. Without that context, it can become a static inventory of connections that is hard to validate and easy to ignore.
- Systems, subnets, or hosts that communicate across trust boundaries.
- Approved ports, protocols, and directional allowances.
- Segmentation intent, such as user to server, server to database, or management plane paths.
- Notes on exceptions, temporary access, and compensating controls.
How teams use it during review and change
Security and infrastructure teams use the matrix to check whether a new application, integration, or vendor connection fits the approved design. It is also a useful starting point for validating firewall policy, micro-segmentation boundaries, and change requests that affect reachability between sensitive zones.
When the matrix is current, reviewers can spot unnecessary paths before they are deployed and identify missing paths that would break expected service flows. That makes it useful both for reducing attack surface and for avoiding accidental outages caused by over-restrictive controls.
Risk and Threat Considerations
A stale or incomplete connectivity matrix can hide exposure that attackers later exploit, especially where one permitted path gives access to multiple downstream systems. The same visibility gap can also lead to weak segmentation, which increases the chance of lateral movement after an initial compromise.
Failure mechanism: Unreviewed exceptions, undocumented dependencies, or permissive network rules create reachability that the organisation no longer understands, so the environment becomes harder to defend and easier to traverse.
Impact: Attackers may move between hosts or environments more easily, sensitive systems may be exposed to unnecessary communication paths, and incident containment becomes slower because defenders cannot rely on the documented network model.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | SC-7 — Boundary Protection | Defines network boundary and segmentation controls directly reflected in the matrix |
| AC-4 — Information Flow Enforcement | Covers controlling which systems may exchange traffic and under what conditions | |
| CM-2 — Baseline Configuration | A connectivity matrix supports the approved network baseline and exposes drift | |
| Recommendation — Map each permitted path to SC-7 and remove unjustified routes that weaken boundary enforcement. Use AC-4 to enforce approved information flows instead of relying on informal network assumptions. Maintain the matrix as part of the approved baseline and review it after every network change. | ||
| NIST CSF 2.0 | PR.AA-05 — Least Privilege | Connectivity matrices help limit system-to-system access to only necessary paths |
| PR.PS-01 — Configuration Management | Matrix maintenance is part of keeping network configurations aligned with intended design | |
| Recommendation — Use least-privilege network paths and remove any communication route not needed for the service. Track connectivity approvals as configuration items and revalidate them during change management. | ||
Practitioner Guidance
Why practitioners should care: Treat the matrix as a living control artifact, not a one-time diagram. If it is not updated alongside firewall changes, cloud networking changes, or application onboarding, it quickly stops reflecting the real trust model.
What to watch for: Pay attention to entries that exist only because of old projects, temporary exceptions that became permanent, and broad network allowances that are not tied to a clearly stated business need. Those are often the first places where segmentation drift appears.
Practitioner takeaway: Keep the matrix close to the change process so every new path is documented, justified, and reviewable before it becomes part of the accepted network posture.
Related resources from NHI Mgmt Group
- How should organisations build a segregation of duties matrix for modern IAM programs?
- What breaks when partner connectivity is modernised without access governance?
- How do you know if an AP SoD matrix is actually working?
- How should security teams build a segregation of duties matrix that reflects real access?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org