IoT Security as Revenue: Beyond Compliance Checklists
summary
Argues that security as revenue is a business requirement: investors and boards withhold capital unless products prove they generate value through risk management, not just checklists. Shows why compliance alone fails, distinguishes criminal/civil/contractual liability, and warns that formal proofs (multi‑billion efforts) missed hardware and real attacker routes. Uses a concrete example of a poisoning attack against a machine learning algorithm on sensors/cars and frames success as resilience = justifiable enduring confidence rather than passing standards.
AI-written summary · about
chapters (8)
- 0:00Security as revenue driver
- 1:13Undervaluing security roles
- 2:39Beyond compliance checklists
- 4:02Complex systems and business conflicts
- 5:47Security for business value
- 6:50Legal responsibilities beyond compliance
- 8:13Security metrics vs board priorities
- 9:17IoT security challenges
related talks
13mMaking best in class security ubiquitous
27mThe business case for security
25mSecuring the Internet of Things - An analyst's view on the market
26mIoT Security Foundation Chairman's Address
42mThe Security We Need: Designing Usable IoT Security
31m20/20 Security Vision: Managing Digital Risk in the Era of IoT
27mEnterprise IoT Security Compliance: Navigating the Cyber Resilience Act
54mSecurity in IoT, More an Attitude Issue than a Technical Challenge