Embedded Security for Embedded Devices 1 Boaz Shedletsky

Embedded Security for Embedded Devices 1

Boaz Shedletsky, LL. B, MBA Sternum LTD I have no relevant financial relationships

IOT market in healthcare is booming IOT Healthcare Market $117 Billion CAGR of 38. 1% $32. 47 Billion 3 2015 Source: IDC 2016 2017 2018 2019 2020

CONNECTED HEALTHCARE REVOLUTION Remote monitoring and management improves patients’ outcome Medical Errors 4 Patient Outcome https: //www. mddionline. com/what-could-total-connectivity-mean-medtech-and-healthcare Hospital costs 16% $200 B cost cutting

Io. T transforms our live BUT there is also another side 5

CYBER RISK: Medical devices were not developed for the connected ecosystem “ Radio-Controlled pacemakers aren’t as hard to hack as you (may) think 6 “ “ J&J Warns Diabetic patients: Insulin pump vulnerable to hacking A specific weakness [of Wanna. Cry] was disruption to MRI and CT scanners. Half a million patients with pacemakers are at risk of a hack and need a risky ‘software update’, st Jude manufacturer admit Medical Devices Hit By Ransomware For The First Time In US Hospitals DAN GOODIN REUTERS NAKED SECURITY MAIL ONLINE FORBES ars TECHNICA 26. 5. 2017 10. 04. 16 02. 01. 18 08. 31. 17 05. 17

What can go wrong? Parsing user input Communicating with insecure source Server I Smartphones 3 rd party vulnerabilities Libraries I OS Encryption / Authentication misuses Chip level vulnerabilities Bluetooth I Wi. Fi I Modem 7

Why do we care about Medical Io. T security ? It can harm the device itself The Hackable Cardiac Expansion Devices from St. Jude 8 It can harm your network It can attack others The Mirai attack

Why is it so difficult to secure ? High Diversity Operating Systems I Communication Protocols I Hardware Low Confidence 3 rd Party Libraries I Homegrown Code Very Low Resources 9 Compute | Memory | Battery

Existing solutions for the medical industry Good, but not enough 1. Penetration testing • Static Analysis • Red teams • Bug bounty programs 2. Network, network EXISTING SOLUTIONS 10

Under The Hood How Malware Works? 11

01 12 03 04 Vulnerability Exploit Shellcode Malware flaw in a system Instructions code injected into a running application to download or run a malware Malicious code spies on or damages a system 02 ‘weaponized’ code taking advantage of vulnerabilities to manipulate system behavior

Although every vulnerability is different, majority of exploitations SHARE A UNIQUE FINGERPRINT 13

Exploitation Fingerprint Override memory (stack heap, data) Corrupting memory Info leak to gather information and exploit the system Control execution flow 14 injecting malicious code malware

Under The Hood Sternum Core Technology Embedded Integrity Verification 15

High Level Product Implementation Connected Medical Device Different communication protocols Neuromodulation Pacemaker B NETWORK Do. Med PROTECTED Insulin Pump Pacemaker A 16 EIV technology integrates into the medical device’s development environment (IDE) to create a protected firmware including third-party code

Embedded Integrity Verification The best security exists RIPE benchmark RIPE: Runtime Intrusion Prevention Evaluator List size: 10 96. 5% success Benchmark 17 165/171 of attacks were prevented using EIV HPP

… With a single click integration 18

Our technology is: Simple fully integrated into your development environment Generic fully compatible for new and existing versions Efficient low consumption of resources ~3% Secure Highest security detection rate, blocks exploitations techniques in your code and 3 rd party code 19

Thank You Please visit us@ www. sternumiot. com or contact me at boaz@sternumiot. com 20