The credential security challenge

Static badge identifiers and copied NDEF URLs can be reused without proving that the expected chip was scanned. Credential programs need controlled issuance, reliable verification and clear lifecycle rules.

Recommended secure NFC approach

  • NTAG 424 DNA with AES-128 authentication and optional SDM/SUN for phone-readable credentials
  • Issuance profiles that control keys, access rights and NDEF configuration
  • Backend association with credential owner, entitlement and status
  • Verification and revocation APIs for the application or reader system

From credential issuance to access decision

  1. Define the credential type, reader capabilities and security policy.
  2. Personalize tags with approved keys and a controlled issuance profile.
  3. Register the issued chip reference against the credential record.
  4. Authenticate the tag or verify its dynamic SDM message using the appropriate reader workflow.
  5. Apply access rights, revocation and audit policy before granting service.

Reader compatibility and scope

A phone-readable NDEF/SUN workflow differs from a dedicated reader performing mutual AES authentication. Choose the method that matches your hardware and threat model; test real readers and credential form factors.

NTAG 424 DNA is not an EMV payment application. It does not replace payment-scheme card issuance, contactless payment kernels, PIN handling or scheme certification.

Pilot requirements

  • Credential form factor and reader or phone models
  • Online/offline verification and revocation policy
  • Expected quantity, key ownership and issuance workflow

Related