Workshop Description
For OT security leads, plant managers, and IT/OT integration teams. Covers the specific cryptographic exposure of PLCs, SCADA, DCS, and IIoT devices, and how to sequence a PQC migration without disrupting production continuity. Includes a working cryptographic inventory methodology for industrial environments using the Purdue model as the organising framework.
Industrial control systems present unique PQC migration challenges. PLCs running Modbus/TCP have no native encryption and rely on network segmentation; OPC UA uses X.509 certificates with RSA/ECDSA that require algorithm replacement; PROFINET uses challenge-response authentication vulnerable to quantum attack; and IIoT edge devices often run on 8-bit or 32-bit MCUs with constrained RAM that cannot accommodate ML-KEM key sizes without firmware redesign. The NIST PQC standards (FIPS 203 ML-KEM, FIPS 204 ML-DSA, FIPS 205 SLH-DSA) are finalised, but IEC 62443 has not yet incorporated PQC requirements into its security levels. This creates a gap: organisations that wait for IEC 62443 updates risk falling behind on migration timelines, while those that move early must make algorithm choices without full standards alignment. This workshop addresses both paths with a pragmatic, Purdue-model-based migration sequencing approach that prioritises by exposure level and operational impact.
What participants cover
- ICS cryptographic exposure by Purdue level: which protocols at each level (Level 0 sensors through Level 4 enterprise) use vulnerable RSA/ECDSA/DH and how harvest-now-decrypt-later applies to each
- FIPS 203/204/205 algorithm selection for OT: ML-KEM key sizes versus constrained device RAM, ML-DSA signature sizes versus OPC UA certificate chains, SLH-DSA for long-lifetime firmware signing
- Protocol-specific migration: OPC UA certificate replacement, PROFINET authentication upgrade, Modbus/TCP encryption overlay options, MQTT/TLS 1.3 with PQC cipher suites for IIoT
- Purdue-model migration sequencing: starting at Level 3.5 (DMZ) and Level 4 (enterprise), then Level 3 (site operations), deferring Level 0-1 (process control) until vendor firmware supports PQC
- Hybrid deployment strategies: running classical and PQC algorithms in parallel during transition to maintain interoperability with legacy equipment and supply chain partners
- IEC 62443 zone and conduit model applied to PQC: mapping cryptographic boundaries to security zones and defining PQC requirements per conduit