Modern manufacturing platforms connect systems that historically lived in different trust zones: PLCs, edge gateways, MES, cloud services, engineering workstations and AI applications. The architecture should assume those connections are valuable and therefore worthy of explicit security design.
Start with zones and conduits
IEC 62443 provides a useful way to reason about industrial security by grouping assets with similar security requirements and controlling communication paths between them.
For a connected MES architecture, that can mean separating control networks, edge integration, application services, enterprise interfaces and administrative access rather than allowing broad lateral connectivity.
Give services identities too
Human role-based access is only part of the problem. Edge agents, APIs, brokers and integration jobs also need authenticated identities with only the permissions required for their function.
Shared credentials and unrestricted service accounts make investigation difficult and expand the impact of a compromised component.
Make write paths exceptional
Read-only telemetry and transactional write actions should not share the same trust assumptions. A system that reads machine state may not need authority to change set points or production status.
Where write-back is required, use narrow APIs, explicit authorization, audit logging and approval workflows appropriate to the operational consequence.
- Network segmentation
- Mutual authentication where supported
- Least-privilege service accounts
- Patch and update governance
- Remote-access controls
- Centralized audit and security monitoring
Security must survive operations
A design that is secure only when every connection is online and every certificate is fresh will eventually create workarounds. Certificate renewal, offline recovery, backup, break-glass access and vendor support all need operational procedures.
Delfers OT Engineering treats those lifecycle questions as part of architecture so connected platforms remain supportable after go-live.
Standards and primary sources used for context.
These links provide technical context. Their inclusion does not claim product certification or compliance unless explicitly stated elsewhere.
