MAGNET identity management proposal for Personal Networks. Dimitris M. Kyriazanos

Transcription

1 Internatinal Telecmmunicatin Unin MAGNET identity management prpsal fr Persnal Netwrks Dimitris M. Kyriazans PhD Student NTUA Geneva, 5 December 2006

2 Persnal Netwrk - A Definitin A Persnal Netwrk (PN) is the set f all netwrkingcapable devices that smene uses fr persnal purpses including telecmmunicatins, financial transactins, infrmatin, entertainment A PN may be gegraphically distributed (e.g. hme cluster, car cluster, ffice cluster) the clusters are intercnnecting thrugh VPNs frming an verlay netwrk Despite its very dynamic nature, the security requirements f a PN are very strict, because the resurces it intercnnects cntain a significant amunt f persnal infrmatin (like cntact lists, bank accunts, passwrds r varius preferences) Geneva, 5 December

3 Frm a PN Geneva, 5 December

4 t a PN Federatin PN 1 Htel Cluster Hme Cluster User 1 User 5 User 4 User 6 User 1 Access Netwrk Intercnnecting Structure Access Netwrk User 2 Access Netwrk Access Netwrk Office Cluster User 2 PN 2 User 3 member f PN federatin 1 member f PN federatin 2 PN 3 Hme Cluster User 3 Geneva, 5 December

5 Sme definitins Identifier. An identifier distinguishes a distinct entity within the cntext f a specific namespace. Attribute. An attribute is a characteristic assciated with an entity, such as an individual. Identity/ Prfile. In an identity management system, identity is that set f permanent r lng-lived tempral attributes assciated with an entity. Identity management. Identity management is the prcess that ensures secure creatin, strage, exchange and update f digital identity. Geneva, 5 December

6 Identity management: what fr? 1. A supprt t security schemes. 2. A supprt fr mbility and pervasiveness 3. Prtectin f users privacy 4. Mre usable and ergnmically-designed IT systems Geneva, 5 December

7 Identity management: what fr? 1. A supprt t security schemes. 2. A supprt fr mbility and pervasiveness 3. Prtectin f users privacy 4. Mre usable and ergnmically-designed IT systems Geneva, 5 December

8 Hw t supprt security? - An entity in the cyberspace wns many identifiers: IP addresses, MAC addresses, URLs, address, UUID - Opens dr t identity usurpatin, frgery - An entity has t manage credentials/keys fr each cmmunicatin layer, applicatin r radi technlgy. - need fr a unique, primary address that vuches fr all the thers and bund t security credentials Geneva, 5 December

9 Hw t supprt mbility? - In mst cases (layer 3 and abve) mbility = an address change - primary address remains unchanged, while ther addresses act as lcatrs (a HIP-like apprach). N need fr re-authenticatin. - -Same reasning applies als fr vertical handver (Wi-Fi t BT fr instance) Geneva, 5 December

10 Step 1: make it secure - Idea: link an identifier t cryptgraphic material 1.key = f (identifier) - identity-based cryptgraphy 2.Identifier = f (key) - cryptgraphically-generated addresses - What we chse in MAGNET: Identifier= hash (public key) Geneva, 5 December

11 Step 2: design a namespace We assciate a unique ID t PN federatins and PNs cmputed as CBIDgrup=hash(PKgrup) derived by the grup generatr. We als prpse the fllwing structure fr MAGNET namespace: CBID PN-F CBID PN CBID Entity validity/access cntrl The name is certified r used with identity-based cryptgraphy, which brings grup membership prf and address wnership prf. Geneva, 5 December

12 Step 3: link t ther addresses Identity Translatin database (ITD)is used t map the unique MAGNET ID int the usual nes. Primary ID eccd0269a2 IP addresses x.x.x.x y.y.y.y z.z.z.z MAC addresses Other IDs x:x:x:x:x:x y:y:y:y:y:y z:z:z:z:z:z Identity Translatin DB Geneva, 5 December

13 Step 4: link t security assciatins - The Security Relatinships Database (SRD) is used t stre the pairwise keys, referenced by the unique ID f the crrespnding devices. Primary ID PKID bbe7e969b8 5b3ab c3b49280 xxx...x yyy...y zzz...z Pairwise Key Validity xxx yyy zzz 15:38:29,97 06:45:21,66 11:21:29,77 Security Relatinships DB Geneva, 5 December

14 A practical use case: fast vertical HO Geneva, 5 December

15 Identity Management I: Security Prfiles The Prfiles prvide structured infrmatin abut all PN elements and cnceptual entities User infrmatin: the identity, rganizatin, rle, grup membership, areas f interest and preferences f the user. The pair-wise lng term keys Grup infrmatin Service infrmatin Trust level Reputatin Plicies: PN-Federatin credentials, timestamps and related infrmatin. User Rle assciatins Geneva, 5 December

16 Identity Management II: Prfile Management Prfiles will definitely nt remain static. Mbility f users & Prtability f devices. Time-limited memberships and rights. Security crisis (e.g. theft r lss f device) Any changes n the prfiles are suppsed t be passed n t any related plicy management and security applicatins thrughut the PN verlay netwrk dynamically, withut requiring ffline time and (re- )prgramming effrts. The administratr shuld be allwed t dynamically issue new plicies and change existing nes, while being sure that these new plicies are spread and stred securely t any invlved devices thrughut the PN. Geneva, 5 December

17 Identity Management II: Prfile Management Prfile Management Mdules and Prfile Repsitries: Distributed int specific cluster administrative devices, prmting scalability fr the PN. In each master device a plicy management mdule is present, enabling: the master device t act as a plicy fficer fr the devices in his jurisdictin. user plicy administratin ver the entire PN. Plicy registratin ccurs either: Transparently alng with Service, Device r ther Entity registratin (interperatin with SD platfrm and device registratin platfrm), perfrming Plicy registratin. User-driven, ffering plicy management administratr (via XML-driven GUI) capabilities t the Secure peratin: Encryptin f Security Prfiles. Integrity check upn decryptin. Geneva, 5 December

18 Last but mst Imprtant: Privacy! Fur basic guidelines: Ntice: The individual shuld have clear ntice f the type f infrmatin cllected, its use, and an indicatin f third parties ther than the riginal cllectr wh will have access t the data. Chice: The ability t chse nt t have data cllected. Access: The ability fr the data subject t see what persnal infrmatin is held abut him/her, t crrect errrs, and t delete the infrmatin if desired. Security: Reasnable measure taken t secure (bth technically and peratinal) the data frm unauthrized access. Geneva, 5 December

19 Thank yu! Fr mre infrmatin abut MAGNET Beynd prject please visit: Or cntact: Dimitris Kyriazans: Khaled Masmudi: Geneva, 5 December