Skip to content
Sign in
Artwork for Cybersecurity Under Pressure. Real Attacks, Real Lessons
Cybersecurity Under Pressure. Real Attacks, Real Lessons · October 16 · 40 min

Why Clean Code Causes Industrial Disasters

Can code be easier to read and still make an industrial process less safe? This episode examines why software refactoring in OT must preserve more than functional output: scan-cycle timing, interlocks, failure behaviour, operator expectations and the evidence behind a validated control baseline. We discuss how engineering teams can review changes, test them against the physical process and control deployment without treating cleaner code as proof of safer operation. Related CUP episodes: When Compiling Becomes the Payload: The OpenPLC Supply Chain Trap When the PLC Project Baseline Becomes a Security Boundary When AI Makes PLC Attacks Easier but Process Authority Stays the Real Risk When a Critical PLC Vulnerability Meets Brownfield Reality

0:00-40:11
Play in

transcript

No transcript — this publisher did not publish one.

show notes

Can code be easier to read and still make an industrial process less safe? This episode examines why software refactoring in OT must preserve more than functional output: scan-cycle timing, interlocks, failure behaviour, operator expectations and the evidence behind a validated control baseline. We discuss how engineering teams can review changes, test them against the physical process and control deployment without treating cleaner code as proof of safer operation.

Related CUP episodes:

  1. When Compiling Becomes the Payload: The OpenPLC Supply Chain Trap
  2. When the PLC Project Baseline Becomes a Security Boundary
  3. When AI Makes PLC Attacks Easier but Process Authority Stays the Real Risk
  4. When a Critical PLC Vulnerability Meets Brownfield Reality
links4

more episodes

All episodes