210 likes | 220 Views
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: Security-Privacy Introduction and Overview Date Submitted: May, 2001 Source: William A. Arbaugh Company: University of Maryland Address:
E N D
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: IEEE802.15.3: Security-Privacy Introduction and Overview Date Submitted: May, 2001 Source: William A. Arbaugh Company: University of Maryland Address: Voice: +1.301.455-2774, E-Mail: waa@cs.umd.edu Re: [ ] Abstract: Security and Privacy principles Purpose: 1) To inform the IEEE 802.15.3 about fundamental security and privacy issues in wireless personal area networks. 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 these viewgraphs become(s) the property of IEEE and may be made publicly available by P802.15.
Security/Privacy Introduction and Overview William A. Arbaugh waa@cs.umd.edu
Talk Outline • Introduction • Roadmap • Scenarios • Preliminary threat analysis • Preliminary requirement analysis
Some beginning thoughts • “Security is a process” • “Cryptography is not security” • “To be effective, security must be transparent”
You can never have 100% • Security is all about Risk Management
Similarities to 802.11 but… • WPAN is a much more difficult problem • CPU constraints • Power constraints • Memory constraints • Cost constraints • Infrastructure issues • The end points in 802.11 are hosts.
Security Architecture Elements • Integrity • Source of data, i.e. prevent datagram forgeries • Data content, i.e. prevent data modification • Confidentiality • How long does the data need to remain protected? • Authentication
Trusted Element • What is it? • Most every day transactions have a common trusted element to them. • Establishing a trusted element with each scenario is one of the most difficult aspects of a security architecture for WPAN.
Roadmap • Define scenarios • Develop threat model • Define requirements • Develop architecture • External review
Scenarios • Consumer • Peripherals • Photo frames • Trade show • Exchange info • Exchange proprietary info
Scenarios cont. • Trading floor / Auctions • Bids public, but need non-repudiation • Settlement • Kiosks/commerce
Threat Classes • Class I • Clever outsiders that attempt to take advantage of existing system weaknesses. Access to moderately sophisticated equipment is assumed. • Class II • Knowledgeable insiders with detailed information about various parts of the system, and they may have access to sophisticated equipment.
Threat Classes cont. • Class III • Funded organizations able to assemble specialized teams with access to extremely sophisticated equipment.
Threat and Requirements • The next few slides present a “straw man” for both the threat and security requirements for each scenario. They are designed to be the starting point for discussions.
Trade Show Threat Model • It would be nice, but establishing a common trust element is too dificult.
Requirements • A single solution WILL NOT meet all of the potential requirements. • Choices (all have draw backs) • Engineer to the strongest requirements • Implement a security association mechanism • Provide minimal support (Class I protection) in .15 and meet stronger requirements with upper layers
Now What? • Committee should agree on a set of scenarios representing typical WPAN usage. • Committee agrees on a threat model for each scenario. • Committee agrees on security requirements for each scenarios. • Architecture developed based on the above. • Architecture submitted for external review.
Conclusions • Security is a process and must be viewed holistically with the rest of the system. • Security must be designed into the system from the beginning.