Skip to content
Secure NFC Hub

Technology / Technical reference

NTAG 424 DNA SDM & SUN Explained

Learn how NTAG 424 DNA SDM and SUN generate dynamic NDEF URLs, mirror encrypted PICC data, use CMAC verification and support replay checks.

DYNAMIC NDEF DATA FLOW

SDM creates data; the server verifies it

The mirrored fields depend on the configured SDM template and file access settings.

  1. 01

    Read NDEF

    Phone taps the tag

  2. 02

    Dynamic fields

    PICC data / SDM MAC

  3. 03

    Verify CMAC

    Matching backend keys

  4. 04

    Apply policy

    Counter + binding

EXAMPLE · CONFIGURATION-DEPENDENT URL

https://verify.example/t?picc=ENCRYPTED_PICC&cmac=SDM_MAC

Encrypted PICC data

May encode UID and read counter according to SDM settings

SDM MAC

Validated using the configured message input and matching key

Illustrative field names and placeholders only. Actual offsets, encryption options and MAC input are profile-specific.

NDEF

Phone-readable format

SDM

Dynamic mirroring

CMAC

Message verification

Backend

Trust decision

Engineering note.Example URL fields: ?picc=…&cmac=… . A counter may be inside encrypted PICC data; it is not always a separate URL field.

01 Introduction

Secure Dynamic Messaging lets NTAG 424 DNA mirror selected file contents or derived fields into an NDEF URI or text record when the tag is read. The result can change on every tap while the physical label stays the same.

SDM is a chip configuration and personalization feature. Parsing the NDEF string on a phone is straightforward; determining whether the mirrored values are authentic requires keys, algorithms and policy in your verification service.

02 Technical reference

SDM versus SUN

Secure Dynamic Messaging (SDM) is the configured mechanism that mirrors dynamic fields during an NDEF read. Secure Unique NFC (SUN) describes the resulting tap-specific message used by an authentication workflow. Neither term means the phone has validated the cryptography.

Depending on the file configuration, the URL may contain encrypted PICC data, a read counter and an SDM MAC. The verifier must interpret the actual enabled options rather than assume every field is always present.

03 Technical reference

Personalization and URL template

  • Define the NDEF URL template, mirrored-field offsets and expected encoded lengths.
  • Configure file access rights and the SDM keys needed by the chosen message format.
  • Personalize a test tag and compare its read output against the approved template.
  • Verify the message with matching server-side key material before production.
04 Technical reference

What the backend must verify

  • Parse mirrored or encrypted data according to the exact issuing profile.
  • Reconstruct and validate the SDM MAC using the applicable key and protocol.
  • Apply counter, replay and revocation policy after cryptographic validation.
  • Resolve product data only after the chip reference is registered and bound.
05 Technical reference

Common integration failures

Incorrect mirror offsets, URL encoding changes, mismatched keys or a verifier using a different SDM configuration can invalidate an otherwise readable URL. Test against real tags and capture both successful and deliberately modified messages.

A replayed URL may still carry a valid historical MAC. Detecting reuse requires backend state and a documented counter policy; cryptographic verification alone is not replay protection.

Work with NFCTEC

Plan your secure NFC application.

From custom NTAG 424 DNA tags to secure personalization and backend verification. Tell us about your product, packaging, quantity and integration requirements.

Custom hardware Secure issuance Authentication