
Who Can End a Supplier Session When the Line Is Down?
A production line is stopped, and a supplier needs an engineering connection to diagnose the fault. In this explicitly hypothetical CUP scenario, the same legacy session can also download a PLC program. The question is who can constrain and end its authority when recovery is urgent.
We trace the path from supplier identity through remote access, a plant-controlled workstation, the engineering tool and the controller. A broker disconnect, account disable and controller-side termination do not necessarily have the same effect; none can undo a program already downloaded. MFA, recording and a jump host add control points, but do not make a change-capable tool read-only.
We discuss named access, expiry, local supervision, alternative routes, surviving sessions and a bounded non-production acceptance exercise. This is an engineering analysis, not a reported incident, product vulnerability or completed experiment. NIST SP 800-82 Rev. 3 provides context; the revocation sequence and acceptance checks are CUP recommendations.
Read the companion analysis: https://cybersecurityunderpressure.com/analysis-supplier-session-revocation-legacy-ot
Altri episodi di "Cybersecurity Under Pressure. Real Attacks, Real Lessons"



Non perdere nemmeno un episodio di “Cybersecurity Under Pressure. Real Attacks, Real Lessons”. Iscriviti all'app gratuita GetPodcast.








