280 likes | 462 Views
Link Layer Key Revocation and Rekeying for the Adaptive Key Establishment Scheme. Benedikt Bock Hasso-Plattner-Institute, Digital Engineering Faculty, University of Potsdam. Wireless Personal Area Network. Smart Home [2]. Smart Parking [1]. Chip Memory ≤ 32kB
E N D
Link Layer Key Revocation and Rekeying for theAdaptive Key Establishment Scheme Benedikt Bock Hasso-Plattner-Institute, Digital Engineering Faculty, University of Potsdam
Wireless Personal Area Network AKES Key Revocation and Rekeying Smart Home [2] Smart Parking [1]
Chip Memory ≤ 32kB Processor 32MHz ARM Cortex M3 Programm Memory ≤ 512kB Energy BatteryPowered ConstraintsofIoT Devices CC2538 [3] AKES Key Revocation and Rekeying
IEEE 802.15.4 AKES Key Revocation and Rekeying
IEEE 802.15.4 AKES Key Revocation and Rekeying
Key Management Key Management Session Key Establishment Rekeying Key Revocation AKES Key Revocation and Rekeying
Adaptive Key Establishment Scheme [4] AKES Key Revocation and Rekeying
Adaptive Key Establishment Scheme [4] Key Management Session Key Establishment Rekeying Key Revocation • Pairwisesessionkeyestablishmentbased on predistributedkeys • Works with all predistributionschemes (e. g. fully pairwisekeysscheme [5]) • Denial-of-sleep resilient Key Predistribution AKES Key Revocation and Rekeying
Key Revocation and Rekeying • Distributed • All nodessharetheresponsibility to find and evictnodes. • Consensus between all nodesisnecessary • Moore et al. [6] proposed a suicidebasedapproach • Assumesintrusiondetectionsystem on eachnode • Assumeseven network topology • Chuang et al. [7] proposed a pkcbasedapproach • High calculationcost • Centralized • Single instanceisresponsible to find and evictnodes • Dini et al. [8] proposed a floodingbasedprotocol • Usesbroadcasts and thereforeassumesthatmessagesarereceived and mayberouted via evictednodes • Assumesknown network topology • Raza et al. [9] Proposed a unicastbasedapproch • Based on CoAP and thereforeroutesmessages via evictednodes. AKES Key Revocation and Rekeying
Approach • Design Goals • Energy-efficientoperation • Avoidevictednodes • Independence from network topology • Live Feedback • Incorporationintoprotocols • Centralized • Unicastbased • Link layer source routing AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach - Overview AKES Key Revocation and Rekeying
Approach – Control Flow AKES Key Revocation and Rekeying
Approach – Control Flow AKES Key Revocation and Rekeying
Approach – Distribution Flow AKES Key Revocation and Rekeying
Focus on messagedistribution Border Nodes and Nodes Based on Contiki-NG Base Station Based on Python aiocoapasCoAPlibrary Implementation AKES Key Revocation and Rekeying
Evaluation • Based on Coojasimulation • Simulation speed 100% • Base Station connected via Unix sockets • Measurements • Total duration • Numberofsentframes • Sentframes per node AKES Key Revocation and Rekeying
Evaluation – Total Duration • Duration of 55.5 secondswith 100 nodes and 1 bordernode • Half amountofnodesmeans half duration • Double amountofbordernodesmeans half duration Approximately linear scalability AKES Key Revocation and Rekeying
Evaluation – Sent Frames • Additional bordernodesreducetheamountof send framessignificantly • Sentframes per nodearereducedwith an additional bordernode Additonalbordernodesimproveenergyefficiency AKES Key Revocation and Rekeying
Fragmentation of link layerframes Optimizelayer 3 adaption Further evaluationwithinphysicaltestbed Future Work AKES Key Revocation and Rekeying
References AKES Key Revocation and Rekeying