Lock Bits
Special memory bits that control read/write access to specific memory blocks. Once a lock bit is set, the corresponding memory block becomes read-only. Lock bits themselves are typically OTP (irreversible).
Lock Bits
Lock bitsLock bitsControl bits making memory blocks permanently read-onlyView full → are special OTP (one-time programmable) memory bits in NFC tags that control read/write access to specific memory blocks. When a lock bit is set to 1, the corresponding memory block or group of blocks becomes permanently read-only. Because lock bits are OTP, this protection is irreversible — once set, the data in the locked pages cannot be modified by any reader, regardless of authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full →.
Static vs Dynamic Lock Bits
NFC ForumNFC ForumIndustry body developing NFC standards, specifications, and certifications since 2004View full → Type 2 tags (NTAG and MIFARE Ultralight families) implement two layers of lock bits:
Static lock bits (page 2, bytes 2-3 in NTAG 21x): - Control write access to pages 3 through 15 (the first 52 bytes of addressable memory). - Each bit protects a specific page or group of pages. - Bit 0 of byte 2 locks page 3 (capability container). Bits 1-7 and bits 0-7 of byte 3 lock pages 4-15. - Setting the CC lock bit is common practice after writing the final NDEF configuration.
Dynamic lock bits (located after user memory): - Control write access to the remaining user memoryuser memoryTag memory portion available for user data storageView full → pages (page 16 onward). - Each dynamic lock bit typically protects a group of pages (the group size depends on the chip model). - For NTAG 216, the dynamic lock bytes are at pages 226-227, covering pages 16-225.
Lock Bit Behavior
| Action | Result |
|---|---|
| Write lock bit 0 to 1 | Target pages become read-only permanently |
| Write lock bit 1 to 0 | Impossible (OTP behavior) |
| Read locked pages | Always allowed |
| Write to locked pages | Rejected by the chip (NAK response) |
Practical Usage
Lock bits are typically set during the final stage of tag provisioning in manufacturing:
- Write the NDEF message to user memory.
- Configure password protection if applicable.
- Set static lock bits to protect the capability container.
- Set dynamic lock bits to protect the NDEF data area.
After locking, the tag becomes a read-only data carrier. This is standard practice for NFC tags deployed in products, packaging, and signage where the data should never be modified in the field.
Comparison with Password Protection
Lock bits and password protection serve different purposes. Lock bits provide absolute, permanent write protection. Password protectionPassword protection32-bit access control for memory areas (plaintext transmission)View full → provides conditional access control — the data can still be written by a reader that knows the 32-bit password. For maximum security, both mechanisms can be combined: password-protect the tag during provisioning (for potential firmware updates), then set lock bits only when the tag is finalized for deployment.
Related Terms
Related Guides
Preguntas frecuentes
The NFC glossary is a comprehensive reference of technical terms, acronyms, and concepts used in Near Field Communication technology. It is designed for developers, product managers, and engineers who work with NFC and need clear definitions of terms like NDEF, APDU, anti-collision, and ISO 14443.
Each glossary term is cross-referenced with related NFC chips, standards, and other terms. For example, the term 'AES-128' links to chips that support AES encryption (NTAG 424 DNA, DESFire EV2/EV3), and the term 'ISO 14443' links to all chips compliant with that standard.
Yes. NFCFYI provides glossary definitions in 15 languages including English, Korean, Japanese, Chinese, Spanish, Portuguese, Hindi, Arabic, French, Russian, German, Turkish, Vietnamese, Indonesian, and Thai. Use the language selector in the header to switch languages.