Skip to content
Secure NFC Hub

Technology / Technical reference

NTAG 424 DNA AES Key Management

Understand NTAG 424 DNA AES-128 key roles, access rights, per-tag diversification, secure personalization and key custody for production issuance.

KEY CUSTODY & PERSONALIZATION

Keep master secrets outside the NFC read path

The illustration describes an example server-managed issuance design, not an automatic feature of the chip.

  1. 01

    Master secret

    Controlled key custody

  2. 02

    Derivation

    Profile / UID inputs

  3. 03

    Tag keys

    Provision AES keys

  4. 04

    Verifier

    Use matching key policy

EXAMPLE · ISSUANCE KEY HIERARCHY

TRUSTED KEY CUSTODY

Master key material

Controlled diversification / derivation

Defined algorithm and tag / batch context

Personalization

Configure tag AES keys and access rights

Verification

Derive or retrieve matching verification material

Illustrative architecture. Diversification is optional and the tag does not automatically derive its own per-UID keys.

AES-128

Tag key algorithm

5 keys

Key numbers 0–4

Per-tag

Optional diversification

Audit

Issuance accountability

Engineering note.Key numbers are not fixed universal roles. Access rights, diversification and key ownership must be defined for each issuing profile.

01 Introduction

The NTAG 424 DNA application exposes multiple AES-128 keys with per-file access conditions. Personalization software — not the end consumer — writes keys and file settings under appropriate authentication.

02 Technical reference

Operational practices

  • Separate master keys from line keys and from verification keys
  • Use diversification so each tag UID maps to distinct key material where required
  • Restrict bench and cloud issuance roles with audit logging
  • Never embed live keys in mobile apps or public NDEF
03 Technical reference

Key custody and diversification

A production design should define who owns master secrets, how issuing profiles select keys, and whether each tag uses shared, batch-specific or diversified keys. Diversification is implemented by the issuing system; it is not automatically performed by the chip.

Server-managed issuance can keep sensitive cryptographic operations within trusted infrastructure when supported by the deployment. A desktop PC/SC reader is then part of the command transport, but this architecture must not be assumed for every workstation or tool.

04 Technical reference

Production controls

  • Separate development, staging and production key material and issuance permissions.
  • Restrict key changes and profile updates to authorized operators with audit records.
  • Define rotation, compromise response, re-issuance and revocation procedures.
  • Validate file permissions, SDM output and backend verification before releasing a batch.
05 Technical reference

APDU command references

Command classes and file operations must follow NXP documentation for your silicon revision. Secure NFC Hub does not publish fabricated command sequences; use official NTAG 424 DNA datasheets and application notes when implementing readers.

  • Confirm file numbers and access conditions in your personalization profile
  • Validate against real tags in a controlled lab before production lots

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