On this page
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.
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
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.
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.
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