1 / 5

Key Management in AAA

Explore the concerns with key management protocols in the security area and their impact on AAA. Learn about acceptable solutions, algorithm independence, confidentiality, replay detection, and more.

plori
Download Presentation

Key Management in AAA

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. Key Management in AAA Russ Housley Incoming Security Area Director

  2. Introduction • Some people are concerned that a working group outside of the Security Area is designing a key management protocols. • Why? • Key management protocols are subtle. • An expert can easily miss a flaw. • Peer review by multiple experts is essential.

  3. Concerns with EAP • Employs new key distribution architecture • Poorly understood security properties • Three party models have been well studied, but these do not align directly with AAA • Select one end-to-end mechanism to protect distributed keys • Needs robust key naming scheme • Needs to establish fresh session keys • Principle of least privilege not followed

  4. Acceptable solution MUST… • Be algorithm independent protocol • For interoperability, select at least one suite of algorithms that MUST be implemented • Establish strong, fresh session keys • Maintain algorithm independence • Include replay detection mechanism • Authenticate all parties • Maintain confidentiality of authenticator • NO plaintext passwords

  5. Acceptable solution MUST also … • Perform client and NAS authorization • Maintain confidentiality of session keys • Confirm selection of “best” ciphersuite • Uniquely name session keys • Compromise of a single NAS cannot compromise any other part of the system, including session keys and long-term keys • Bind key to appropriate context

More Related