The Security We Need: Designing Usable IoT Security
summary
Argues that usable IoT security needs concrete mechanisms not slogans: a smart home often has 40 devices so secure defaults and zero-touch provisioning (device keys baked in by manufacturer) are necessary to scale; runtime defenses require monitor CPU and network anomalies and gateways to reduce battery costs; operational control means being able to revoke device certificate to cut compromised devices off; warns users routinely disable slow updates so update performance and preconfigured security buckets must be measured and designed.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:42A little About Me
- 1:35Learning Objectives
- 9:02Security Intricacies Don't Make Sense To Users - Type 1
- 11:49Security is Not Interesting to the Regular User
- 14:20Barriers to Necessary Workflow
- 15:40Differing Views of Security
- 16:54Put on your "User" Hat
- 18:25P2: Secure Defaults Only ctd.
- 19:55Display Targeted Risk Information for Security Config
- 20:56Assist your User with Pre-configured Security Levels
- 21:55Design to Scale (Zero-Touch Device Provisioning Example)
- 23:43Do Not Allow Passive or Transitive Authorization
- 24:06Implement Runtime Anomaly Detection & Device Health Checks
- 25:25Ensure lot Admins Can Seamlessly Revoke Previously Granted Authority Ctd.
- 26:23Just Keep Secrets Secret
- 27:02Monitor Circumvention of Security Controls
- 28:46In closing, Aim for Clarity & Simplicity
- 30:47My Social Networking
related talks
31mSecuring the Internet of Things
54mSecurity in IoT, More an Attitude Issue than a Technical Challenge
28mIoT Security - it's not just the devices
25mSecuring the Internet of Things - An analyst's view on the market
37mWhy is IoT security so hard and what can we do about it?
45mBuilding Trust with UX Design: Examples from IoT and Beyond
54mSecurity in IoT: Challenges, Vulnerabilities and Countermeasures
30mThe Seven Properties of Highly Secure IoT Devices