 Key exchange o Kerberos o Digital certificates  Certificate authority structure o PGP, hierarchical model  Recovery from exposed keys o Revocation.

Slides:



Advertisements
Similar presentations
Chapter 10 Real world security protocols
Advertisements

Authentication Applications. will consider authentication functions will consider authentication functions developed to support application-level authentication.
Key Management. Shared Key Exchange Problem How do Alice and Bob exchange a shared secret? Offline – Doesnt scale Using public key cryptography (possible)
Key distribution and certification In the case of public key encryption model the authenticity of the public key of each partner in the communication must.
Attacks on cryptography – Cyphertext, known pltext, chosen pltext, MITM, brute-force Types of ciphers – Mix of substitution and transposition – Monoalphabetic,
Cryptography Chapter 7 Part 4 Pages 833 to 874. PKI Public Key Infrastructure Framework for Public Key Cryptography and for Secret key exchange.
Slide 1 Vitaly Shmatikov CS 378 Attacks on Authentication.
Key Exchange – Diffie-Hellman – Symmetric crypto (KDC idea, Needham-Shroeder, Kerberos) – Asymmetric crypto – certificates Stolen keys recovery Group keys.
Cryptography and Network Security Third Edition by William Stallings Lecture slides by Lawrie Brown.
1 Supplement III: Security Controls What security services should network systems provide? Confidentiality Access Control Integrity Non-repudiation Authentication.
COEN 350: Network Security Authentication. Between human and machine Between machine and machine.
Computer Security: Principles and Practice EECS710: Information Security Professor Hossein Saiedian Fall 2014 Chapter 23: Internet Authentication Applications.
Chapter 14 From Cryptography and Network Security Fourth Edition written by William Stallings, and Lecture slides by Lawrie Brown, the Australian Defence.
Http Web Authentication Web authentication is used to verify a users identity before allowing access to certain web pages On web browsers you get a login.
Lecture 23 Internet Authentication Applications
1 Pertemuan 12 Authentication, Encryption, Digital Payments, and Digital Money Matakuliah: M0284/Teknologi & Infrastruktur E-Business Tahun: 2005 Versi:
Environmental Council of States Network Authentication and Authorization Services The Shared Security Component February 28, 2005.
Kerberos Jean-Anne Fitzpatrick Jennifer English. What is Kerberos? Network authentication protocol Developed at MIT in the mid 1980s Available as open.
Core Web Service Security Patterns
 Authentication o Something you know (password) o Something you have (smartcard) o Something about you (iris scan)  Password authentication o To protect.
 Authorization via symmetric crypto  Key exchange o Using asymmetric crypto o Using symmetric crypto with KDC  KDC shares a key with every participant.
1 Authentication Applications Digital Signatures Security Concerns X.509 Authentication Service Kerberos Based on slides by Dr. Lawrie Brown of the Australian.
Introduction to PKI Seminar What is PKI? Robert Brentrup July 13, 2004.
Online Security Tuesday April 8, 2003 Maxence Crossley.
Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE USC CSci530 Computer Security Systems Lecture.
Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE CSci530: Computer Security Systems Authentication.
Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE CSci530: Computer Security Systems Authentication.
Copyright © Clifford Neuman - UNIVERSITY OF SOUTHERN CALIFORNIA - INFORMATION SCIENCES INSTITUTE CSci530: Computer Security Systems Authentication.
Key Management. Shared Key Exchange Problem How do Alice and Bob exchange a shared secret? Offline – Doesn’t scale Using public key cryptography (possible)
1 Authentication Protocols Celia Li Computer Science and Engineering York University.
Computer Science Public Key Management Lecture 5.
Authentication and Identity Management. Ideally – Who you are Practically – Something you know (e.g., password) – Something you have (e.g., badge) – Something.
Strong Password Protocols
IDENTITY MANAGEMENT Hoang Huu Hanh (PhD), OST – Hue University hanh-at-hueuni.edu.vn.
Part Two Network Security Applications Chapter 4 Key Distribution and User Authentication.
Networks and Security. Types of Attacks/Security Issues  Malware  Viruses  Worms  Trojan Horse  Rootkit  Phishing  Spyware  Denial of Service.
SYSTEM ADMINISTRATION Chapter 13 Security Protocols.
Masud Hasan Secue VS Hushmail Project 2.
Cryptography and Network Security Chapter 14 Fifth Edition by William Stallings Lecture slides by Lawrie Brown.
Identity Management Report By Jean Carreon and Marlon Gonzales.
Lecture 23 Internet Authentication Applications modified from slides of Lawrie Brown.
Lecture 11: Strong Passwords
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 22 – Internet Authentication.
David Evans CS150: Computer Science University of Virginia Computer Science Class 31: Cookie Monsters and Semi-Secure.
E-Commerce Security Professor: Morteza Anvari Student: Xiaoli Li Student ID: March 10, 2001.
Unit 1: Protection and Security for Grid Computing Part 2
Authentication Applications Unit 6. Kerberos In Greek and Roman mythology, is a multi-headed (usually three-headed) dog, or "hellhound” with a serpent's.
1 Securing Data and Communication. 2 Module - Securing Data and Communication ♦ Overview Data and communication over public networks like Internet can.
Authentication 3: On The Internet. 2 Readings URL attacks
Fall 2010/Lecture 321 CS 426 (Fall 2010) Key Distribution & Agreement.
CSCE 522 Identification and Authentication. CSCE Farkas2Reading Reading for this lecture: Required: – Pfleeger: Ch. 4.5, Ch. 4.3 Kerberos – An Introduction.
X.509 Topics PGP S/MIME Kerberos. Directory Authentication Framework X.509 is part of the ISO X.500 directory standard. used by S/MIME, SSL, IPSec, and.
Kerberos By Robert Smithers. History of Kerberos Kerberos was created at MIT, and was named after the 3 headed guard dog of Hades in Greek mythology Cerberus.
COEN 350: Network Security Authentication. Between human and machine Between machine and machine.
Key Management. Shared Key Exchange Problem How do Alice and Bob exchange a shared secret? Offline – Doesn’t scale Using public key cryptography (possible)
Identification Authentication. 2 Authentication Allows an entity (a user or a system) to prove its identity to another entity Typically, the entity whose.
1 Chapter 10: Key Management in Public key cryptosystems Fourth Edition by William Stallings Lecture slides by Lawrie Brown (Modified by Prof. M. Singhal,
Security fundamentals Topic 5 Using a Public Key Infrastructure.
© Copyright 2009 SSLPost 01. © Copyright 2009 SSLPost 02 a recipient is sent an encrypted that contains data specific to that recipient the data.
Key Management Network Systems Security Mort Anvari.
User Authentication  fundamental security building block basis of access control & user accountability  is the process of verifying an identity claimed.
Dos and Don’ts of Client Authentication on the Web Kevin Fu, Emil Sit, Kendra Smith, Nick Feamster Presented: Jesus F. Morales.
Fall 2006CS 395: Computer Security1 Key Management.
1 SUBMITTED BY- PATEL KUMAR C.S.E(8 th - sem). SUBMITTED TO- Mr. DESHRAJ AHIRWAR.
@Yuan Xue Case Study (Mid-term question) Bob sells BatLab Software License Alice buys BatLab Credit card information Number of.
Secure HTTP (HTTPS) Pat Morin COMP 2405.
Web Applications Security Cryptography 1
Key Management.
Cryptography and Network Security
Presentation transcript:

 Key exchange o Kerberos o Digital certificates  Certificate authority structure o PGP, hierarchical model  Recovery from exposed keys o Revocation lists, time-limited keys, real time validation  Group key management o Robustness, forward/backward secrecy

 Ideally o Who you are  Practically o Something you know o Something you have o Something about you

 Password or Algorithm o e.g. encryption key derived from password  Issues o Someone else may learn it  Find it, sniff it, trick you into providing it o Other party must know how to check o You must remember it

 Alice inputs her password, computer verifies this against list of passwords  If computer is broken into, hackers can learn everybody’s passwords o Use one-way functions, store the result for every valid password o Perform one-way function on input, compare result against the list

 Hackers can compile a list of frequently used passwords, apply one-way function to each and store them in a table – dictionary attack  Host adds random salt to password, applies one-way function to that and stores result and salt value o Randomly generated, unique and long enough

 Someone sniffing on the network can learn the password  Lamport hash or S-KEY – time-varying pass o To set-up the system, Alice enters random number R o Host calculates x 0= h(R), x 1= h(h(R)), x 2= h(h(h(R))),..., x 100 o Alice keeps this list, host sets her password to x 101 o Alice logs on with x 100, host verifies h(x 100 )=x 101, resets password to x 100 o Next time Alice logs on with x 99

 Someone sniffing on the network can learn the password o Host keeps a file of every user’s public key o Users keep their private keys o When Alice attempts to log on, host sends her a random number R o Alice encrypts R with her private key and sends to host o Host can now verify her identity by decrypting the message and retrieving R

 Key Distribution o Confidentiality not needed for public key o Solves n 2 problem  Performance o Slower than conventional cryptography o Implementations used for key distribution, then use conventional crypto for data encryption  Trusted third party still needed o To certify public key o To manage revocation o In some cases, third party may be off-line

 Passport  Liberty Alliance  Shibboleth

 Two versions of Passport o Centralized and federated  Liberty Alliance o Loosely federated with framework to describe authentication provided by others

 Goal is single sign-on o Solves problem of weak or repeated user/pass combinations  Implemented via redirections o Users authenticate themselves to a common server, which gives them tickets o Similar flavor to Kerberos but different environment – many organizations  Widely deployed by Microsoft o Designed to use existing technologies in servers/browsers (HTTP redirect, SSL, cookies, Javascript)

 Client (browser), merchant (Web server), Passport login server  Passport server maintains authentication info for client o Gives merchant access when permitted by client  Divides client data into profile (address) and wallet (credit card) David P. Kormann and Aviel D. Rubin, Risks of the Passport Single Signon Protocol, Computer Networks, Elsevier Science Press, volume 33, pages 51-58, 2000.

David P. Kormann and Aviel D. Rubin, Risks of the Passport Single Signon Protocol, Computer Networks, Elsevier Science Press, volume 33, pages 51-58, SSL Token = 3DES encrypted authentication info using key merchant shares with passport server Also set cookie at browser

 User interface is confusing and may misrepresent the reality  Weak keys may be used for 3DES  Single key is used to encrypt cookies for all clients  Cookies stay on machine, can be stolen o No authenticator (timestamp), like in Kerberos, enables reuse by others  Coupling of Hotmail with Passport David P. Kormann and Aviel D. Rubin, Risks of the Passport Single Signon Protocol, Computer Networks, Elsevier Science Press, volume 33, pages 51-58, Read more at

 Multiple federated identity providers o E.g. ISPs register own users o One can rely on claims made by other ID providers  Claims o s, relationships, authorization for scenarios, ownership of private/public key pair  Need “translators” for different claim languages

 Design criteria was most of the issues addressed by Federated Passport, i.e. no central authority  Use SAML (Security Association Markup Language) to describe trust across authorities, and what assertions mean from particular authorities  Four assurance levels o How much we trust a given identity assertion o Little, some, high and very high confidence