Keys for Success: Today s Landscape of IoT Technologies and Security Standards

Size: px

Start display at page:

Download "Keys for Success: Today s Landscape of IoT Technologies and Security Standards"

Theodore Stafford
6 years ago
Views:

1 Keys for Success: Today s Landscape of IoT Technologies and Security Standards Pratul Sharma, Technical Marketing Manager, ARM Amit Shah, VP R&D, Alcatel-Lucent mbed Sponsored session/ ARM Tech Con 2015 November 11, 2015

2 Agenda ARM IoT Technology standards Landscape - Focusing on Web to Edge IoT security Alcatel-Lucent Secure Services Device Certification 2

3 The growth opportunity for IoT Expected number of IoT devices shipped in B Smart Mobile 6% CAGR 58% CAGR New ecosystems and business models are emerging 1.6B Smart Home 1.8B Smart City IoT 43% CAGR 54% CAGR 1.1B Auto. 0.6B Industrial 21% CAGR 3 Source: Gartner, 2015

4 Two Scenarios of IoT Market Growth The future Open Data and Objects Smart Everything Reach Sensors & Actuators Networks Risk Today Applications Mobile internet Internet / broadband M2M SaaS Fixed Telephony Networks Mobile Telephony 4

5 Problems to Solve Interoperability Scalability Security Technology Reuse Lower barrier to Innovation 5

6 These Problems are Already Solved In the context of the Internet and the Web Any Web Browser works with any web service, more or less Regardless of wire protocols used in the network Regardless of the data models and content types Across vertical application segments The Web scales to planetary size Low barrier to Innovation We want the same qualities for IoT What are the important design patterns in Internet and Web Architecture? How can these design patterns apply to IoT? 6

7 Internet and Web Design Patterns Narrow Waist Architecture Layered Protocols Uniform Addressing Stateless Interaction 7

8 A simple Model of an IoT system Comm. Infra. Interface Communication Infrastructure IoT Devices middleware Web app For Interoperable and scalable IoT system we need standards for 1) Data Communication 2) Web Objects 3) Device Management 8 Uniform end-end Security

9 Communication interfaces in an IoT system IoT Device Comm. Infra. Interface Comm. Infra. App. Interface IoT Devices middleware Web app 1) Data Communication 9

Addressing, Routing IP HTTP TCP IP 802.3 IP TCP HTTP 802.3 Medium 802.3 HTTP TCP IP 802.

10 Middleware and Web app. Interface middleware Message Body Message Body HTTP HTTP App. layer HTTP HTTP TCP HTTP TCP/TLS Connection, Reliability, data flow TCP/TLS HTTP TCP IP TCP HTTP IP Addressing, Routing IP HTTP TCP IP IP TCP HTTP Medium HTTP TCP IP s of bytes It s a Standard IP interface as constrained devices are not involved Standard IP protocol stack is suitable for communication 10

Routing 6LoWPAN CoAP UDP 6LowPAN 802.15.

11 Middleware and IoT device Interface IoT Devices (Constrained) middleware Message Body Message Body CoAP CoAP App. layer CoAP CoAP UDP CoAP UDP/DTLS Connection, Reliability, data flow UDP/DTLS CoAP UDP 6LowPAN UDP CoAP 6LoWPAN Addressing, Routing 6LoWPAN CoAP UDP 6LowPAN LowPAN Medium UDP CoAP CoAP UDP 6LowPAN s of bytes 11 Standard IP protocol stack is not suitable for communication IETF has defined lightweight protocols like CoAP and 6LoWPAN for data communication

12 CoAP features: Machine to Machine Communication Resource discovery New devices (nodes) are discovered automatically. No human intervention needed. Easy to add new devices. Easy to replace the devices. Simple Caching Optimize performance Subscription Push of Information from IoTdevices to application. Content Negotiation Explicitly indicate the content type of the payload in the header ReST oriented ReST based web services are based on architecture of the web and more compatible with existing web tools and techniques. 12

13 6LoWPAN : Connecting Billions of Things Standard Internet IOT nodes 6LoWPAN specification 6LoWPAN is adaptation layer for IPV6 Function IPV6 header compression Packet fragmentation and re-assembly Optimized Neighborhood discovery Packet size ~127 bytes Packet size ~ 1280 bytes 13

14 Why 6LoWPAN No Translation Gateways Re-use existing infrastructure Open and Free Standard Encourages Innovation Managing and commissioning 14

15 Thread 15

16 Web objects Service 1 Service 2 Service 3 Service 1 Service 2 IPSO Object Standard Web object Binary Web Object IoT Device CoAP UDP 6LoWPAN Binary Web Object IoT Device CoAP UDP 6LoWPAN IoT Device CoAP UDP 6LoWPAN Interoperable Services Service 1 Service 2 Non-interoperable devices & Services We need standard Web objects for Interoperability IoT Device IPSO Object CoAP UDP 6LoWPAN IoT Device IPSO Object CoAP UDP 6LoWPAN 16 Interoperable Devices & Services

17 IPSO Object example: Temperature Sensor Object info Object Object ID Object URN Multiple Instances? IPSO Temperature 3303 urn:oma:lwm2m:ext:3303 Yes Resource Info Resource Name Resource ID Access Type Multiple Instances? Units Descriptions Sensor Value 5700 R No Cel This resource type returns the Temperature Value in C Min Measured Value 5601 R No Cel The minimum value measured by the sensor since it is ON Max Measured Value 5602 R No Cel The maximum value measured by the sensor since it is ON Accessing the Resources (Standard URIs) Temperature Value /3303/0/5700 Min Measured Value /3303/0/5601 Max Measured Value /3303/0/5602 LWM2M Client /303/ Temperature Value Min Measured Value Object Max Measured Value

18 Sensinode 2013 Device Management 18

19 IoTValue Chain is Very Complex IP Provider SoC Provider Source: Gartner Research,

20 IoT devices with Flat Security Model IoT devices include significant software complexity Code base is too large for exhaustive validation With flat security all code/data lives in a shared address space Bugs in any code can lead to a security flaw If malicious code updates Flash then it may become impossible to remotely recover a device Server Application Protocol BLE Stack SSL Library Diagnose WiFi Stack Secure Storage Device Secure ID Crypto Management Crypto API Keys Firmware RNG Update 20

21 Device Security: Secure Partitioning for MCUs Split memory into private critical and public uncritical Small private footprint enables exhaustive verification Public code never sees keys/secrets Vulnerabilities on public side can t affect private side Private side can verify integrity of the public side Public code can t write code directly to Flash Private side can reliably recover device to clean state Server Public BLE Stack WiFi Stack Application Protocol SSL Library Device Management Diagnose Private Firmware Update Secure Storage Crypto Keys Crypto API Secure ID RNG 21

22 mbed TLS SSL/TLS/ DTLS Cipher Layer MD Layer (Hash) Public Key layer RNG AES DES Triple DES RC4, RC5.. MD2, MD4, MD5 SHA-1, SHA-2 RSA DH Key exchange ECC ECDSA ECDH 22

23 Security Services in mbed Secure device identity Key and certificate storage Protection of server API tokens Transport layer security (and APIs to corresponding HW features) Cryptographic algorithms Key Exchange Random number generation Firmware Over The Air (FOTA) enables agile security (future) Patch vulnerabilities Move to new (stronger) crypto algorithms 23

24 IoT System Security IoT Devices middleware Web app Boot Correct FW Operation Code tampering, access Reset/Shutdown Secure Keys/ID Data communication Encryption, decryption Device Management Auth FOTA, Bootstrap, Provisioning Secure user Access and Authentication 24 Re-configure to correct state

25 Build IoT Device mbed OS Tools 25 Connect your devices mbed Device Connector Build application with example code Reference apps Utilize cloud solutions Cloud Partners

26 So how do we take this to the market? We already discussed relevant standards for IoT that will allow scale but without trust and security we won t have the market growth we d like to see In order to take the standards based end-points to the market, we need remove other barriers to entry The next section will highlight some of the challenges and roadblocks that need to be addresses and provide a path that enables you to address and remove them 26

security breaches October 2014 Millions of smart meters in Spain compromised

27 The Internet of (hacked) Things on the rise As the number of connected devices rises, and the value created from the data, so does the risk for abuse, and security breaches October 2014 Millions of smart meters in Spain compromised February million BMWs impacted July million Chryslers recalled 27

28 Why is it happening? Broken chain of trust Many sources of data (sensors) are unmanaged and the transport network is un-trusted 1. Intercept and manipulate data in transit - Man in the middle attack 2. Compromise the device: Direct access, side loading, remote access IOT applications and analytics Data connectivity IP Value?? Untrusted network Data Unmanaged data source 28

29 How to solve it? Manage endpoints (sensors) to establish trust Industry best practices: 2-way authentication Signed software delivery from trusted source to ensure authenticity Certificates, keys, encryption Device management IP IOT applications and analytics Secure data connectivity Secure connection Value DM Data Managed data source 29

30 Standards and best practices OMA Light Weight M2M (LWM2M) Client Servier Architecture for M2M Designed for (battery) constrained devices Simple, low footprint, BW efficient Both device management (incl FOTA) and business data Based on CoAP (IETF) DTLS-based security Transport-agnostic Generic restful protocol on top of UDP or SMS More then just a protocol REST resources and management procedures on top of CoAP Resource model and semantic (server, device, firmware, reboot, ) A set of Use Cases (bootstrap, register, device mngt and sevice enablement, data observation/notification) Secure & BW efficient AAA Interfaces Bootstrapping Registration Object/resource access Reporting Managed remote asset Device management LWM2M server LWM2M client Objects M2M device Application LWM2M CoAP DTLS UDP SMS Stack Efficient payload CoAP protocol DTLS security UDP or SMS bearer Objects 30

31 Motive role in the value chain What matters most? IoT Secure Services Connect, Manage, Control, Collect, Analyze, Act CORE/EDGE RAN End users Enterprise, cities SI s Telcos Device OEM Chipset/modules Data anywhere Usability Confidentiality Data ownership Any device, any app Data integrity and confidentiality Solution cost Any Telco Design time Reusability Ease of use Security, robustness Network optimization Device coverage/interoperability OPEX reduction Move up in the value chain Reduce onboarding cost SW programmable Footprint: Mgmt and data clients Drive cost down Volume 31 Device certification

MotiveSMART Device Certification Program TR069 devices OMA-DM/CP devices CSP devices ARM mbed devices LWM2M devices The MotiveSmart Program uses standards based verification testing Enables

participate in the program: Internet gateway devices, M2M gateways, automotive units, mobile handsets, chipsets, client protocol stacks, set-top boxes, VoIP ATAs and phones, WiMAX devices,

32 MotiveSMART Device Certification Program TR069 devices OMA-DM/CP devices CSP devices ARM mbed devices LWM2M devices The MotiveSmart Program uses standards based verification testing Enables providers/carriers to have their devices tested and validated for interoperability prior to deployment Over devices tested from 100+ of the world s top device and technology manufacturers participate in the program: Internet gateway devices, M2M gateways, automotive units, mobile handsets, chipsets, client protocol stacks, set-top boxes, VoIP ATAs and phones, WiMAX devices, Femtocells, USB dongles, NAS devices, Homeplug, ONTs Device requirements Scope, test plans OEM self verification Motive verification and certification Motive knowledge base Motive device management Come see us at ARM mbed Zone (TECHCON Nov , 2015 Santa Clara) 32

33 MotiveSMART Simple work flow Sign-Up at our cloud based secure portal Tell us about the thing you are certifying Access is granted Start testing Look at logs, test as often as needed Certification Complete Go over the results Download test result 33

34 MotiveSMART Program Members devices tested to date 34

35 Come see us at Booth #512 35

36 The trademarks featured in this presentation are registered and/or unregistered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved. All other marks featured may be trademarks of their respective owners. Copyright 2015 ARM Limited

Resilient IoT Security: The end of flat security models

Resilient IoT Security: The end of flat security models Xiao Sun Senior Application Engineer ARM Tech Symposia China 2015 November 2015 Evolution from M2M to IoT M2M Silos of Things Standards Security