1 / 9

Security Framework

Security Framework. Authors:. Date: 2012-07-17. Background. IEEE 802.11 provides cryptographic security using work developed in TGi (2004) Key Establishment / Authentication Pre-Shared Keys 802.1X / EAP / Radius Authentication AES-CCMP for link encryption What are we missing?.

lynngraham
Télécharger la présentation

Security Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Security Framework Authors: Date: 2012-07-17 Paul A. Lambert (Marvell)

  2. Background • IEEE 802.11 provides cryptographic security using work developed in TGi (2004) • Key Establishment / Authentication • Pre-Shared Keys • 802.1X / EAP / Radius Authentication • AES-CCMP for link encryption • What are we missing? Paul A. Lambert (Marvell)

  3. Strong Device-to-Device Authentication • IEEE 802.11 does not have a “good” solution fordevice-to-device authentication • Preshared keys are problematic: • Difficult to install • Poor authentication (can be reshared) • EAP based methods are designed to use a remote server Paul A. Lambert (Marvell)

  4. Device-to-Device AuthenticationPossible Use Cases and Benefits • Simplified secure device discovery • All devices have an provable identity • Enables good peer-to-peer security • Easy device enrollment and installation • Provable identity greatly simplifies installation process • Simplified installation of headless devices (sensors, etc) • Cost and complexity reduced for systems needing centralized authorization Paul A. Lambert (Marvell)

  5. Proposed Framework • Every device has a public / private key • public key is used as identity • Raw key or hash of Key • Certificate, but not requiring a Certificate Authority (CA’s assign names – this is not necessary) • Simple Key Exchange • Preassociation in 802.11 • 4 message exchange • based on well defined cryptographic standards(a few to choose from – ANSI, etc.) • Able to support Suite B Paul A. Lambert (Marvell)

  6. Public Key Based Authentication Key pairs are used in an authentication exchange that proves that an entity “holds” a particular public key • Private Key • Public Key K2 K1 K1 K2 Public Keyscan be openly shared Paul A. Lambert (Marvell)

  7. Simple Device Enrollment • Devices have a identity out-of-the box • Self generated key pair • Binding of wireless authentication to a specific device • Label based on public key • Remote enrollment based on knowing identity Paul A. Lambert (Marvell)

  8. Scalable Access Authorization K2 K1 Can K1 enter network? K1 Access control servers do NOT need to hold any secrets Paul A. Lambert (Marvell)

  9. Straw Poll Would this group support the definition of device-to-device public key authentication mechanisms for IEEE 802.11? yes: no: abstain: Paul A. Lambert (Marvell)

More Related