← Back to the chapter · Next detail →

Technical detail · NFC Real-World Applications

Access-control evidence

19.6 Folded Access-Control Review Notes

For access systems, a successful NFC observation should move into a verifier and policy path:

StepReview evidence
ObserveReader reports a credential presentation or tag input without assuming access should be granted.
VerifyCopied static values, malformed input, revoked credentials, and wrong-reader cases are rejected.
AuthorizeDoor, role, time window, workflow state, offline rule, and denial handling are checked by policy.
ActThe controller gives constrained feedback and handles duplicate taps without repeated unlocks.
RecordAllow/deny result, reason, reader, credential reference, fallback, and retest trigger are logged.

Keep tag data and credential proof separate. A service label may hold a door reference or support lookup code, but it should not contain an unlock command, role, long-lived secret, or private personal data.

← Back to the chapter · Next detail →