University:
Boston University
Course:
SAR HP 151 | Introduction to Health Professions
Academic year:

2020
Views:

208

Pages:

26
Author:

bulhossiq8pf

Intro to embedded security: implications for connected healthcare products and services Agenda ▷ Intro to embedded security ▷ Healthcare + embedded ▷ (brief) review of life-sustaining medical device vulnerabilities ▷ Regs? Best practices? What’s next? Embedded - an example Built in security! ○ Network key: encryption key unique to every network ○ Global link key: pre-configured key for all nodes, used to join network Why embedded? Obscurity to scale… quickly Why embedded? Obscurity to scale… quickly Wright’s Law “Security won’t get better until tools for practical exploration of the attack surface are made available” -- Joshua Wright (ZigBee Security Expert), 2011 Embedded Overview Embedded is in the spotlight due to rapid shifts in capability The good old days: ○ Bare metal ○ Assembly ○ 8051 ○ Dishwashers Embedded devices are advancing but still small footprint + low power Power: Duty cycling, not “always on” Deployment: Wireless, easy config, backward compatibility Updates: One-time programming, dependent on supply chain Embedded is in the spotlight due to rapid shifts in capability Today’s reality: ○ GHz processors; GB memory, persistent storage ○ 2G, 3G, LTE, IP, custom RF, Zigbee, Z-wave, LoRa Exploits are becoming more and more common Local (external port) Home Routers / modems • Root serial console - modify speed value Cell Phones • Android phones via audio jack • Motorola SMS via audio jack Remote (via cell) Jeep UConnect Flaw: • 1.4 million cars recalled • Sprint network, UDP port 6667 open 2015: BMW Door Unlocks • 2.2 million cars, but fixed OTA 2010: 100 Vehicles ‘Bricked’ How we look at embedded We tend to work at the lowest and least explored levels of the OSI model External ports often provide access manufacturers don’t advertise Black box RF analysis yields information on (lack of) cryptographic implementations PCB Reverse Engineering can help with low-level logic and power exploitation A simple logic analyzer can often decode intra-chip communication Unprotected Headers + Debug Ports are ubiquitous Unprotected Headers + Debug Ports are ubiquitous Widely unprotected persistent storage leaks secrets At the lowest levels of the OSI model we find common easy exploits Full USB + network stacks Storage in the clear w/o secure boot Jamming + poorly encrypted wireless connections Unencrypted communication channels (hardware) Unlocked serial console, bootloader console, JTAG Where does this leave us with embedded devices? 1. Obscurity doesn’t cut it anymore 2. The tools are still lacking 3. Patch and device management is almost non-existent 4. People are catching on (good and bad)