Zones, not
luck.
We split production networks into zones and define every crossing explicitly. An infected office PC cannot reach a controller, and remote maintenance only runs through a controlled access point.
Six levels, clearly separated.
Click a building block on the right. The diagram shows where it sits in the architecture.
Where segmentation stops an attack.
A typical sequence seen in many incidents. Keep scrolling: without separation the attack runs through, with a zone model it ends at the firewall.
Phishing email
An employee opens a booby-trapped attachment in the office network.
Office PC compromised
The attacker harvests credentials and looks for ways into the plant.
IT/OT firewall
Default deny: there is no permitted connection from the office to the control level. Our sensor reports the attempt.
SCADA / HMI
Without segmentation the HMI would be directly reachable.
PLC manipulated
Without segmentation: setpoints change, the line stops.
Standards are our toolkit.
For many companies NIS2 and the Cyber Resilience Act are now mandatory. We align architecture, tools and documentation with them so that audits become routine.
Zones, conduits and security levels for automation systems. For asset owners, integrators and vendors.
Information security management system. We deliver the technical controls and evidence.
The IND.1 and IND.2 modules for operational technology form the basis of our checklists.
Risk management, reporting duties and supply chain. Part of the German BSI Act since December 2025.
Reporting duties for manufacturers since 11 September 2026, full application from December 2027.
Data-minimising architecture, processing in Germany and clear deletion rules for log data.