1 / 7

Enhanced RADIUS Attributes for Secure Key Exchange in ERP Systems

This draft introduces new RADIUS attributes to facilitate key exchange between visited and home domains in ERP systems, involving AAA server requests, key responses, and EAP exchanges. Security considerations include IPsec and keywrap techniques. Presented at HOKEY WG with future steps outlined.

stefano-carton
Télécharger la présentation

Enhanced RADIUS Attributes for Secure Key Exchange in ERP Systems

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. draft-gaonkar-radext-erp-attrs-00 Kedar Gaonkar Lakshminath Dondeti

  2. New RADIUS attributes • a visited domain AAA server requesting a key • Key Request • The home domain (AS) delivering the key • Key Response

  3. ERP Exchange with Local Re-auth Server Local Re-auth Server Peer Auth1 Auth2 AS Initial EAP Exchange Full EAP Exchange MSK, EMSK, DSRK MSK, EMSK, DSRK1, DS-rRK1, DS-rIK1 EAP Success EAP Success EAP Success (MSK) (MSK, VMSK1) MSK DSRK1, DS-rRK1, DS-rIK1 Subsequent EAP-ER Exchange EAP Request Identity (Optional message) EAP Re-auth Initiate (authenticated with L-rIK1) rMSK11 EAP Re-auth Finish (authenticated with L-rIK1) (rMSK11) rMSK11 rMSK11

  4. Key-Request Attribute Type Length Key-Type Requesting Entity’s Identity (String) … Key Type: 0 : Reserved 1 : Domain Specific Root Key (DSRK)

  5. Key-Response attribute Type Length Key type Key Length Key Lifetime (4 octets) …… Key Name (8 octets) …… Key (Variable) … ... Requesting Entity’s Identity (String, Variable) … …

  6. Security Considerations • The draft at the moment says use IPsec • There was discussion on this topic • End-to-end encapsulation using keywrap • The technique of the keyreq document can be used with these attributes as well

  7. Next Steps • We presented this at the HOKEY WG • After a brief discussion, it appears that we can use draft-zorn-radius-keywrap-13 • We have one more use case for that I-D now

More Related