Pacemakers and implantable cardiac defibrillators: Software radio attacks and zero-power defenses Ben Ransford ransford@cs.umass.edu U. Washington: UMass Amherst: BIDMC/ D. Halperin T. S. Heydt-Benjamin Harvard: T. Kohno S. Clark B. Defend W. H. Maisel, MD W. Morgan K. Fu http://secure-medicine.org/ Ben Ransford, IEEE Security & Privacy ’08
Neurostimulator Pharmacy on a chip Cardiac Device Prosthetic Drug pump limb Ben Ransford, IEEE Security & Privacy ’08 2 Photos: Medtronic, Hearing Loss Assoc. of WA, St. Jude Medical, Otto Bock
Neurostimulator Pharmacy on a chip Cardiac Device Prosthetic Drug pump limb Ben Ransford, IEEE Security & Privacy ’08 2 Photos: Medtronic, Hearing Loss Assoc. of WA, St. Jude Medical, Otto Bock
Why Care About IMDs? • Common devices • Sophisticated devices with radios • Perform vital functions inside people • Are they secure? Ben Ransford, IEEE Security & Privacy ’08 3
Trends in Cardiac Devices • Complex therapies • Radio interfaces • Monitoring over Internet • Algorithms for problem detection • More storage, better CPU, ... Implantable defibrillator, 2003 Ben Ransford, IEEE Security & Privacy ’08 4
An Implanted Computer ... which is wirelessly reprogrammable ... and contains personal data. 1990–2002: ~2.6 million (US) [JAMA 2006] Ben Ransford, IEEE Security & Privacy ’08 5 Photos: oldcomputers.net, Wikipedia (“Heart”)
Contributions • Study of a real implantable device • Attacks with software radio • Prototype energy harvesting defenses Ben Ransford, IEEE Security & Privacy ’08 6
The Next 20 Minutes 1. How secure is a real device? 2. Why is this non-trivial to get right? 3. Where should we go from here? Ben Ransford, IEEE Security & Privacy ’08 7
Ben Ransford, IEEE Security & Privacy ’08 #1: Analysis of a Real Device http://secure-medicine.org/ 8
We analyzed an ICD. • I mplantable C ardiac D efibrillator • Related to pacemaker • Large shock: resync heart Heart • Monitors heart waveforms Ben Ransford, IEEE Security & Privacy ’08 9
Implantation Scenario 1. Doctor sets patient info 2. Surgically implants 3. Tests defibrillation 4. Ongoing monitoring Ben Ransford, IEEE Security & Privacy ’08 10 Photos: Medtronic; Video: or-live.com
Implantation Scenario 1. Doctor sets patient info 2. Surgically implants 3. Tests defibrillation 4. Ongoing monitoring Device Programmer Ben Ransford, IEEE Security & Privacy ’08 10 Photos: Medtronic; Video: or-live.com
Implantation Scenario 1. Doctor sets patient info 2. Surgically implants 3. Tests defibrillation 4. Ongoing monitoring Ben Ransford, IEEE Security & Privacy ’08 10 Photos: Medtronic; Video: or-live.com
Implantation Scenario 1. Doctor sets patient info 2. Surgically implants 3. Tests defibrillation 4. Ongoing monitoring Home monitor Ben Ransford, IEEE Security & Privacy ’08 10 Photos: Medtronic; Video: or-live.com
Attack #1: Steal Device Programmer • Insider attack • Thief can reverse engineer, modify... • Risk: get “root” on many implants Issue: ICD’s trusted computing base is large. Ben Ransford, IEEE Security & Privacy ’08 11 Photo: Medtronic
Why Steal When You Can Build? • Software radio • GNU Radio software, $0 • USRP board, $700 • Daughterboards, antennas: $100 ~10 cm (un-optimized) Ben Ransford, IEEE Security & Privacy ’08 12
Attack #2: Eavesdrop Private Info Ben Ransford, IEEE Security & Privacy ’08 Ben Ransford, IEEE Security & Privacy ’08 13
Attack #2: Eavesdrop Private Info Diagnosis Ben Ransford, IEEE Security & Privacy ’08 Ben Ransford, IEEE Security & Privacy ’08 13
Attack #2: Eavesdrop Private Info Diagnosis Hospital Ben Ransford, IEEE Security & Privacy ’08 Ben Ransford, IEEE Security & Privacy ’08 13
Attack #2: Eavesdrop Private Info Implanting Diagnosis physician Hospital Ben Ransford, IEEE Security & Privacy ’08 Ben Ransford, IEEE Security & Privacy ’08 13
Attack #2: Eavesdrop Private Info Implanting Diagnosis physician Also: Device state Patient name Date of birth Hospital Make & model Serial no. ... and more Ben Ransford, IEEE Security & Privacy ’08 Ben Ransford, IEEE Security & Privacy ’08 13
Attack #2: Eavesdrop Private Info In the future: Sophisticated devices may divulge a lot more data . Challenge: Can we add encryption? Ben Ransford, IEEE Security & Privacy ’08 14 Photo: Medtronic
Attack #3: Sniff Vital Signs 1 0.5 0 − 0.5 − 1 0 500 1000 1500 2000 2500 3000 ICD emits reconstructible Eavesdropping setup vital signs Issue: Vital signs can say plenty. Ben Ransford, IEEE Security & Privacy ’08 15
Attack #4: Drain Energy • Implant designed for infrequent radio use • Radio decreases battery lifetime “Are you sleeping?” “No!” Ben Ransford, IEEE Security & Privacy ’08 16
Simple Replay Attacks • Ours: “Deaf” (transmit-only) attacks • Caveats: Close range; only one ICD model tested; attacks not optimized; takes many seconds ~10 cm Ben Ransford, IEEE Security & Privacy ’08 Photo: Medtronic 17
Attack #5: Turn Off Therapies • “Stop detecting fibrillation.” • Device programmer would warn here Issue: Can quietly change device state. Ben Ransford, IEEE Security & Privacy ’08 18
Attack #6: Affect Patient’s Physiology • Induce fibrillation which implant ignores • Again, at close range • In other kinds of implant: • Flood patient with drugs • Overstimulate nerves, ... Issue: Puts patient safety at risk. Ben Ransford, IEEE Security & Privacy ’08 19
Ben Ransford, IEEE Security & Privacy ’08 #2: Fundamental Challenges http://secure-medicine.org/ 20
Conventional Solutions? How about... Non-trivial problem Authenticate device Key management is hard. programmers? Revocation? Encrypt all Under what key? transmissions? Must fail open! Ben Ransford, IEEE Security & Privacy ’08 21
Cannot fail closed • Closed: Don’t know the password? No admission! • Medical personnel need emergency access. • Challenge: design to fail open . Ben Ransford, IEEE Security & Privacy ’08 22
Security vs. Safety? • Tensions discussed in [IEEE Pervasive ’08] • Patient’s health is the top priority • We seek the sweet spots Ben Ransford, IEEE Security & Privacy ’08 23
Ben Ransford, IEEE Security & Privacy ’08 3. Defensive Directions http://secure-medicine.org/ 24
Prototype defenses against some of the attacks. Main idea: defend without using battery. Ben Ransford, IEEE Security & Privacy ’08 25
B.Y.O.P. • WISP = RFID + computation [Ubicomp ’06] • WISPer = WISP + our code • “Maximalist” crypto [RFIDSEC ’07] • Prototype: 913 MHz RFID band Goal: External party pays for power. Ben Ransford, IEEE Security & Privacy ’08 26
WISPer as Gatekeeper External party 1 • Authenticate against WISPer 3 WISPer • WISPer to ICD: “OK to use radio” 2 • Acoustic patient notification Implant • How to deter enemies? (Open question!) Ben Ransford, IEEE Security & Privacy ’08 27
How WISPer Could Work • Auxiliary device (possibly integrated) • Audible or tactile patient alert • Patient detects activity: am I in a clinic? • Fail open: sensible , tactile key exchange Ben Ransford, IEEE Security & Privacy ’08 28
Testing WISPer: Simulated Torso 1 cm bacon WISPer 6 cm chuck Energy harvesting through tissue is possible. Ben Ransford, IEEE Security & Privacy ’08 29
Ben Ransford, IEEE Security & Privacy ’08 Medical Devices Need Continued Attention! http://secure-medicine.org/ 30
Medical Device Trends • Further computerization of care • Longer-range communication • Cooperation among devices Issue: All of these bring risks. Ben Ransford, IEEE Security & Privacy ’08 31
Related Work • [IEEE Pervasive ’08] D. • [Ubicomp ’06] J. R. Smith, A. P. Sample, P. S. Powledge, S. Roy, Halperin, T. S. Heydt- and A. Mamishev: A wirelessly- Benjamin, K. Fu, T. Kohno, powered platform for sensing and and W. H. Maisel: Security computation . and privacy for implantable • [RFIDSEC ’07] H.-J. Chae, D. J. medical devices . (January Yeager, J. R. Smith, and K. Fu: 2008) Maximalist cryptography and • computation on the WISP UHF [JAMA ’06] W. H. Maisel, M. RFID tag . Moynahan, B. D. Zuckerman, T. • More in paper P. Gross, O. H. Tovar, D.-B. Tillman, and D. B. Schultz: Pacemaker and ICD generator malfunctions: Analysis of Food and Drug Administration annual reports. (JAMA 295(16)) Ben Ransford, IEEE Security & Privacy ’08 32
Conclusions • Analysis of wirelessly controlled IMD • Methodologies & defensive directions ‣ Software radio ‣ Energy harvesting gatekeeper ‣ Patient notification (deterrence) • Many open problems http://secure-medicine.org/ Ben Ransford, IEEE Security & Privacy ’08 33
Recommend
More recommend