BRKARC-2032 – Designing for Secure Convergence of Enterprise and PCNs
BRKARC-2032 – Designing for Secure Convergence of Enterprise and Process Control Networks
Presenter: Chuck Stickney, Cisco SE
Handful of OT folks in the room; majority IT.
Convergence Benefits
- Simplification (common protocols)
- Reduced Cost
- Pervasive enablement of features and services
PCN vs Enterprise
- PCN: peer-to-peer, publish/subscribe model; application defines communication parameters; strict time sync
- Enterprise: three-tier architecture; session oriented; many-to-one (centralized apps)
- PCN: short, high-volume messages; localized traffic; delay/jitter sensitive; unreliable transmission; no out of order messages, no retransissions; similar to voice/video (these are problems that IT has solved for years)
- Enterprise: large messages; remote traffic; delay tolerant; reliable, connection oriented; retransmission, re-ordering
“Layer 2, Layer 3″ are not terms that OT folks understand. IT folks: speak a language your OT folks can understand.
PCN Characteristics
- Proprietary protocols (Modbus, Profibus, DeviceNet)
- Incompatibility between systems (connectors, cabling, signals) (think: Ethernet vs Token Ring)
- Industrial Ethernet: a common data link layer using standard 802.3 components (EtherNet/IP, Modbus/TCP, Profinet)
- Ethernet/IP: Rockwell; uses Common Industrial Protocol (CIP); implicit, real-time (UDP, mcast port 2222); explicit, non-time critical (tcp port 44818)
- Profinet: Siemens; IO and non-realtime; IO is Layer 2 only where app layer directly interfaces with MAC layer bypassing layers 3 – 6; non-real time Continue reading