← Back to the chapter · Previous detail
Technical detail · NFC Security and Alternatives
Turn comparison results into tag-release rules
17.21 Folded Security Best-Practice Notes
Use these rules when turning comparison results into a release design:
| Best practice | Reason |
|---|---|
| Treat public tag content as untrusted input. | Static URLs, UIDs, and text records can be copied, replaced, or replayed. |
| Keep secrets and changing state outside NDEF. | The app, secure element, reader, controller, or backend should own authorization and current state. |
| Fail closed on unexpected records. | Unknown hosts, record types, payload lengths, MIME types, or schema versions should not trigger hidden commands. |
| Read back and mount-test final tags. | A tag written correctly on a bench can fail after locking, label overlay, metal mounting, or phone-case changes. |
| Log tap, proof, policy, fallback, and action separately. | Reviewers need to know whether the tap was observed, the payload was accepted, the policy allowed it, and the action ran. |
When stronger proof is required, use a credential or authenticated tag pattern with freshness, revocation, relay handling, and audit. Short NFC range is a useful usability boundary, but it is not a complete security control.