From Wild West to Secure Business: Understanding Data and Standards in OT
summary
Claim that security need not add extra cost and must be engineered in from the start, with concrete rules: NISv2 and the EU Cyber Resilience Act widen scope, vendors must meet IEC 62443-4-1 and especially 62443-4-2 (no known vulnerabilities at release). Cites 36 months to comply from 17 Oct, 93 compliance enhancements, most customers (95%) misqualify data, legacy PLCs 20–48 years old, 4–6 ms I/O refresh, safety reactions <50 ms, 128-bit minimum encryption, and a £4.8m outage caused by using one firewall instead of eleven.
AI-written summary · about
chapters (8)
- 0:00OT security challenges
- 2:36Digitalization and Industry 4.0
- 7:59NIS2 and CRA compliance
- 11:34IEC 62443 and supply chain
- 13:43Network design and protocols
- 16:56Security levels and asset protection
- 19:23Role of standards in OT
- 20:28Summary
related talks
46mThe Perfect Storm, What NIS2 and CRA Mean for Your IT Security Strategy
27mIoT: What will security standards and certification look like ten years from now?
59mMerging Security and Compliance: Perspectives on Emerging Regulations and Best Practices
52mPanel: Industrial Systems In The Crosshairs: What It Really Takes To Defend OT
57mDon’t Forget the Little Guy: Vulnerability Management in Operational Technology
48mYou Too Can Secure OT
05mIndustry Responses to the European Directive on Security of Network and Information
27mEnterprise IoT Security Compliance: Navigating the Cyber Resilience Act