Navigating Third-Party Risk in OT Environments
summary
Claims that remote access for real‑time troubleshooting creates the biggest OT exposure, contracts often strip owners of control, and you need keystroke logging and replayable sessions for non‑repudiation. Practical fixes: force east‑west traffic through taps, add segmentation zones and DMZ historians, deploy Claroty/Dragos/Nozomi class visibility, or leverage IT remote‑access platforms with RBAC and MFA. Surprising data points: OT gear runs 15–40 years, visibility rollouts can take four years, a $3M firewall ask prevents an $80M outage; insist on vendor SBOMs and vulnerability notification.
AI-written summary · about
chapters (9)
- 0:00Operational technology intro
- 3:31Third-party risk in OT
- 7:52Network segmentation role
- 15:39Controlling vendor remote access
- 20:40Security wrappers for legacy OT
- 26:06Identity and access management in OT
- 29:56Patch and vulnerability challenges
- 35:16Immediate steps to reduce risk
- 36:26Closing thoughts and workforce
related talks
48mYou Too Can Secure OT
51mPreparing for and Defending OT Systems from Ransomware
40mZero Trust: Regaining Trust in a Remote Work World
52mPanel: Industrial Systems In The Crosshairs: What It Really Takes To Defend OT
53mCXO Panel: OT & IoT Risk Management Strategy For CISOs
11mKeynote
47mField Guide to Building an Operational Technology Cybersecurity Capability
57mDon’t Forget the Little Guy: Vulnerability Management in Operational Technology