BS ISO/IEC 29192 โ€” Lightweight Cryptography Series (Information Security Techniques)

Information technology โ€” Security techniques โ€” Lightweight cryptography (ISO/IEC 29192 series)

๐Ÿ” BS ISO/IEC 29192 is the UK implementation, published by the British Standards Institution (BSI), of the ISO/IEC 29192 international series, which specifies Information technology โ€” Security techniques โ€” Lightweight cryptography. Prepared under the responsibility of BSI Technical Committee IST/33 (IT โ€” Security techniques), it defines low-overhead cryptographic algorithms and related requirements for resource-constrained embedded and IoT devices. It is an important standard basis for protecting RFID, sensor nodes, smart meters, and wearable devices.

๐Ÿ’ก IoT and embedded devices often have only a very small chip area, memory, and energy budget, so heavyweight cryptographic algorithms are hard to support. Lightweight cryptography provides acceptable security strength at much lower implementation cost โ€” one of the foundations of “IoT security”.

1. Series Overview and Background ๐Ÿ“Œ

With the proliferation of IoT, RFID, and smart cards, a large number of devices need to protect data security under very low resource conditions. The ISO/IEC 29192 series started publishing in 2012, defining the constraint categories, security requirements, and concrete algorithms of lightweight cryptography. BSI implemented the series as British Standards, forming BS ISO/IEC 29192.

The parts are clearly structured: Part 1 specifies general requirements and constraint classification, Part 2 specifies block ciphers, Part 3 specifies stream ciphers, and Parts 4 and 5 add related algorithms and mechanisms. Together the parts provide a complete, verifiable lightweight cryptography suite for resource-constrained environments.

โš ๏ธ In this batch, BS ISO/IEC 29192-4:2013+A1:2016 and BS ISO/IEC 29192-5:2016 are scanned editions; their content here is summarized from public domain knowledge. Always refer to the official BSI published version for exact clauses.

2. Series Structure and Technical Highlights ๐Ÿ“‹

StandardPart TitleYearKey Technical Content
BS ISO/IEC 29192-1:2012General2012Constraint categories (chip area, energy, code/RAM size, bandwidth, execution time), security and classification requirements
BS ISO/IEC 29192-2:2012Block ciphers201264-bit block cipher PRESENT, 128-bit block cipher CLEFIA, including object identifiers and test vectors
BS ISO/IEC 29192-3:2012Stream ciphers2012General stream-cipher models and keystream generators, Enocoro-128v2 and Enocoro-80
BS ISO/IEC 29192-4:2013+A1:2016Supplementary part (scanned edition)2013/2016Summarized from public domain knowledge; involves related algorithms or authentication mechanisms
BS ISO/IEC 29192-5:2016Supplementary part (scanned edition)2016Summarized from public domain knowledge; involves supplementary lightweight algorithms or applications
๐Ÿ’ก Constraint categories are the “design boundary” of lightweight cryptography: chip area, energy consumption, program/memory size, communication bandwidth, and execution time together define acceptable implementation overhead and are the basis for algorithm selection and security trade-offs.

3. Key Technical Requirements ๐Ÿ”ง

3.1 General Requirements (Part 1)

Part 1 defines the constraint categories of lightweight cryptography (chip area, energy consumption, program code and RAM size, communication bandwidth, execution time) and the security and classification requirements, providing unified criteria for algorithm selection and implementation.

3.2 Block Ciphers (Part 2)

Part 2 specifies the 64-bit block cipher PRESENT and the 128-bit block cipher CLEFIA, giving algorithm structure, key schedule, object identifiers, and test vectors, to balance different levels of security strength against implementation overhead.

3.3 Stream Ciphers (Part 3)

Part 3 specifies the general models of stream ciphers (synchronous keystream generators, output functions) and the Enocoro-128v2 and Enocoro-80 dedicated keystream generators, suitable for high-speed, low-latency data protection in resource-constrained scenarios.

๐Ÿšจ Security essentials: lightweight cryptography trades lower overhead for “sufficient” security strength, not absolute security. Choose algorithms according to the threat model and resource budget, and avoid over-relying on lightweight schemes in sensitive applications.

4. Engineering Practice and Applications ๐Ÿ› ๏ธ

  • ๐Ÿ” RFID and smart cards: implement data encryption and authentication within a very small chip area.
  • ๐Ÿ”ง IoT sensors: protect telemetry data and node communication with low-energy cryptography.
  • ๐Ÿ“Š Smart meters: safeguard the confidentiality and integrity of metering data and key management.
  • ๐Ÿ“‹ Wearable devices: provide privacy protection within limited memory and battery life.
โœ… Lightweight cryptography provides implementable encryption means for resource-constrained devices, supporting IoT data protection and privacy compliance, and is a key building block of smart-hardware security design.

5. Frequently Asked Questions โ“

โ“ Q: Why is “lightweight” cryptography needed?
A: Many embedded and IoT devices have extremely limited resources (chip area, memory, energy), making traditional cryptography hard to support; lightweight cryptography provides acceptable security strength at lower overhead.
โ“ Q: What is the difference between PRESENT and CLEFIA?
A: PRESENT is a 64-bit block cipher with lower implementation cost; CLEFIA is a 128-bit block cipher with higher security strength, suiting scenarios needing stronger protection.
โ“ Q: What scenarios fit stream ciphers?
A: Stream ciphers (such as the Enocoro family) suit scenarios needing high speed, low latency, and constrained resources, e.g., sensor nodes and real-time communication encryption.
๐Ÿ” Q: How should a lightweight cryptographic algorithm be chosen?
A: Weigh threat model, resource budget, and data sensitivity comprehensively; refer to the constraint categories and security requirements specified by the standard, and assess implementation overhead versus algorithm strength as needed.
🔒
ๆญฃๅœจๅŠ ่ฝฝไธ‹่ฝฝๅœฐๅ€๏ผŒ่ฏท็จๅ€™ 10 ็ง’

Leave a Reply

Your email address will not be published. Required fields are marked *