Skip to content
Secure NFC Hub

Technology / Technical reference

NTAG 424 DNA Security Architecture

Design NTAG 424 DNA security architecture across tag issuance, AES key custody, SDM/SUN verification, replay handling and product binding.

END-TO-END TRUST BOUNDARIES

Separate issuing, reading and verification

Each stage has distinct credentials, authorization rules and operational risks.

  1. 01

    Issuance

    Keys + configuration

  2. 02

    NFC tag

    Chip-generated data

  3. 03

    Verification

    MAC + counter checks

  4. 04

    Business API

    Binding + entitlement

SYSTEM TRUST BOUNDARIES

CONTROLLED ISSUANCE

Key custody + encoder

Protected keys, issuance profiles and audit

PUBLIC NFC READ

Tag + consumer phone

Untrusted transport of dynamic NDEF data

TRUSTED BACKEND

Verifier + product API

MAC, counter, revocation and product binding

Trust boundaries are conceptual. Actual services, key storage and authorization depend on the deployment.

Issuance

Controlled provisioning

SDM / SUN

Tap data

Server

Cryptographic verifier

Policy

Product-level decision

Engineering note.A verified chip message does not independently establish physical product authenticity, custody or legal ownership.

01 Introduction

A credible NTAG 424 DNA deployment spans tag construction, secure issuance, product binding, consumer read and server verification. Each layer has distinct threats and controls.

02 Technical reference

Layer responsibilities

  • Silicon: AES auth, file access, SDM mirroring, optional tamper status
  • Personalization: keys, NDEF templates, serialization, audit
  • Verification: MAC/SUN checks, counter/revocation policy, logging
  • Experience: content shown after a positive verification outcome
03 Technical reference

Trust boundaries and threat model

A successful MAC check supports confidence in the configured chip-generated message, but does not establish the contents of a package or legal ownership of an item. Tag transfer, compromised issuing keys and incorrect product binding require separate controls.

The public NFC landing page should not contain verification secrets. Protected services need authentication, transport security, logging and appropriate rate limits; counter handling and offline behavior must be explicitly designed.

04 Technical reference

Production verification checklist

  • Test genuine, modified and replayed SDM URLs against the backend verifier.
  • Confirm that unissued, revoked and unbound tags follow defined response rules.
  • Audit who can change keys, issue batches and alter product bindings.
  • Validate the physical tag and tamper construction on the finished product.
05 Technical reference

What the chip does not do

It does not execute anti-counterfeiting business rules, ERP integration, cloud analytics or automatic law-enforcement reporting. Plan those in issuing and verification systems operated under your security model.

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