Agenda. Make the Internet of Things Work to Cloud The Risks and Weakness Security on the IoT Building a Secure IoT Path from device to Cloud.

Transcription

1 Secure IoT Connection by Spencer Chang May, 2018

2 2 Agenda Make the Internet of Things Work to Cloud The Risks and Weakness Security on the IoT Building a Secure IoT Path from device to Cloud Amazon AWS Summary

3 The efficient design of the data path for IoT applications 3 Wireless Sense Act Standards & Alliances Browser Cloud Platform

4 What is MCU? (Microcontroller Unit) 4 1. Memory and Flash inside 2. The different Peripheral Low Power for Battery application Low Cost 3. Easy to attach Sensor 4. The different IC Package 5. Quality and Reliability 8/16/32 MCU

5 The efficient design of the data path for IoT applications 5 Wireless Sense Act Standards & Alliances Browser Cloud Platform

6 6 Wireless Technologies 10,000 Primary differentiator is Internet access 1,000 Cellular / Satellite Range (meters) ISM Proprietary MiWi IEEE MiWi ZigBee IEEE IEEE Bluetooth Bluetooth WiBree IEEE Wi-Fi TCP/IP ,000 10, ,000 Data-rate Kbps

7 7 Wireless Technologies CONFIGURATIONS ADVANTAGES DISADVANTAGES Your Wi-Fi Product Router Cloud Existing infrastructure Customer familiarity Power Consumption Limited Range Large Stack Your Bluetooth Product Cell Phone Wi-Fi or Cell Cloud Smartphone availability Low power Easy setup Native security Limited Range Royalties Your ZigBee or Sub-GHz Product Gateway Wi-Fi or Ethernet Router Cloud Light stack Multi-radio support Multi-proto support Good range Very low power Additional concentrator required Your Ethernet Product Router Cloud Plug-and-play Flexible design Max. reliable bandwidth Cost effective Robust Requires wiring Your LoRa ZigBee or Sub-GHz Technology Product Gateway Wi-Fi or Ethernet Router Cloud Low power Long rage (10 miles) Spread spectrum data Bidirectional data path Public network adoption

8 8 WiFi----Network Types Infrastructure Client nodes communicate via an access point Most common, like connecting your PC to a home network Ad-hoc Point-to-Point connections Every node connected to every other node Android unsupported Soft AP Module looks like an Access Point AP module is central coordinator Basic network management DHCP, routing, gateway redirection

9 The efficient design of the data path for IoT applications 9 Wireless Sense Act Standards & Alliances Browser Cloud Platform

10 10 TCP/IP Protocol Stack Application Layer The Application layer is the group of applications requiring network communications. Host A Web Browser Generates the data and requests connections Host B Web Server Transport Layer (TCP/UDP) The Transport layer establishes the connection between applications on different hosts. Establishes connections with remote host Network Layer (IP) The Network layer is responsible for creating the packets that move across the network. Transfers packets with virtual (IP) addresses Data Link Layer (MAC) The Data Link layer is responsible for creating the frames that move across the network. Transfers frames with physical (MAC) addresses Physical Layer The Physical layer is the transceiver that drives the signals on the network. Transmits and receives bits

11 Transmit Data Using Network Layers Application Layer I want to download a web page from this address: Message Transport Layer (TCP/UDP) Source Port = 31,244 Destination Port = 80 Network Layer (IP) I want to download a web page from this address: Segment/Datagram Source IP Addr = Dest IP Addr = Packet Source Port = 31,244 Destination Port = 80 Message Data Link Layer (MAC) Source MAC Addr = 00:12:F1:1E:E8:93 Dest MAC Addr = 00:04:A3:4D:1C:73 Frame Src IP Addr Dest IP Addr Src Port # Dest Port # Message Physical Layer 11

12 Receive Data Using Network Layers Application Layer I want to download a web page from this address: Message Transport Layer (TCP/UDP) Source Port = 31,244 Destination Port = 80 Network Layer (IP) I want to download a web page from this address: Segment/Datagram Source IP Addr = Dest IP Addr = Packet Source Port = 31,244 Destination Port = 80 Message Data Link Layer (MAC) Source MAC Addr = 00:12:F1:1E:E8:93 Dest MAC Addr = 00:04:A3:4D:1C:73 Frame Src IP Addr Dest IP Addr Src Port # Dest Port # Message Physical Layer 12

13 Receive Data Using Network Layers Application Layer I want to download a web page from this address: Message Transport Layer (TCP/UDP) Source Port = 31,244 Destination Port = 80 Match! Network Layer (IP) I want to download a web page from this address: Segment/Datagram Source IP Addr = Dest IP Addr = Match! Packet Source Port = 31,244 Destination Port = 80 Message Data Link Layer (MAC) Physical Layer Source MAC Addr = 00:12:F1:1E:E8:93 Dest MAC Addr = 00:04:A3:4D:1C:73 Match! Frame Src IP Addr Dest IP Addr Src Port # Dest Port # Message 13

14 TCP/IP Protocol Stack (Terminology Reference) Application Layer Transport Layer Network Layer Data Link Layer (MAC) Physical Layer Reference from: 14

15 15 TCP/IP Protocol Stack (Terminology Reference) Layer # Layer Name 5 Application Transport Network or Internet Data Link Protocol HTTP, SMTP, MQTT etc TCP/UDP IP Ethernet, Wi-Fi Protocol Data Unit Messages Segments/ Datagrams Packets Frames 1 Physical 10 Base T, Bits Addressing n/a Port #s IP Address MAC Address n/a

16 TLS Protocol 16

17 17 MQTT Client MQTT a lightweight protocol for IoT messaging Open open sepc,standard 40+ client implementations Lightweight minimal overhead efficient format tiny clients(kb Reliable QoS for reliability on unreliable networks Simple connect+publish+subscribe

18 18 MQTT Communication bi-directional, async push communication

19 19 MQTT and TLS MQTT relies and TCP as transport protocol, which means by default the connection does not use an encrypted communication. To encrypt the whole MQTT communication, most many MQTT brokers like HiveMQ allow to use TLS instead of plain TCP. If you are using the username and password fields of the MQTT CONNECT packet for authentication and authorization mechanisms, you should strongly consider using TLS. Port 8883 is standardized for a secured MQTT connection, the standardized name at IANA is secure-mqtt and port 8883 is exclusively reserved for MQTT over TLS.

20 The efficient design of the data path for IoT applications 20 Wireless Sense Act Standards & Alliances Browser Cloud Platform

21 Cloud Platform 21

22 22 Agenda Make the Internet of Things Work to Cloud The Risks and Weakness Security on the IoT Building a Secure IoT Path from device to Cloud Amazon AWS Summary

23 Business Security Impact of IoT 23 Your brand Your Company Your Revenue Your IP Your Customers

24 24 Security Classification Data Security Protecting Authenticity and Integrity of communication Malware/Ransomware attacks Secure Key Storage Symmetric/Asymmetric Cryptography Design Security Protection against unauthorized execution Reverse Engineering Root of Trust Secure Boot Secure Field Upgrade Key Provisioning IP Protection Hardware Security Protection Against Proximity/Physical Attacks SPA/DPA Attack Perturbation Attacks Environmental monitors Anti-Tamper

25 25 Level of Security The highest level of security? Yes, but the level of security required is Application and Implementation dependent. mpos Wi-Fi Baby Monitor Required Security How to determine level of Security? Requires Data Security, MCU Security and Chip Security. Requires Data Security and MCU Security.Chip Security is not Mandatory. Risk Assessment is key to Gauge level of Security required for Application. The higher the risk, the higher the level of Security required.

26 The weakness of the data path for IoT applications 26 Wireless Sense Act Standards & Alliances Browser Cloud Platform

27 MCU should protect code 27

28 Key & Code Recovery Can Be Outsourced! 28

29 29 Secure Boot Boot code runs first on power-on Immutable code <- Trusted! Boot code authenticates application code from the SPI flash This code is now trusted Application code authenticates next level code 2nd link in the chain of trust

30 The weakness of the data path for IoT applications 30 Wireless Sense Act Standards & Alliances Browser Cloud Platform

31 31 Wi-Fi / Internet Security Gateway SSL/TLS 1.2 is for end to end encryption Ensures Data Encryption Coming out of the LAN, also Known as Internet Security Cloud Service WPA/WPA2 is for WLAN Ensures Data Encryption within the LAN to avoid intrusion Device Fake Device Authentication used for Anti-cloning, Ecosystem Management, Storage of Keys/Certificates

32 KRACK Wi-Fi WPA2 vulnerability 32 What is KRACK (Key Reinstallation Attack) VU#228519? WPA2 (Wi-Fi Protected Access II) protocol, the standard Wi-Fi security mechanism, has critical security vulnerabilities. WPA2 is widely used in Home Access Point. The vulnerabilities are in the standard definition and not in a specific implementation almost all implementations are affected What is the risk? While Exploiting the vulnerability, hackers can perform: Packet decryption Packet replay TCP connection hijacking HTTP content injection Etc.

33 KRACK Wi-Fi WPA2 vulnerability 33 The bad news Almost all of the Wi-Fi devices in the world from mobile phones to Access Points (AP) and PCs are affected. The good news Using Application level security (i.e. SSL / TLS) ensures the data being sent over the Wi-Fi link is secured. Even better news (for our customers) As security is critical for us and is one of our focus areas, Microchip was one of the first vendors to issue a patch. Updated firmware with fixes for the ATWINC15x0 is available online and other devices are being evaluated / fixed. Microchip web site: KRACK Detailed information:

34 Wireshark Open/WEP/WPA Demo 34

35 The weakness of the data path for IoT applications 35 Wireless Sense Act Standards & Alliances Browser Cloud Platform

36 OpenSSL Heartbleed 36

37 37 CVE The Heartbleed Bug has affected websites, s, and banking institutions utilizing open SSL/TLS encryption. As the story continu to unfold, IT security experts provide their thoughts on the one of t most significant internet security crises to date Private Key Cookie SESSION ID ACCOUNT/PASSWORD PERSON Info/Credit Card Other memory Info

38 HOW THE HEARTBLEED BUG WORKS 38

39 HOW THE HEARTBLEED BUG WORKS 39

40 HOW THE HEARTBLEED BUG WORKS 40

41 HOW THE HEARTBLEED BUG WORKS 41

42 HOW THE HEARTBLEED BUG WORKS 42

43 OpenSSL CVE (Heartbleed) 43

44 How to Hack HTTPS/SSL Secured Websites using MITMF 44

45 The weakness of the data path for IoT applications 45 Wireless Sense Act Standards & Alliances Browser Cloud Platform

46 Do you know DDoS? distributed denial-of-service attack 46

47 Cloud Security 47

48 48 Cloud Security

49 49 Agenda Make the Internet of Things Work to Cloud The Risks and Weakness Security on the IoT Building a Secure IoT Path from device to Cloud Amazon AWS Summary

50 ATECC508A/ ATECC608A Introduction Provides secure storage and execution environment for keys Symmetric (SHA256) Asymmetric (elliptic curve) Supports NIST P-256 curve a.k.a. secp256r1, prime256v1 10.5Kb storage across 16 slots High-quality internal RNG Supports SHA256, ECDSA, and ECDH algorithms 50

51 ATECC508A/ATECC608A/ HW Security 51 Advanced Multi-Level HW Security Active shield over entire chip All memories internally encrypted Data independent execution Internal state consistency checking Power supply tamper protection Temperature lockouts Internal clock generation Secure test methods No die features can be identified No package or die identification Designed to defend against a multitude of attacks Microchip Active Shield Standard uc, logic & memory

52 52 ATECC508A Acceleration ATECC508A versus Cortex M0+ running at 48MHz 6000 H/W vs S/W Benchmark 5000 milliseconds P256 Key Gen ECDSA Sign ECDSA Verify ECDHE ATECC508A Cortex 48MHz Reduces code size (no elliptic curve crypto library)

53 53 ATECC508A/ ATECC608A TLS Support Supports authentication (ECDSA) and key exchange (ECDH) Encryption (AES) is still handled by the host MCU. ATECC608A support AES. Protects the device s identity key Accelerate verification and key agreement

54 54 TLS Handshake Mutual Client Random Verify Verify ClientHello ServerHello Certificate ServerKeyExchange Server CertificateRequest ServerHelloDone GenKey Certificate ECDH ClientKeyExchange Sign CertificateVerify ATECC508A ATECC608A Finished Finished

55 55 TLS Handshake One Way Client Random Verify Verify ClientHello ServerHello Certificate ServerKeyExchange Server CertificateRequest ServerHelloDone GenKey Certificate ECDH ClientKeyExchange CertificateVerify ATECC508A ATECC608A Finished Finished

56 56 ATECC508A for AWS IoT (TLS)--Example ATECC508A is very configurable AWS configuration preconfigures for use with AWS IoT Slot 0 Device private key Slots 2 ECDHE private key Slots 10-12,14 Device and signer certificates Other slots pre-configured for common use cases

57 57 ATECC508A Certificate Key ATECC508A stores the device s private key Stored in slot 0 Internally generated by RNG Can t be read, never exposed Public key used in its certificate when provisioned

58 58 ATECC508A Key Agreement Ephemeral private key Helps speed and code size Regenerated for every session Stored in slot 2 Used with ECDH command to generate pre-master secret

59 59 Certificate Storage Certificates are public Store both device certificate and signer certificate Simplifies certificate validation Uses compressed format Dynamic certificate data on ATECC508A Static certificate data in firmware Uses slots 10-12,14 for storage

60 Notes on Microchip s Factory Provisioning 60 Secure Facilities Camera monitored Physical access control Network isolation HSMs in floor secured locked cages Frequent 3 rd party audits Hardware Secure Modules (HSM) Highly secure computers World class certifications FIPS Level 3 CC EAL 4+ Certification U/L 1950 (EN60950) & CSA C22.2 compliant FCC Part 15 - Class B Floor bolted secure cage in a dedicated room BAC and EAC epassport HSM from

61 Secure authentication scheme for IoT and cloud servers 61

62 62 Agenda Make the Internet of Things Work to Cloud The Risks and Weakness Security on the IoT Building a Secure IoT Path from device to Cloud Amazon AWS Summary

63 63 The Chain of Trust HP s AWS Account Amazon Device Certificate Verify OK! HP Material Box) IOT Device Device Certificate

64 issues Get Device Certificate HP 1. A lot of time to register 100K IOT device on cloud and get the 100K Certificate 2. Where and How to store the 100K Certificate and keep them secure? PC? Material Box) IOT Device Device Certificate 3. A lot of Cost to store the 100K Certificate into every Device 4. Where to store the Certificate on Device and keep them secure? FLASH? 64

65 65 The Chain of Trust OEM s AWS Account HP-1 Reject! HP-2 (son) Register! Customer-Specific Production Signers with BYOC (CA provisioning) Device certs Loaded with JITR (Lambda ) Cindy Root of Trust HP-2 (Son) (to Microchip) Customer- Specific Production Signers Root CA (OEM) HP-3 ( 孫 ) (Material Box) IOT Device Device Certificate

66 Amazon AWS IoT Demo 66

67 Amazon Alexa Demo 67

68 Summary

69 69 Vision Be The Very Best Embedded Control Solutions Company Ever

70 70 The Security level of IoT device Networking appliances Smart Home Building Automation Intelligent transportation Intelligent medical Ambient Temperature

71 71 Country Who's responsible for IoT security IC/Solution Provider Division/Marketing/Sales/FAE OEM/ODM/OBM Manufacture User

72 The Regulation of the Internet of Things 72 With the rise of the IoT and related technologies such as robotics, AI and Big Data, new regulatory frameworks are deployed in an age where data is gold. Moreover, the Internet of Things needs specific attention in the scope of, among others, the GDPR and the eprivacy Regulation. IoT and Data Protection Impac Assessments under the GDPR IoT, data breaches and the reporting duty IoT and the challenge of consent and lawful processing

73 73 Guidelines for the Safety of the Internet of Things (1/3) IOT Device Manufacture In November 15,2016, the Department of Homeland Security (DHS) issued a set of Strategic Principles for Securing the Internet of Things (IoT), Version 1.0. These principles highlight approaches and suggested practices to fortify the security of the IoT and will equip stakeholders to make responsible and risk-based security decisions as they design, manufacture, and use internet-connected devices and systems. Incorporate Security at the Design Phase Connect Carefully and Deliberately Promote Security Updates and Vulnerability Management Promote Transparency across IoT Prioritize Security Measures According to Potential Impact Build on Recognized Security Practices

74 74 Guidelines for the Safety of the Internet of Things (2/3) IOT Device Manufacture Promoting New Business Harnessing Secured IoT System Implementing Technological Development and Demonstration Related to IoT Systems Security Creation of Secured IoT Systems Improving Structural Frameworks for IoT systems Security Considering Approaches for Enhanced IoT Systems Security

75 75 State of the Art and Challenges for the Internet of Things(3/3) IETF Security Architecture Security Policies Security Services Security Technical Architecture Security incident handling

76 In the Future

77 AWS GreenGrass and Azure Field Gateway (HW-Based) 77

78 New IoT Gateway Platform (AWS GreenGrass)--MPU 78 MPU AWS GreenGrass Slides ` Microchip s SAMA5D2 family offers full Greengrass compatibility in a low-power, small form factor microprocessor (MPU) targeted at industrial and long-life gateway and concentrator applications in harsh and physically insecure environments.

79 Thank you