Skip to content
Secure NFC Hub

Technology / Technical reference

NTAG 424 DNA: Features, SDM & Security

Understand NTAG 424 DNA security: AES-128, NFC Type 4, NDEF, Secure Dynamic Messaging, SUN authentication, personalization and backend verification.

CHIP & VERIFICATION ARCHITECTURE

From NFC read to a verified product record

A standard NDEF read can carry dynamic SDM data. A trusted verifier makes the cryptographic decision.

  1. 01

    NTAG 424 DNA

    Configured NDEF + SDM

  2. 02

    NFC phone

    Reads a dynamic URL

  3. 03

    Verifier

    Checks MAC + policy

  4. 04

    Application

    Resolves product record

NFC TYPE 4 · CONCEPTUAL FILE VIEW

Capability Container

NFC Type 4 discovery and access metadata

NDEF File

URI template with optional SDM-mirrored fields

Secure Configuration

AES keys, file access and SDM settings

Logical overview, not a byte-addressed memory map. File IDs and permissions must be checked against the relevant NXP documentation.

13.56 MHz

RF frequency

Type 4

NFC Forum tag

AES-128

Cryptography

416 bytes

User memory

Engineering note.NTAG 424 DNA chip specifications refer to the standard IC; a complete label has additional antenna and environmental constraints.

01 Technical reference

What the chip provides

NTAG 424 DNA is an NFC Forum Type 4 tag IC with AES-128 capabilities, configurable file access rights and optional Secure Dynamic Messaging (SDM). A phone or reader performs a standard NDEF read; cryptographic features are available to personalization equipment and to applications that implement the correct protocol steps.

The tag does not run cloud services, store product master data or decide whether a unit is genuine in a business sense. Those outcomes require personalization, key management and a trusted verification service.

02 Technical reference

NFC Type 4, NDEF and secure files

NTAG 424 DNA supports NFC Forum Type 4 operation. Its NDEF content can be read by compatible NFC phones, while access rights and cryptographic commands are managed separately during issuance. A readable URL is a user experience, not an authentication result.

Secure Dynamic Messaging can insert dynamic fields into an NDEF URL. The verifier must know the exact SDM configuration, key derivation and message format used by the issuing profile.

03 Technical reference

Typical use cases

Brand protection on packaged goods, tamper-indicating labels, serialized product identity and tap-unique SUN payloads that a backend can verify.

  • Packaging with an embedded or applied NFC inlay
  • Consumer tap opening a URL that includes dynamic SDM fields
  • Issuer-controlled keys written during personalization
  • Server-side MAC or encryption verification with matched keys
04 Technical reference

From factory personalization to consumer verification

  1. 01Select the physical tag or label and validate its antenna performance on the actual product.
  2. 02Configure AES keys, file permissions, NDEF data and SDM parameters in a controlled issuance environment.
  3. 03Register the issued tag reference against a product, serial or batch record.
  4. 04On tap, verify the dynamic message and apply counter, revocation and product policy server-side.
05 Technical reference

Common mistakes

Treating a static NDEF URL as proof of authenticity without SDM verification. Assuming reader authentication alone proves supply-chain integrity. Storing long-lived secrets in NDEF. Confusing NTAG 424 DNA with NTAG 424 DNA TagTamper — tamper status is product-specific hardware.

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