March 2019 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Security vs. Sequence Length Considerations]

Slides:



Advertisements
Similar presentations
doc.: IEEE <doc#>
Advertisements

<month year> <doc.: IEEE doc>
<month year> <doc.: IEEE doc>
November 2017 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [AES-256 for ] Date Submitted:
<month year> doc.: IEEE < e>
<month year> doc.: IEEE < e>
June 2006 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Scenarios for Usage Model Document.
<doc.: IEEE −doc>
<month year> doc.: IEEE < e>
<month year> doc.: IEEE < e>
July 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [SRDEV PPDU for Enhanced Impulse Radio] Date.
<month year> <doc.: IEEE doc> March 2011
<month year> doc.: IEEE < e> <March 2018>
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part
July 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [SRDEV HRP PHY Step 1 Consensus – Baseline.
March 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Secure RF Ranging] Date Submitted: [5 March,
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>
doc.: IEEE <doc#>
June 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: ax and HRP_LRP Coexistence Date.
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: z Comments on ax Coexistence Assurance.
Date Submitted: [26-Oct-2005]
July 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [SRDEV Evaluation Criteria] Date Submitted:
Submission Title: [Errors in a] Date Submitted: [18 March, 2010]
May 2007 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: OFDM PHY Proposal Date Submitted: 7 May 07.
November 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [MAC for Secure Ranging] Date Submitted:
<month year> doc.: IEEE < e>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Comments on proposed HRP enhancements by NXP and DW]
January 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [MAC for Secure Ranging] Date Submitted:
doc.: IEEE <doc#>
Submission Title: [HRP UWB PHY enhanced mode converged consensus]
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part
doc.: IEEE <doc#>
Date Submitted: [26-Oct-2005]
<month year> <doc.: IEEE doc> September 2015
doc.: IEEE <doc#>
Submission Title: Validation and Verification Task Force Proposal
November 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [MAC Considerations] Date Submitted: [12.
January 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [MAC for Secure Ranging] Date Submitted:
doc.: IEEE <doc#>
<month year>20 Jan 2006
<month year> <doc.: IEEE doc> January 2013
Submission Title: [Secure Ranging Definitions and Interoperability]
doc.: IEEE <doc#>
doc.: IEEE <doc#>
doc.: IEEE <doc#>
<month year> <doc.: IEEE doc> September 2015
doc.: IEEE <doc#>
May 2018 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: z Comments on ax Coexistence Assurance.
March 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [DF6 Radio-burst length over PSDU size] Date.
<month year> doc.: IEEE < e> <March 2018>
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Agenda for TG4z EIR t for May.
doc.: IEEE <doc#>
doc.: IEEE <doc#>
Submission Title: [Proposed Resolution for FSK/GFSK Prior Comments]
Submission Title: [SFD comparison] Date Submitted: [18−July−2006]
<month year> doc.: IEEE < e>
Submission Title: [SFD comparison] Date Submitted: [18−July−2006]
<month year> doc.: IEEE <030158r0> <March 2003>
<author>, <company>
<month year> doc.: IEEE < e>
June, 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [OFDM PHY Mode Representation] Date Submitted:
doc.: IEEE <doc#>
May 2010 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Proposed Resolution To The FCC Part
<author>, <company>
July 2009 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Flexible DSSS Merging Effort] Date Submitted:
Jul 12, /12/10 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Dependable Interest Group Closing.
<month year> doc.: IEEE s September 2019
Presentation transcript:

March 2019 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Security vs. Sequence Length Considerations] Date Submitted: [12 March, 2019] Source: [Jaroslaw Niewczas (Decawave), Billy Verso (Decawave), Tony Fagan (Decawave), Frank Leong (NXP Semiconductors), Jochen Hammerschmidt (Apple), Brima Ibrahim (NXP Semiconductors), Eren Sasoglu (Apple), Daniel Knobloch (BMW), Thomas Reisinger (Continental)] Re: [Input to the Task Group] Abstract: [Presentation, HRP, PHY, STS, Channel Sounding, Enhanced Impulse Radio] Purpose: [] 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. Decawave, NXP, Apple, BMW, Continental

Security vs. Sequence Length Considerations <month year> doc.: IEEE 802.15-<doc#> March 2019 Security vs. Sequence Length Considerations Decawave, NXP, Apple, BMW, Continental <author>, <company>

March 2019 EXECUTIVE SUMMARY A desired security level (e.g., equivalent to 32 bits, 64 bits, 128 bits) can be obtained using varying cipher sequence lengths, from short to long, by selecting the acceptance threshold at the receiver appropriately Decawave, NXP, Apple, BMW, Continental

March 2019 INTRODUCTION The “secure ranging” signalling feature of the 802.15.4z UWB PHYs is based on: Transmission of very short-lasting (~2ns) pulses (carrying bit-information), which cannot be so quickly detected and manipulated by the attacker. Due to this shortness, the exact moment of the pulse reception accurately determines the distance between the devices Using strong cryptographic algorithms to generate a stream of encrypted, pseudo-random bits, modulating the UWB transmission Ensuring that the entropy of the solution is large enough to achieve immunity against distance reducing attacks Decawave, NXP, Apple, BMW, Continental

March 2019 UWB SECURE EXCHANGE Example Scenario: Transmitter/receiver both cryptographically generate local copies of the same bit-stream, based on mutually pre-agreed parameters (KEYS and NONCES). The bit-stream shall be a sequence of +1s and -1s, mapped to pulse phases (polarities) or carrier frequencies Example: Random sequence of pulse polarities {-1, +1} Decawave, NXP, Apple, BMW, Continental

March 2019 IDENTIFYING 1st PATH Multiple approaches exist by which the 1st path in the Channel Impulse Response (CIR) may be evaluated. Method 1 (subject of our analysis): The (periodic) preamble may be used to build up a CIR estimate, from which the first path is extracted and verified using a ciphered sequence. Method 2: A ciphered sequence may be used to (both) build up a CIR estimate and verify the first path within this estimate. Decawave, NXP, Apple, BMW, Continental

DEFINITION: “MATCH LEVEL” March 2019 DEFINITION: “MATCH LEVEL” When receiving the transmitted bit sequence, the receiver compares it to the locally generated reference. The threshold on the “match level” between the copies will determine if the ranging message will be accepted or not. A 100% match level means that all the received bits accurately matched the locally generated reference. A 50% match level means that half of the bits matched the reference and the other half had the opposite sign. Decawave, NXP, Apple, BMW, Continental

SECURITY vs. SEQUENCE LENGTH & MATCH LEVEL March 2019 SECURITY vs. SEQUENCE LENGTH & MATCH LEVEL The security level will depend on the length of the ciphered sequence, which determines the number of all possible bit combinations. However, security level will also depend on the number of bit combinations which will trigger the acceptance of the ranging exchange by the receiver. Let’s assume length-32 cipher and that the receiver will only accept the 1-st path if the similarity level is 100%. There are 232 bit combinations possible and only ONE of them can result in the acceptance. Therefore probability of false acceptance due to reception of random noise (or the attacker’s actions) is 2-32 = 2.3283e-10. If the receiver sets the similarity threshold at 96.9% (accepting the ranging exchange with 31 or 32 bits matching the reference), there will be 1+32=33 bit combinations which satisfy this criterion, and the probability of a random sequence meeting the threshold is 33/232 = 2-26.956 = 7.6842e-09. Decawave, NXP, Apple, BMW, Continental

SECURITY LEVEL TRADE-OFFS March 2019 SECURITY LEVEL TRADE-OFFS It is clear that increasing the sequence length will increase the security and lowering the acceptance threshold will reduce it Both the cipher sequence length and the acceptance threshold on the Match Level will determine the security (thus, the probability of false 1st-path detection) The probabilities of false 1st path detection can be computed for any sequence length and any acceptance threshold level Decawave, NXP, Apple, BMW, Continental

FALSE 1st PATH DETECTION PROBABILITIES March 2019 FALSE 1st PATH DETECTION PROBABILITIES Decawave, NXP, Apple, BMW, Continental

Guessability Consideration March 2019 Guessability Consideration The equivalence between the security level of short vs long sequence along with suitable thresholds may seem counter-intuitive. For example, it may appear impossible to predict 120 out of 128 bits (90%) while correctly choosing 2500 out of 4096 (61% of the bits) seems much more achievable with a bit of luck. In reality, the probability of the former being successful is ~10-22, while the success rate of the latter is ~10-45. When attempting to predict 4096 bits, in only 1% of the attempts, the number of correctly predicted bits will be above 52% and in just 0.01% attempts – above 53%. Decawave, NXP, Apple, BMW, Continental

March 2019 CONCLUSION Identical PHY-layer security levels can be obtained using various cipher sequence lengths with appropriate decision-making criteria at the receiver. Decawave, NXP, Apple, BMW, Continental