• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Mutual Authentication For Wireless Communication
 

Mutual Authentication For Wireless Communication

on

  • 4,933 views

it deals how authentication is done for wireless communication.

it deals how authentication is done for wireless communication.

Statistics

Views

Total Views
4,933
Views on SlideShare
4,921
Embed Views
12

Actions

Likes
2
Downloads
0
Comments
0

1 Embed 12

http://www.slideshare.net 12

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Mutual Authentication For Wireless Communication Mutual Authentication For Wireless Communication Presentation Transcript

    • SEMINAR ON MUTUAL AUTHENTICATION FOR WIRELESS COMMUNICATION
      • PRESENTED BY
      • DEEPAK KUMAR
      • IT- ’A’ , S - 7
      • Introduction
      • Mutual Authentication in a wireless nw
      • Types of Mutual Authentication in a wireless nw
      • How to Set-Up Mutual Authentication
      • Mutual Authentication Protocol
      • Attacks on Protocols
      • PKI
      • Advantages of Mutual Authentication
      • Limitations of Mutual Authentication
      • Conclusion
      • References
      • Authentication : -
      • Authentication is the process of verifying identity of an entity.
      • Authentication is used in a system where certain no of users are given authority to access or use the resources .
      • It can also be used in e-commerce .
      • An individual can be authenticated by a no. of ways :-
      • eg.- Using logon-password,
      • Public key Interface, user id- password, etc.
      • Basically there are 3 methods of authentication :-
      • What you have
      • What you are
      • What you know
      • Methods of Authentications :
      • What you have  keys, ID, pass cards, tokens.
      • objects can be taken and are not tied or "signed" to any particular person.
      • objects can be stolen . Keys can be duplicated , IDs can be faked
      • What you are  DNA, fingerprints, voice match, etc.
      • They can not be faked but they can be stolen
      • What you know  Passwords, pass phrases, etc.
      • They cannot be stolen (from your mind), they cannot be duplicated .
      • It only verifies that somebody knows the password.
      • M/A in a wireless n/w Environment
      • Mutual authentication is a process by which both entities a client and a server authenticate each other in a wireless network environment .
      • A connection can occur only when the client trusts the server's digital certificate and the server trusts the client's digital certificate.
      • The exchange of certificates is carried out by means of the Transport Layer Security (TLS) protocol.
      • Once a site has been identified as hostile , the user's computer can be blocked from visiting it or using its features thereafter.
      • How does it work?
      • Types of M/A in a Wireless n/w Environment
      • 1. Certificate-based mutual authentication
      • 2. Username &Password based Mutual Authentication
      • How to Set-Up Mutual Authentication
      • Using a single certificate:-
      •  
      • The problem is once the single certificate is compromised then the whole system is compromised .
      • Using two certificates :-
      Client Web Service Client publicprivate certificate Service publicprivate certificate Service public key Client public key
      • Mutual Authentication Protocols
      • It is also known as Needham – Schroeder public key authentication protocol.
      • 1. A -> AS: IDa, IDb
      • 2. AS -> A: EKrs[Kub, IDb]
      • 3. A -> B: EKub[ Na, IDa]
      • 4. B -> AS: IDb, IDa
      • 5. AS -> B: EKrs[Kua,IDa]
      • 6. B -> A: EKua[IDa, Na, Nb]
      • 7. A -> B: EKub[Nb]
      • Here A and B are the two
      • entities while AS is the
      • Authentication server
      • Goals of Mutual Authentication Protocol
      • Provide Mutual authentication between users or between user and server
      • Minimal information transferred for mutual authentication
      • Password storage protection
      • Password protection during transit over an unsecured network
      • A method transportable to various platforms
      • An easy to use and efficient protocol for secure use over a network
      • Attacks on Mutual Authentication Protocol
      • 1.Privacy attack:-
      • The messages 1 and 4 are not encrypted and are plain text messages. Any intruder monitoring the network can read the message and can infer that A and B trying to communicate with each other. The intruder can also determine how often the two parties communicate and for how long they communicate.
      • 2. Impersonation Attack:-
      • Due to this effect the key used by device can be revoked and one can make his own rule on it.
      • 3. Nuisance attack:-
      • These kinds of attacks do not compromise on security but disrupt the activities of the legitimate user.
      • The encryption protocol is stopped doing its business.
      • It causes several unnecessary communication between entities.
      • Modification to Minimize Attacks on protocols
      • 1. Modification to minimize Privacy attack:-
      • by encrypting the messages.
      • When a user has to send a message to the server he encrypts the message using the public key of the server there by preventing any intruder from reading the message.
      • 2. Modification to minimize Impersonation attack:-
      • In addition to encryption, a nonce is added to the messages.
      • The nonce is returned when the authentication server communicates back to the user.
      • The use of nonce assures user that the response received is current and has been sent from the server.
      • 3. Modification to minimize Nuisance attack:-
      • The use of aliases can reduce the effect of nuisance attack on individual users.
      • This scheme involves the use of an alias ID.
      • Eg.- A broadcasts --> B, KUb[ N1, IDa, ID_a_alias]
      • Alias is a one time randomly genereted no. so it's very hard for a malicious user to correctly guess the alias.
      • MUTUAL AUTHENTICATION VIA CELL PHONE
      • Step 1:- Service provider delivers service on the computer.
      • Step 2:- authentication server authenticates the mobile phone.
      Service provider Authentication Server Service is delivered to the computer Authentication is done over mobile N/W Internet Mobile phone n/w 1 2
      • Step 3:- Phone no is sent from computer to service provider.
      • Step 4:- Authentication server sends OTP over n/w.
      • Step 5:- User enters the OTP.
      Service provider Authentication Server Phone No sent from the computer Authentication server sends OTP over N/W Internet Mobile phone n/w User enters OTP 3 4 5
      • Step 6:- Server sends one time phone No for the client to call for authentication.
      • Step 7:- Server authenticates the user using callers phone No.
      Service provider Authentication Server Server sends OTP1 for the client to call for authentication Server authenticates the user using callers phone No. Internet Mobile phone n/w 6 7
      • Public key Infrastructure(PKI)
      • PKI enables users to exchange information over a communication n/w by use of public and private key pair.
      • PKI uses the public key cryptography which is the most common method for authenticating a message sender or encrypting a msg .
      • cryptography has usually involved the creation and sharing of a secret key for the encryption and decryption of messages.
      • A public key infrastructure consists of:
      PKI Certificate authority (CA) Registration authority (RA) Directories Certificate management system Issues and verifies digital certificates Verifies the certificate authority Hold the certificate with their public keys Manage and control all these things
      • How Do Public and Private Keys Work?
      • A public and private key are created simultaneously by a certificate authority (CA).
      • The private key is given only to the requesting party and the public key is made publicly available in a directory that all parties can access.
      • Step 1:- When a sender sends an encrypted message to receiver then it uses the public key of receiver to encrypt the message.
      • Step 2:- Sender sends an encrypted signature by using private key of sender.
      • Step 3:- When a receiver receives an encrypted message from the sender then it uses its private key of receiver to decrypt the message.
      • (authentication of receiver)
      • Step 4:- Decrypt an encrypted signature by using sender’s public key .
      • (Authentication of sender).
      • Authentication vs. Authorization
      • Similarity:-
      • Both are the two interrelated security concepts.
      • Differences:-
      • 1. Authentication is a process of identifying a user.
      • Authorization is a process of verifying authority of a user to use the resources.
      • 2. Authorization occurs after successful authentication .
      • Advantages of M/A for Wireless Communication
      • It guarantees authenticity of both parties within the same communication session.
      • The method is easy to implement since both parties share the same set of algorithm and it is achieved by exchanging two consecutive one-time passwords.
      • It is useless for a malicious third party to steal a used one-time password because the one-time password has already expired after a single use.
      • The overall scheme provides a high level of security and robustness . 
      • Minimum knowledge is exchanged during authentication.
      • Limitations of M/A for Wireless Communication
      • Its Coding is complex , requiring extensive testing and verification of the protocol.
      •  
      • Policy must prevent compromise of hash function and user password.
      •  
      • A protocol with minimum preliminary knowledge to provide mutual authentication.
      •  
      • A zero-knowledge proof for authentication of each user.
      •  
      • Widest range of protocol implementation over varying operating systems.
      • CONCLUSIONS
      • Thus we have seen that 2 individuals can authenticate each other by mutual authentication. The method provides a very high security from external malicious users and protocols. The process is simple and highly secure because minimum knowledge is exchanged during authentication. Once when Authentication has been established by two entities they authorize each other to access their resources up to a limit .
      • REFERENCES
      • Websites
      • http://docs.sun.com/
      • http://aspadvice.com/blogs/
      • http://www.freepatentsonline.com/
      • http://en.wikipedia.org/
      • http://www.microsoft.com/
      • http://searchfinancialsecurity.techtarget.com/
      • http://developers.sun.com/
      • http://www.acm.org/
      • Books
      • Mutual authentication in wireless networks – Richarad R Joos
      • Authentication and security protocol for mobile computing – Yuliang Zheng
      • Security issues in Mobile computing – N Asokan
      • THANK YOU