1 / 11

What is network security?

What is network security?. Confidentiality: only sender, intended receiver should “understand” message contents sender encrypts message receiver decrypts message Authentication: sender, receiver want to confirm identity of each other

gilles
Download Presentation

What is network security?

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. What is network security? Confidentiality: only sender, intended receiver should “understand” message contents • sender encrypts message • receiver decrypts message Authentication: sender, receiver want to confirm identity of each other Message Integrity: sender, receiver want to ensure message not altered (in transit, or afterwards) without detection Non-repudiation: receiver want to ensure message must have come from claimed sender Access and Availability: services must be accessible and available to (legitimate) users (e.g. no DoS)

  2. Alice Bob data, control messages channel secure sender secure receiver data data Trudy Friends and enemies: Alice, Bob, Trudy • Alice, Bob, and Trudy well-known short hands in network security world • Bob, Alice want to communicate “securely” • Trudy (intruder) may intercept, delete, add messages Q: What can a “bad guy” do? • eavesdrop: intercept messages • actively insert messages into connection • impersonation: can fake (spoof) source address in packet (or any field in packet) • hijacking: “take over” ongoing connection by removing sender or receiver, inserting himself in place • denial of service: prevent service from being used by others (e.g., by overloading resources)

  3. K K A-B A-B encryption algorithm decryption algorithm ciphertext plaintext plaintext message, m K (m) A-B K (m) A-B m = K ( ) A-B The language of cryptography public-key crypto: encryption key public, decryption key secret (private) symmetric key crypto: sender, receiver keys identical. Key used to encrypt and decrypt message. Symmetric key cryptography symmetric key crypto: Bob and Alice share same (symmetric) key: K • e.g., key is knowing substitution pattern in mono alphabetic substitution cipher • Bob and Alice agree on key value using the Diffie-HellmanKey Exchange

  4. + Bob’s public key K B - Bob’s private key K (K (m)) = m K B B B - + 2 1 + K (m) B encryption algorithm decryption algorithm plaintext message plaintext message, m ciphertext - + m = K (K (m)) B B Public Key Cryptography need K ( ) and K ( ) such that public key cryptography • sender, receiver do not share secret key • public encryption key known to all • private decryption key known only to receive Requirements - + + given public key K , it should be impossible to compute private key K B B B - B

  5. + K (m) B Alice’s IP address “I am Alice” Authentication Symmetric vs Public key encryption: There is no guarantee that the message came from Alice, since anyone can send public key encrypted to Bob, In contrast, in symmetric key encryption the sender is implicitly identified to the receiver. Goal: Bob wants Alice to “prove” her identity to him Alice says “I am Alice” in an IP packet containing her source IP address Failure scenario?? Trudy can create a packet “spoofing” Alice’s address

  6. - K (R) A + + K K A A - - + (K (R)) = R K (K (R)) = R A A A Authentication: • can we authenticate using public key techniques? use of nonce, public key cryptography “I am Alice” Bob computes R and knows only Alice could have the private key, that encrypted R such that “send me your public key”

  7. We all often signs documents (checks, credit card receipts, legal documents, …). How to sign electronic documents? Public key cryptographic technique analogous to hand-written signatures. sender (Bob) digitally signs document, establishing he is document owner/creator. verifiable, non-forgeable: recipient (Alice) can prove to someone that Bob, and no one else (including Alice), must have signed document Simple digital signature for message m: Bob signs m by encrypting with his private key KB, creating “signed” message, KB(m) - - K K B B Bob’s private key Bob’s message, m (m) Dear Alice Oh, how I have missed you. I think of you all the time! …(blah blah blah) Bob Bob’s message, m, signed (encrypted) with his private key Public key encryption algorithm Message integrity :Digital Signatures - -

  8. Suppose Alice receives msg m, digital signature KB(m) Alice verifies m signed by Bob by applying Bob’s public key KB to KB(m) then checks KB(KB(m) ) = m. If KB(KB(m) ) = m, whoever signed m must have used Bob’s private key. Alice thus verifies that: Bob signed m. No one else signed m. Bob signed m and not m’. Non-repudiation: Alice can take m, and signature KB(m) to court and prove that Bob signed m. Digital Signatures (more) - - - + + - + -

  9. Symmetric key problem: How do two entities establish shared secret key over network? Solution: trusted key distribution center (KDC) acting as intermediary between entities Public key problem: When Alice obtains Bob’s public key (from web site, e-mail, diskette), how does she know it is Bob’s public key, not Trudy’s? Solution: trusted certification authority (CA) Trusted Intermediaries • Alice, Bob need shared symmetric key. • KDC: server shares different secret key with each registered user (many users) • Alice, Bob know own symmetric keys, KA-KDC KB-KDC , for communicating with KDC.

  10. KDC generates R1 KA-KDC(A,B) KDC Alice knows R1 KA-KDC(R1, KB-KDC(A,R1) ) Bob knows to use R1 to communicate with Alice KA-KDC KB-KDC KX-KDC KY-KDC KP-KDC KB-KDC KP-KDC KA-KDC KZ-KDC KB-KDC(A,R1) Alice and Bob communicate: using R1 as session key for shared symmetric encryption Key Distribution Center (KDC) Q: How does KDC allow Bob, Alice to determine shared symmetric secret key to communicate with each other?

  11. + + + + digital signature (decrypt) K K digital signature (encrypt) K K B B B B Bob’s public key CA private key certificate for Bob’s public key, signed by CA - Bob’s identifyinginformation K K CA CA Certification Authorities • Certification authority (CA): binds public key to particular entity, E. • E (person, router) registers its public key with CA. • E provides “proof of identity” to CA. • CA creates certificate binding E to its public key. • certificate containing E’s public key digitally signed by CA – CA says “this is E’s public key” • When Alice wants Bob’s public key: • gets Bob’s certificate (Bob or elsewhere). • apply CA’s public key to Bob’s certificate, get Bob’s public key Bob’s public key CA public key +

More Related