Why is SCADA Security an Uphill Battle?
summary
Explains why control networks keep failing by naming actual weak points: 66% in SCADA master (HMI/DCS/web apps), real protocol flaws in Modbus DNP3 and other stacks, and concrete device issues like exposed debug ports and hardcoded passwords. Shows a released open-source scanner, SCADA Scan, with usage caveats (never run on production) and gives real counts of recent CVEs plus patching and network-segmentation outcomes so viewers know what tools and fixes were tested and which still fail.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:22Agenda
- 7:462009 - 2013 SCADA Vulnerabilities
- 10:13Components
- 11:40Acquisition Convert parameters like light, temperature, pressure or flow to analog signals
- 12:45Conversion
- 15:32Presentation & Control
- 16:342013 Vulnerabilities by category
- 18:42Emerson ROC800 Vulnerabilities
- 21:53Siemens CP 1604 / 1616 Interface Card Vulnerability
- 23:24Communication
- 27:50ModBus Vulnerabilities
- 28:31Security Analysis of SCADA protocols
- 30:54SSH, FTP, TFTP, IGMP, SNMP
- 37:13Real world issues
- 44:05System Wide Challenges
- 44:39Proposals
- 45:58Scada Scan
related talks
30mPractical Attack Vectors and Their Ideal Defensive Strategies for ICS & SCADA
16mHoney, I Hacked The SCADA! : Industrial CONTROLLED Systems!
12mQuick Look: SCADA Security: How Do I Know If I’ve Already Been Owned?
51mIndustrial Control Systems : Pentesting PLCs 101 (Part 2/2)
58mIndustrial Control Systems : Pentesting PLCs 101 (Part 1/2)
19mIoT Security Exposed: From PLC Flaws to the Imperative of SBOM
58mWhy Control System Cyber-Security Sucks…
52mPanel: Industrial Systems In The Crosshairs: What It Really Takes To Defend OT