1 / 24

Message Authentication

Message Authentication. Network Security. Message Authentication. Objectives of the Topic After completing this topic, a student will be able to explain message authentication approaches. Message Authentication. Figures and material in this topic have been adapted from

gibbons
Download Presentation

Message Authentication

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. Message Authentication Network Security

  2. Message Authentication Objectives of the Topic • After completing this topic, a student will be able to • explain message authentication approaches.

  3. Message Authentication Figures and material in this topic have been adapted from • “Network Security Essentials : Applications and Standards”, 2014, by William Stallings.

  4. Message Authentication • Encryption protects against passive attack (eavesdropping). • Protection against active attack (falsification of data and transactions) is known as message authentication.

  5. Message Authentication • Message authentication is a procedure that allows communicating parties to verify that received messages, file, document, or other collection of data are authentic.

  6. Message Authentication • There are two important aspects: • to verify that the contents of the message have not been altered, and • to verify that the source is authentic.

  7. Message Authentication • Also, we would like to verify a message’s timeliness (it has not been artificially delayed and replayed) and sequence relative to other messages flowing between two parties. • These are related to data integrity.

  8. Message Authentication Authentication Using Encryption • We can perform authentication by the use of symmetric encryption.

  9. Message Authentication • We assume that only the sender and receiver share a key, so only the genuine sender would be able to encrypt a message successfully.

  10. Message Authentication • The receiver assumes that no alterations have been made and that sequencing is proper if the message includes an error detection code and a sequence number.

  11. Message Authentication • If the message includes a timestamp, the receiver is assured that the message has not been delayed beyond that normally expected for network transit.

  12. Message Authentication Authentication without Encryption • An authentication tag is generated and appended to each message for transmission.

  13. Message Authentication • The message itself is not encrypted and can be read at destination independent of the authentication function. • Because the message is not encrypted, message confidentiality is not provided.

  14. Message Authentication • We can combine encryption of a message and its authentication tag in a single algorithm. • Typically, message authentication is provided as a separate function from message encryption.

  15. Message Authentication Message Authentication Code (MAC) • Is a technique that involves the use of a secret key to generate a small block of data, known as a message authentication code , that is appended to the message.

  16. Message Authentication • MAC assumes that two communicating parties, say A and B, share a common secret key KAB.

  17. Message Authentication • When A has a message to send to B, it calculates the message authentication code as a function of the message and the key: MACM = F(KAB , M ).

  18. Message Authentication • The message plus code are transmitted to the intended recipient.

  19. Message Authentication • The recipient performs the same calculation on the received message, using the same secret key, to generate a new message authentication code. • The received code is compared to the calculated code.

  20. Message Authentication

  21. Message Authentication • If we assume that only the receiver and the sender know the identity of the secret key, and if the received code matches the calculated code, then:

  22. Message Authentication • 1. The receiver is assured that message has not been altered. • Attacker does not know the secret key. If message is altered but code remains the same, then receiver’s calculation of the code will differ from the received code.

  23. Message Authentication • 2. The receiver is assured that the message is from the alleged sender. • 3. If the message includes a sequence number, then the receiver can be assured of the proper sequence.

  24. Message Authentication • The NIST specification, FIPS PUB 113, recommends the use of DES. • DES is used to encrypt the message, and the last number of bits of ciphertext are used as the code. • A 16- or 32-bit code is typical. End

More Related