terraswarm terraswarm
play

TerraSwarm TerraSwarm A Toolkit for Construction of Authorization - PowerPoint PPT Presentation

Feb 28, 2024 •204 likes •538 views

TerraSwarm TerraSwarm A Toolkit for Construction of Authorization Service Infrastructure for the Internet of Things (IoT) Hokeun Kim 1 , Eunsuk Kang 1 , Edward A. Lee 1 , David Broman 2 1 University of California, Berkeley 2 KTH Royal Institute

  1. TerraSwarm TerraSwarm A Toolkit for Construction of Authorization Service Infrastructure for the Internet of Things (IoT) Hokeun Kim 1 , Eunsuk Kang 1 , Edward A. Lee 1 , David Broman 2 1 University of California, Berkeley 2 KTH Royal Institute of Technology IoTDI 2017, Pittsburgh, PA April 19, 2017 Sponsored by the TerraSwarm Research Center, one of six centers administered by the STARnet phase of the Focus Center Research Program (FCRP) a Semiconductor Research Corporation program sponsored by MARCO and DARPA.

  2. Overview – IoT & Authorization • Internet of Things • Authorization (access control) – Critical for computer security Private data Control Benefits, but also challenges • Existing security solutions? • Proposed approach – SST – May work well for some parts of – SST: Secure Swarm Toolkit the IoT, but not for the entire IoT! – An open-source toolkit for building authorization infrastructure for the IoT – To address IoT security challenges 2 TerraSwarm Research Center

  3. Motivation • Challenges in IoT security [1] Heterogeneity Security requirements & resource availability • Connectivity (wired connections vs. mobile devices) • System management • 3 TerraSwarm Research Center [1] Singh et al., 2016. "Twenty Security Considerations for Cloud-Supported Internet of Things"

  4. Motivation (cont'd) • Challenges in IoT security [1] Operation in an open (or hostile) Environment Physical access & wireless access to IoT devices • Higher risk of being compromised • Must be able to revoke access of compromised IoT devices • 4 TerraSwarm Research Center [1] Singh et al., 2016. "Twenty Security Considerations for Cloud-Supported Internet of Things"

  5. Motivation (cont'd) • Challenges in IoT security [1] Sources: "Ericsson Mobility Report", June 2016 / "Cisco Global Cloud Index: Forecast and Methodology,2015–2020", Published in 2016 Scalability 28 billion connected devices in 2021 • 15.3 ZB data traffic in 2020 • 1 ZB (Zetta byte) = 10 9 TB (Terra bytes) – 5 TerraSwarm Research Center [1] Singh et al., 2016. "Twenty Security Considerations for Cloud-Supported Internet of Things"

  6. Background: Authorization & IoT • Authorization – Access control • "Can I enter the EECS building?" – Allowing/denying access to resources – Revoking access (e.g., lost ID card) • Authentication – Identifying someone/something • "Member of EECS?" – Essential for authorization 6 TerraSwarm Research Center

  7. Background (cont'd) • Many IoT platforms use TLS (or DTLS [2] ) for authentication/authorization – E.g., Amazon AWS IoT, OpenIoT [3] , OSCAR [4] , etc. • TLS (Transport Layer Security, also called SSL/TLS) – Underlying security protocol for HTTPS – Widely used, very successful for web [1] Variant of TLS over UDP, 2012 "Datagram Transport Layer Security Version 1.2. RFC 6347" [2] John Soldatos et al., 2015. "OpenIoT: Open Source Internet-of-Things in the Cloud" 7 TerraSwarm Research Center [3] Vucinic et al., 2015. "OSCAR: Object security architecture for the Internet of Things"

  8. Background (cont'd) • TLS based on a Certificate Authority (CA) digital certificate Certificate issued by CA Public-key cryptography Certificate Web Server Browser Encrypted Secure channel • Challenges with using TLS for the entire IoT – Energy overhead of public-key crypto & certificates – Scalability (managing certificates for ~28 billion devices) – Revocation of certificates can be problematic [1,2] – Limited support for one-to-many communication [1] Mutton, "Certificate revocation: Why browsers remain affected by Heartbleed", Netcraft, April, 2014 8 TerraSwarm Research Center [2] Duncan, "How certificate revocation (doesn’t) work in practice", Netcraft, May, 2013

  9. Background (cont'd) • Challenges with applying other security solutions Kerberos Authentication Server * Service Server Client * *Ticket: temporary token for accessing service Source: http://www.yuden.co.jp/ut/solutions/wsn/ – Kerberos [1] – Security solutions for "Things" • Advantages for access revocation • E.g., WSN, MANET or swarm devices • Requires stable connection • Assume homogeneous environments • Centralized architecture • Not designed for Internet scale [2] [1] C. Neuman et al., 2005. "The Kerberos Network Authentication Service (V5)". RFC 4120 [2] Alcaraz et al., 2010. "Wireless sensor networks and the internet of things: Do we need 9 TerraSwarm Research Center a complete integration?"

  10. Proposed Approach • SST – Secure Swarm Toolkit – An open-source toolkit for authentication/authorization of the IoT (available on https://github.com/iotauth) 10 TerraSwarm Research Center

  11. Proposed Approach (Cont'd) • Specific goals of SST Integration of existing security solutions (not inventing new Heterogeneity ones) Locally centralized and Open Environment globally distributed (Access Revocation) architecture Ease of deployment Scalability by local domain experts at a large scale 11 TerraSwarm Research Center

  12. SST’s Design and Implementation • Auth [1] – Locally centralized, globally distributed auth entication/ auth orization entity (software) – Java program to be deployed on edge devices [2] (e.g., Intel IoT gateways) Auth Personal Auth Area Auth Smart Home Medical Center Network Internet Auth Auth Auth Auth [1] A prototype of Auth has been Conference Room Auth proposed in Kim et al., 2016. "A Secure Auth Network Architecture for the Internet of Things Based on Local Authorization Electric Vehicle Factory Entities" Auth [2] Lopez et al., 2015. "Edge-centric Computing: Vision and Challenges” Auth 12 TerraSwarm Research Center Smart Power Grid

  13. Design and Implementation (cont'd) • Secure communication accessors Auth IoT Service Message Message – Software building blocks for securely accessing Auth and the IoT services Secure Comm Accessor – Encapsulate crypto keys & operations Encrypt & Crypto Process Generate authenticate – Help IoT developers who are not Key Message Message Message security experts Decrypt & verify IoT Application (Actor-oriented Program Model) – Currently available accessors (in JavaScript) – We're still at a starting point and working on more accessors! – For more information, see https://accessors.org 13 TerraSwarm Research Center

  14. Design and Implementation (cont'd) • Example: How SST (Auth and accessors) works Encrypted with Distribution Key between Auth and Client Auth Session Key I want to use IoT Service! Client IoT Service SecureCommServer SecureCommClient Process Request Client To Send Message Access Respond Response To Client From Service 14 TerraSwarm Research Center

  15. Design and Implementation (cont'd) • Example: How SST (Auth and accessors) works Auth Client IoT Service SecureCommServer SecureCommClient Initiate challenge-response Process Request Client To Send Message Access Respond Response To Client From Service Challenge-response [1] to check whether IoT Server has the same Session Key [1] Similar to TLS PSK extension by Eronen and Tschofenig. 15 TerraSwarm Research Center 2005. Pre-Shared Key Ciphersuites for TLS. RFC 4279.

  16. Design and Implementation (cont'd) • Example: How SST (Auth and accessors) works OK, Client can access this IoT Service. Encrypted with Distribution Key between Auth and IoT Server Auth Session Key Client IoT Service SecureCommServer SecureCommClient Initiate challenge-response Process Request Client To Send Message Access Respond Response To Client From Service 16 TerraSwarm Research Center

  17. Design and Implementation (cont'd) • Example: How SST (Auth and accessors) works Auth Client IoT Service SecureCommServer SecureCommClient Initiate challenge-response Process Request Finish challenge-response Client To Send Message Secure communication Access Respond Response To Client From Service Protected communication channel using session key and standard cryptography [2] [2] Followed TLS 1.2’s standard, including 17 TerraSwarm Research Center sequence number, encrypt-then-MAC

  18. Heterogeneity SST for Heterogeneity Open Env. Scalability • SST’s configuration alternatives Less energy More security Distribution key Underlying protocol overhead guarantees D-3 P-2 Updated using public key TCP D-2 Permanent P-1 D-1 UDP No direct key distribution Crypto strength Cached session keys & key lifetimes K-3 K-2 K-1 C-1 C-2 C-3 Unlimited Multiple One Lightweight & long Strong & short Two (server-client) Authentication only O-1 S-1 More than two (broadcasting) Encryption O-2 S-2 Unlimited Ephemeral Diffie-Hellman Effect of knobs will be shown O-3 Number of S-3 through experiments! Session key usage session key sharers 18 TerraSwarm Research Center

More recommend