These totals come from the supplied platform screenshot. An asset without an observed link is a gap in this record; it does not establish that the asset is silent or offline.
A CLEARER VIEW OF THE EVIDENCE
Follow a path. Ask the right question.
Illustrative layout · selected paths only Choose a node or the amber path for details.
Illustrative zones & conduits
Illustrative assetSelected relationshipReview exampleZone boundaries are illustrative.
Cross-zone flow — review
Illustrative Modbus PLC → firewall path. Confirm the actual zone assignments, permitted conduit and business purpose before treating any path as a finding.
This simplified map is a presentation illustration. It shows four selected cross-zone links, not all 42 recorded links. Protocol groups alone do not establish security zones. The amber path is an example review prompt, not a platform-generated alert or a verified segmentation issue.
FROM VISIBILITY TO REVIEW
The connection is the starting point.
A relationship map helps your engineering team ask whether the recorded communication has an owner, a clear operational purpose and an agreed place in the architecture.
Validate device identity and capture coverage.
Confirm zones, conduits and permitted traffic.
Review consequences before changing production systems.
“Unclassified assets” means a protocol was not identified in the available evidence. Device identity, current traffic and online status still require validation.
View the original recorded mapOriginal supplied screenshot. Open at full size to inspect the recorded protocol groups and totals.
