“Our network drawings don't match what's actually connected.”
Architecture documentation can be reviewed to identify unclear boundaries, excessive connectivity, weak segmentation assumptions and important dependencies — before an incident reveals them.
Segmentation determines how far an incident can spread.
Shared services can quietly connect zones that should be separate.
An accurate model makes network changes safer to plan.
Access paths are often the least documented part of the design.
A sequence that can be adapted to your environment and scope.
Collect drawings, firewall exports and system descriptions.
Draw zones, boundaries and permitted flows as found.
Test each segmentation assumption against the evidence.
Record excess connectivity and unclear boundaries.
Define a target design and migration steps.
Drawings show the control network separated from the business network by a firewall. The firewall export shows broad rules added for a historian project, and a domain controller shared by both sides. The review recommends moving the historian interface to a DMZ and separating identity services.
A belief that two parts of the network cannot communicate, or only in limited ways. Reviews check whether firewall rules, shared services and remote access paths actually support it.
From the blog
Regulation7 min
National NIS2 laws are now being enforced. Here is what energy, water, transport and manufacturing operators should be able to show for their OT environments.
Read the article
Regulation6 min
Manufacturers must now report actively exploited vulnerabilities and severe incidents. Asset owners should expect more advisories, and suppliers need a working process.
Read the article
Architecture8 min
Segmentation diagrams often look perfect and behave very differently. A practical method for zones and conduits that match how your site really works.
Read the articleDescribe where you are today and we'll suggest a practical way forward.