Mutual Authentication

What Is Mutual Authentication?

authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full →/" class="text-cyan-600 dark:text-cyan-400 underline decoration-dotted decoration-cyan-300 dark:decoration-cyan-700 underline-offset-2 hover:decoration-solid transition-colors">Mutual authenticationMutual authenticationTwo-way identity verification between reader and tagView full → is a cryptographic protocol in which both the NFC readerNFC readerActive device generating RF field to initiate communication with tagsView full → and the tag independently verify each other's identity before any sensitive data is exchanged. Unlike one-way authentication where only the tag proves itself to the reader, mutual authentication ensures that the tag also confirms it is communicating with an authorized reader. This two-directional trust model prevents both tag cloning and rogue reader attacks.

Why Mutual Authentication Matters

In a one-way scheme, a legitimate tag can be tricked into revealing its data to a malicious reader because the tag has no mechanism to verify the reader's credentials. Mutual authentication closes this gap. This is critical for contactless payments (EMV specifications require it), corporate access control (rogue readers cannot harvest badge credentials), and brand protection (NTAG 424 DNA tags authenticate the backend server).

How It Works

The process typically follows a three-pass challenge-response protocol:

1. Reader challenge: The reader sends a random nonce to the tag.
2. Tag response + tag challenge: The tag encrypts the reader's nonce with the shared secret key, appends its own random nonce, and returns both.
3. Reader response: The reader decrypts and verifies the tag's response, then encrypts the tag's nonce and sends it back. The tag verifies this final response.

If any step fails, the session terminates without data exchange. Modern implementations use AES-128, providing 128-bit security strength. Older systems used DES/3DES or the now-broken Crypto-1.

Chips Supporting Mutual Authentication

Session Keys and Secure Messaging

After successful mutual authentication, both parties derive a session key from the exchanged nonces and the shared master key. All subsequent communication is encrypted and integrity-protected. The session key is unique per transaction, preventing replay attacks even if the entire RF exchange is captured.

For the highest assurance, combine mutual authentication with originality signatures and SUN messages for layered defense.