Skip to content
Secure NFC Hub

Technology / Technical reference

NTAG 424 DNA SUN Authentication & Verification

Secure Unique NFC (SUN) messages from SDM: what changes per tap, what the chip signs or MACs, and verifier responsibilities.

VERIFICATION DECISION FLOW

Cryptographic validity is only the first check

The backend must distinguish a valid new tap from altered, replayed or revoked data.

  1. 01

    Parse payload

    Configured SDM format

  2. 02

    Verify MAC

    Reject modifications

  3. 03

    Check counter

    Replay / concurrency

  4. 04

    Resolve status

    Binding + revocation

SERVER-SIDE VERIFICATION OUTCOMES

Valid new tap

MAC OK · COUNTER NEW

Continue to binding and revocation checks

Modified payload

MAC INVALID

Reject cryptographic verification

Replayed payload

COUNTER REUSED

Apply documented replay policy

MAC

Cryptographic integrity

Counter

Replay policy input

Revocation

Backend status

Result

Application decision

Engineering note.A previously captured URL can retain a valid MAC. Replay handling requires server-side state and a defined counter policy.

01 Introduction

A SUN message is the tap-unique output of an SDM-enabled NDEF payload. Typical mirrored items include the tag UID, a tap counter, cryptographic MAC and optional encrypted PICC data, depending on configuration.

The phone reads NDEF; it does not perform SUN verification. Your backend must parse the URL or discrete fields, retrieve the correct diversified key material and execute the MAC or decryption steps defined for your deployment.

02 Technical reference

What a verification service checks

  • Decode mirrored or encrypted fields according to the configured SDM template
  • Validate the message authentication code using the correct key material
  • Enforce replay, counter, revocation and product-association policy
  • Return a controlled verification outcome without exposing secret keys
03 Technical reference

Replay and counter policy

A captured SUN URL can contain a historically valid MAC. A verifier should track the accepted read-counter state for the relevant tag or chip reference and decide how to handle duplicates, delayed requests and concurrent scans.

Counter validation is a backend policy, not an automatic rejection by the chip. Offline access, multiple verification regions and recovery from missed taps require an explicit consistency model.

04 Technical reference

Test cases for integration

  • Verify a valid tap using the issuing profile and its matching keys.
  • Modify the MAC or encrypted PICC field and confirm rejection.
  • Submit a previously accepted URL and confirm the configured replay outcome.
  • Check revoked and unrecognized tag references without disclosing key material.
05 Technical reference

What a valid SUN result does not prove

A verified SUN message authenticates configured chip data. It does not independently prove product contents, ownership, packaging integrity or that the tag remains attached to the intended item.

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