Message Integrity and Authentication
Message Integrity and Authentication
and
Message Authentication
Objectives
Checking integrity
Message Authentication
⚫ message authentication is concerned with:
◦ protecting the integrity of a message
◦ validating identity of originator
◦ non-repudiation of origin (dispute resolution)
⚫ will consider the security requirements
⚫ then three alternative functions used:
◦ message encryption
◦ message authentication code (MAC)
◦ hash function
Message Authentication Functions
⚫Message Encryption
⚫Message Authentication Code (MAC)
⚫Hash Function
Symmetric Message Encryption
⮚ encryption can also provides authentication
⮚ if symmetric encryption is used then:
● receiver know sender must have created it
…since only sender and receiver know key used
● know content are not altered...
... if message has suitable structure, redundancy
or a suitable checksum to detect any changes
Public-Key Message Encryption
⮚ if public-key encryption is used:
● encryption provides no confidence of sender
• since anyone potentially knows public-key
● however if
• sender signs message using their private-key
• then encrypts with recipients public key
• have both secrecy and authentication
11.22
Preimage Resistance
11.23
Second Preimage Resistance
11.24
Collision Resistance
11.25
Nested MAC
Nested MAC
Hashed MAC (HMAC)
⮚NIST has issued a standard (FIPS 198) for
nested MAC that is often referred to as
HMAC (Hashed MAC)
⮚The implementation of HMAC is much
more complex than the simplified nested
MAC.
⮚Additional features such as padding
HMAC
Details of HMAC
Cipher based MAC (CMAC)
⮚NIST has defined a standard (FIPS 113)
called Data Authentication Algorithm (DAA)
or CMAC or CBCMAC.
⮚The method is similar to CBC mode of
operation of symmetric block cipher.
CMAC