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