Jan 2014 Tero Kivinen, INSIDE Secure

Slides:



Advertisements
Similar presentations
Doc.: IEEE Submission Mar 2014 Tero Kivinen, INSIDE Secure Slide 1 Project: IEEE P Working Group for Wireless Personal Area.
Advertisements

Submission Title: [LB 28 Results] Date Submitted: [14 March 2005]
Project: IEEE Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposals for adding a version number and for the treatment.
Submission Title: [Add name of submission]
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
Submission Title: Coding example for the ULI
Jan 2014 Tero Kivinen, INSIDE Secure
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Add name of submission] Date Submitted:
doc.: IEEE <doc#>
Submission Title: [WG-Treasurer’s Report July04]
Jan 2014 Robert Moskowitz, Verizon
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: Algorithm agility without frame by frame information
March 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Toumaz response to TG6 Call for Applications]
<month year> doc.: IEEE < e>
<May,2009> doc.: IEEE <doc .....> <July 2009>
doc.: IEEE <doc#1>
Submission Title: Example of P2P route discovery
Submission Title: Coding example for the ULI
<month year> doc.: IEEE <xyz> January 2001
Submission Title: Coding example for the ULI
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Enhancing reliability of data transmission.
<month year> <doc.: IEEE doc> December 2015
September g Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Recognition of Hiroshi.
Submission Title: [Proposal for Short Address Multicast]
Jan Robert Moskowitz, Verizon
Submission Title: [Uniform bandplan for TG4a Modulation]
<month year> doc.: IEEE <xyz> November 2000
Submission Title: Algorithm agility without frame by frame information
Submission Title: [IEEE WPAN Mesh Reference Model]
doc.: IEEE /XXXr0 Sep 19, 2007 June 2009
Submission Title: [Frame and packet structure in ]
November 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Simplified geometry for the usage model.
Submission Title: Rogue Resolutions from kivinen
<month year>20 Jan 2006
<month year> <Nov 2018>
<month year> doc.: IEEE < e>
September 2000 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG3 Rank Order Voting Process Description.
April 19 July 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: WNG Closing Report for San Diego.
<month year> <doc.: IEEE doc> January 2016
March 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [DF6 Radio-burst length over PSDU size] Date.
Jan 2014 Tero Kivinen, INSIDE Secure
<month year> doc.: IEEE s March 2019
Tero Kivinen, AuthenTec
Tero Kivinen, INSIDE Secure
Submission Title: [ e Schedule Update]
Submission Title: Rogue Resolutions from kivinen
Submission Title: [LB 28 Results] Date Submitted: [14 March 2005]
January 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [TG3c Project Plan] Date Submitted: [17.
doc.: IEEE <doc#>
Tero Kivinen, AuthenTec
July 2013 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Technical Decisions for KMP transport Date.
8/4/2019<month year> <month year> doc.: IEEE Doc: IEEE vat
September 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Suggested TG3c PAR Changes] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
Mar 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Resolution for Comment 70 ] Date Submitted:
<month year> <doc.: IEEE doc> September 2015
August, 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Improve the latency between GTS request.
Doc.: IEEE Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Summary.
Submission Title: TG9ma Closing Report for July Meeting
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Dependable Interest Group Closing.
Submission Title: TG9ma Agenda for September Meeting
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: More LB156 Comment Resolution Date Submitted:
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: MLME-SOUNDING and MLME-CALIBRATE comment.
Jan 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TeraHertz Closing Report Date Submitted: January.
Submission Title: TG9ma Closing Report for July Meeting
Submission Title: TG9ma Closing Report for September Meeting
12/15/2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AWGN Simulation Results] Date Submitted:
Presentation transcript:

Jan 2014 Tero Kivinen, INSIDE Secure Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Security PIB Differences Date Submitted: 17 May, 2012 Source: Tero Kivinen, Company: INSIDE Secure Address: Eerikinkatu 28, FI-00180 Helsinki, Finland Voice:+358 20 500 7800, FAX: +358 20 500 7801, E-Mail: kivinen@iki.fi Re: Security PIB Differences Abstract: Pictures describing the changes between 2006 and 2011 security PIB Purpose: How to fix the security in the 2006 and 2011 Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15. Tero Kivinen, INSIDE Secure

Tero Kivinen Los Angeles, CA January 22, 2014 Security PIB Differences between 2006 and 2011, and problem in macFrameCounter Tero Kivinen Los Angeles, CA January 22, 2014 Tero Kivinen, INSIDE Secure

Security PIB differences between 2006 and 2011 Jan 2014 Security PIB differences between 2006 and 2011 Number of Items In 2006 there is List of items and counter for the items (macKeyTableEntries, macDeviceTable Entries etc) In 2011 there is just Sets or Lists no counts Added fields in 2011 SecurityLevelDescriptor has AllowedSecurityLevels field Tero Kivinen, INSIDE Secure

KeyDescriptors KeyIdLookupDescriptor is very different Jan 2014 KeyDescriptors KeyIdLookupDescriptor is very different 2006 has only LookupData and Size 2011 has expanded fields: KeyIdMode, KeySource, KeyIndex, DeviceAddrMode, DevicePANId, DeviceAddress KeyDeviceList removed in 2011 In 2006 it had UniqueDevice, BlackListed DeviceDescriptorHandle was moved to KeyDescriptors level Tero Kivinen, INSIDE Secure

Jan 2014 2006 MAC PIB Tero Kivinen, INSIDE Secure

Jan 2014 2011 MAC PIB Tero Kivinen, INSIDE Secure

Both have problems macFrameCounter is global to device Jan 2014 Both have problems macFrameCounter is global to device FrameCounter is per remote peer Tero Kivinen, INSIDE Secure

macFrameCounter This is global to device Jan 2014 macFrameCounter This is global to device This is used when sending packets out I.e regardless who the device sends packet to or what key is used the counter is incremented. When this reaches 0xffffffff the device needs to rekey all keys Makes using more than one key per device almost useless You cannot for example create multiple keys at once and start using next one when first one needs to be rekeyed. You cannot create separate key for device where you are sending lots of data. Cannot create low volume broadcast key for broadcasts and high volume unicast key for the peer sending lots of data Tero Kivinen, INSIDE Secure

FrameCounter This is per remote peer Jan 2014 FrameCounter This is per remote peer Identified by PANId, ShortAddress, ExtAddress This is used to check the replay attacks, i.e. if incoming FrameCounter from the device is smaller than this it is dropped. This makes it useless to have multiple keys between same peers Tero Kivinen, INSIDE Secure

What should be done macFrameCounter needs to be per key: Jan 2014 What should be done macFrameCounter needs to be per key: should be moved to the KeyDescriptors table. It should be incremented every time key is used. FrameCounter needs to be per key and per remote peer. DeviceDescriptors table should also have keyIndex if KeyIdMode is not 0x00. Tero Kivinen, INSIDE Secure

Why this was not problem earlier Jan 2014 Why this was not problem earlier Only problem if you are using multiple keys between peers, i.e. have KeyIdMode that is not 0x00, and you have multiple KeyIndex values between peers. Might be bigger problem when bigger networks want to use multiple keys and do not want to rekey all of them at the same time Tero Kivinen, INSIDE Secure