Workshop Description
For mining IT/OT managers, communications engineers, and remote operations leads. Covers PQC migration for VSAT satellite links, underground mesh networks, drone telemetry, and IoT sensor networks. Addresses ML-KEM key size versus bandwidth constraints, NIST FIPS 203/204/205/206 algorithm selection for constrained mining devices, and vendor readiness assessment.
Remote mining operations depend on communications infrastructure that is simultaneously critical and constrained. VSAT satellite links provide the primary data path for sites hundreds of kilometres from terrestrial fibre. Underground operations rely on leaky feeder, WiFi mesh, or private LTE/5G networks with limited bandwidth and intermittent connectivity. Surface operations coordinate autonomous haul trucks, drone surveys, and thousands of IoT sensors across open-pit footprints spanning several square kilometres. Every one of these communication links uses cryptographic protocols (TLS, IPsec, DTLS) with key exchange and authentication algorithms that quantum computers will break. The challenge specific to mining is that PQC algorithms are larger than their classical predecessors. ML-KEM-768 produces 1,568-byte ciphertexts. ML-DSA-65 signatures are 3,309 bytes. On a 128 kbps VSAT return channel or a 127-byte LoRaWAN MTU, these sizes have operational consequences. This workshop maps the PQC overhead against your actual link budgets, identifies which communication paths need architectural changes, and builds a migration sequence that maintains operational continuity.
What participants cover
- VSAT and satellite link encryption: PQC impact on DVB-S2X, LEO mesh (Starlink/OneWeb), and HF/VHF radio fallback links with bandwidth and latency analysis
- Underground and surface mesh networks: PQC for leaky feeder, WiFi 6/6E, private LTE/5G in tunnels, autonomous haul truck fleet management, and drone telemetry
- ML-KEM key size versus mining MTU: fragmentation strategies for 1,568-byte ciphertexts on LoRaWAN (127 bytes), underground mesh, and constrained IoT sensor networks
- NIST FIPS algorithm selection: ML-KEM-512/768/1024 tiering by link capability, ML-DSA versus SLH-DSA for device CPU constraints, FN-DSA for compact drone telemetry signatures
- Vendor readiness assessment: VSAT providers (Hughes, Viasat, SES), mining mesh vendors (Rajant, Newtrax/Sandvik), and IoT platform PQC migration timelines
- Procurement strategy: incorporating NIST FIPS 203/204/205 requirements into mining communications RFPs and lifecycle costing for PQC-capable infrastructure