Message authentication code

Message authentication code (MAC), sometimes known as a tag, is a short piece of information used to authenticate a message—in other words, to confirm that the message came from the stated sender (its authenticity) and has not been changed. The MAC value protects both a message’s as well as its authenticity, by allowing verifiers (who also possess the secret key) to detect any changes to the message content.



Informally, a message authentication code consists of three algorithms:

  • A key generation algorithm selects a key from the key space uniformly at random.
  • A signing algorithm efficiently returns a tag given the key and the message.
  • A verifying algorithm efficiently verifies the authenticity of the message given the key and the tag. That is, return accepted when the message and tag are not tampered with or forged, and otherwise return rejected.

For a secure unforgeable message authentication code, it should be computationally infeasible to compute a valid tag of the given message without knowledge of the key, even if for the worst case, we assume the adversary can forge the tag of any message except the given one.

Formally, a message authentication code (MAC) is a triple of efficient algorithms (G, S, V) satisfying:

  • G (key-generator) gives the key k on input 1n, where n is the security parameter.
  • S (signing) outputs a tag t on the key k and the input string x.
  • V (verifying) outputs accepted or rejected on inputs: the key k, the string x and the tag t. S and V must satisfy the following:
Pr [ kG(1n), V( k, x, S(k, x) ) = accepted ] = 1.

A MAC is unforgeable if for every efficient adversary A

Pr [ kG(1n), (x, t) ← AS(k, · )(1n), x ∉ Query(AS(k, · ), 1n), V(k, x, t) = accepted] < negl(n),

where AS(k, · ) denotes that A has access to the oracle S(k, · ), and Query(AS(k, · ), 1n) denotes the set of the queries on S made by A, which knows n. Clearly we require that any adversary cannot directly query the string x on S, since otherwise she can easily obtain a valid tag.


While MAC functions are similar to cryptographic hash functions, they possess different security requirements. To be considered secure, a MAC function must resist under . This means that even if an attacker has access to an which possesses the secret key and generates MACs for messages of the attacker’s choosing, the attacker cannot guess the MAC for other messages (which were not used to query the oracle) without performing infeasible amounts of computation.

MACs differ from digital signatures as MAC values are both generated and verified using the same secret key. This implies that the sender and receiver of a message must agree on the same key before initiating communications, as is the case with . For the same reason, MACs do not provide the property of offered by signatures specifically in the case of a network-wide shared secret key: any user who can verify a MAC is also capable of generating MACs for other messages. In contrast, a digital signature is generated using the private key of a key pair, which is public-key cryptography. Since this private key is only accessible to its holder, a digital signature proves that a document was signed by none other than that holder. Thus, digital signatures do offer non-repudiation. However, non-repudiation can be provided by systems that securely bind key usage information to the MAC key; the same key is in the possession of two people, but one has a copy of the key that can be used for MAC generation while the other has a copy of the key in a that only permits MAC verification. This is commonly done in the finance industry.

Message integrity codes

The term message integrity code (MIC) is frequently substituted for the term MAC, especially in communications, where the acronym MAC traditionally stands for (media access control address). However, some authors use MIC to refer to a , which is different from a MAC – a message digest does not use secret keys. This lack of security means that any message digest intended for use gauging message integrity should be encrypted or otherwise be protected against tampering. Message digest algorithms are created such that a given message will always produce the same message digest assuming the same algorithm is used to generate both. Conversely, MAC algorithms are designed to produce matching MACs only if the same message, secret key and are input to the same algorithm. Message digests do not use secret keys and, when taken on their own, are therefore a much less reliable gauge of message integrity than MACs. Because MACs use secret keys, they do not necessarily need to be encrypted to provide the same level of assurance.

RFC 4949 recommends avoiding the term “message integrity code” (MIC), and instead using “checksum“, “”, “hash“, “keyed hash”, “message authentication code”, or “protected checksum”.


MAC algorithms can be constructed from other cryptographic primitives, like cryptographic hash functions (as in the case of ) or from algorithms (, and ). However many of the fastest MAC algorithms like and are constructed based on universal hashing.

Additionally, the MAC algorithm can deliberately combine two or more cryptographic primitives, so as to maintain protection even if one of them is later found to be vulnerable. For instance, in (TLS), the input data is split in halves that are each processed with a different hashing primitive (MD5 and SHA-1) then together to output the MAC.


Various standards exist that define MAC algorithms. These include:

  • FIPS PUB 113 Computer Data Authentication, withdrawn in 2002, defines an algorithm based on .
  • FIPS PUB 198-1 The Keyed-Hash Message Authentication Code (HMAC)
  • Mechanisms using a block cipher
  • /IEC 9797-2 Mechanisms using a dedicated hash-function

ISO/IEC 9797-1 and -2 define generic models and algorithms that can be used with any block cipher or hash function, and a variety of different parameters. These models and parameters allow more specific algorithms to be defined by nominating the parameters. For example, the FIPS PUB 113 algorithm is functionally equivalent to ISO/IEC 9797-1 MAC algorithm 1 with padding method 1 and a block cipher algorithm of DES.

==An example of MAC use==Fi

In this example, the sender of a message runs it through a MAC algorithm to produce a MAC data tag. The message and the MAC tag are then sent to the receiver. The receiver in turn runs the message portion of the transmission through the same MAC algorithm using the same key, producing a second MAC data tag. The receiver then compares the first MAC tag received in the transmission to the second generated MAC tag. If they are identical, the receiver can safely assume that the message was not altered or tampered with during transmission ().

However, to allow the receiver to be able to detect , the message itself must contain data that assures that this same message can only be sent once (e.g. time stamp, sequence number or use of a one-time MAC). Otherwise an attacker could – without even understanding its content – record this message and play it back at a later time, producing the same result as the original sender.

One-time MAC

Universal hashing and in particular hash functions provide a secure message authentication code as long as the key is used at most once. This can be seen as of the for authentication.

The simplest such pairwise independent hash function is defined by the random key key = (a,b), and the MAC tag for a message m is computed as tag = (am + b) mod p, where p is prime.

More generally, k-independent hashing functions provide a secure message authentication code as long as the key is used less than k-times for k-wise independent hashing functions.

See Also on BitcoinWiki