Submission Requirements and Evaluation Criteria for the Lightweight Cryptography Standardization Process

Submission Requirements and Evaluation Criteria for the Lightweight Cryptography Standardization Process

Submission Requirements and Evaluation Criteria for the Lightweight Cryptography Standardization Process Table of contents 1 Introduction ......................................................................................................................... 2 2 Requirements of Submission Packages ................................................................................ 3 2.1 Cover Sheet ............................................................................................................. 3 2.2 Algorithm Specification and Supporting Documentation.......................................... 3 2.3 Source Code and Test Vectors ................................................................................. 4 2.4 Intellectual Property Statements / Agreements / Disclosures .................................... 4 2.4.1 Statement by Each Submitter ................................................................................. 5 2.4.2 Statement by Patent (and Patent Application) Owner(s) ......................................... 6 2.4.3 Statement by Reference/Optimized/Additional Implementations’ Owner(s) ........... 7 3 Minimum Acceptability Requirements ................................................................................ 7 3.1 AEAD Requirements ............................................................................................... 7 3.2 Hash Function Requirements ................................................................................... 8 3.3 Additional Requirements for Submissions with AEAD and Hashing ........................ 9 3.4 Design Requirements ............................................................................................... 9 3.5 Implementation Requirements ............................................................................... 10 3.5.1 AEAD ................................................................................................................. 10 3.5.2 Hash Function ...................................................................................................... 13 4 Evaluation Criteria ............................................................................................................ 14 4.1 Minimum Acceptability of the Submission ............................................................ 14 4.2 Side Channel and Fault Attack Resistance ............................................................. 14 4.3 Cost ....................................................................................................................... 15 4.4 Performance .......................................................................................................... 15 4.5 Third-party Analysis .............................................................................................. 15 4.6 Suitability for Hardware and Software Implementations ........................................ 15 5 Evaluation Process ............................................................................................................ 15 1 1 Introduction The deployment of small computing devices such as RFID tags, industrial controllers, sensor nodes and smart cards is becoming much more common. The shift from desktop computers to small devices brings a wide range of new security and privacy concerns. In many conventional cryptographic standards, the tradeoff between security, performance and resource requirements was optimized for desktop and server environments, and this makes them difficult or impossible to implement in resource-constrained devices. When they can be implemented, their performance may not be acceptable. Lightweight cryptography is a subfield of cryptography that aims to provide solutions tailored for resource-constrained devices. There has been a significant amount of work done by the academic community related to lightweight cryptography; this includes efficient implementations of conventional cryptography standards, and the design and analysis of new lightweight primitives and protocols. In 2013, NIST initiated a lightweight cryptography project to study the performance of the current NIST-approved cryptographic standards on constrained devices and to understand the need for dedicated lightweight cryptography standards, and if the need is identified, to design a transparent process for standardization. In July 2015, NIST held the first Lightweight Cryptography Workshop in Gaithersburg, MD, to get public feedback on the constraints and limitations of the target devices, and requirements and characteristics of real-world applications of lightweight cryptography. A second workshop was held in October 2016. In March 2017, NIST published NISTIR 8114 Report on Lightweight Cryptography and announced that it has decided to create a portfolio of lightweight algorithms through an open process. In April 2017, NIST published the draft whitepaper Profiles for the Lightweight Cryptography Standardization Process to solicit feedback on proposed functionalities for initial inclusion in the portfolio. In this call for submissions document, the submission requirements and evaluation process for the lightweight cryptography standardization process are explained. NIST requires that submission packages must be received by NIST by February 25, 2019 Submission packages that are received by NIST by January 4, 2019 will be reviewed for completeness by NIST; the submitters will be notified of any deficiencies within a month, allowing time for deficient packages to be amended by the submission deadline. After the submission deadline, NIST will publish all first-round submissions received, except that NIST may eliminate submissions that do not meet requirements stated in this call. No changes to packages will be permitted after the submission deadline, except at specified times during the evaluation phase. Due to the specific requirements of the intellectual property statements as specified in Section 2.4, e-mail submissions shall not be accepted for these statements. The statements specified in Section 2.4 must be mailed to Dr. Kerry McKay, Information Technology Laboratory, Attention: Lightweight Cryptographic Algorithm Submissions, 100 Bureau Drive – Stop 8930, National Institute of Standards and Technology, Gaithersburg, MD 20899-8930. The remainder of the submission package can either be mailed with the intellectual property statements, or sent as e- mail to: [email protected]. This submission e-mail shall have subject line precisely 2 “round 1 submission: NAME” where NAME is replaced by the name of the submission. For technical inquiries, send e-mail to [email protected]. To facilitate the electronic distribution of submissions to all interested parties, copies of all written materials must also be submitted in electronic form in the PDF file format. NIST welcomes both domestic and international submissions; however, in order to facilitate analysis and evaluation, it is required that the submission packages be in English. This requirement includes the cover sheet, algorithm specification and supporting documentation, source code comments, and intellectual property information. “Complete and proper” submission packages will be posted at https://csrc.nist.gov/Projects/Lightweight-Cryptography for public review. To be considered as a “complete and proper” submission, packages shall satisfy the requirements specified in Section 2 and Section 3. 2 Requirements of Submission Packages To be considered as a “complete” submission, packages shall contain the following: • Cover sheet • Algorithm specifications and supporting documentation • Source code and test vectors • Intellectual property statements / agreements / disclosures These requirements are detailed below. 2.1 Cover Sheet The cover sheet of a submission package shall contain the following information: • Name of the submission. • Name(s) of the submitter(s). Corresponding submitter’s name, e-mail address, telephone, organization, and postal address. • (optional) Backup point of contact (with telephone, postal address, and e-mail address). 2.2 Algorithm Specification and Supporting Documentation A complete written specification of the algorithms shall be included, consisting of all necessary mathematical operations, equations, tables, and diagrams that are needed to implement the algorithms. The document shall also include a design rationale, and an explanation for all the important design decisions (with respect to targeted constrained devices) that have been made. The submitter shall explain the provenance of any constants or tables used in the algorithm. Each submission package shall describe a single algorithm, or a collection of algorithms, that implements the authenticated encryption with associated data (AEAD) functionality, and optionally also implements the hashing functionality. 3 For algorithms that have tunable parameters, the submission document shall specify concrete values for these parameters. The submission may specify several parameter sets that allow the selection of a range of possible security/performance tradeoffs. The submitter shall provide an analysis of how the security and performance of the algorithms depend on these parameters. The submission package shall include a statement of the expected security strength of each variant of the submission, along with a supporting rationale. The submission package shall include a statement that summarizes the known cryptanalytic attacks on the variants of the submission, and provide estimates of the complexity of these attacks.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    17 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us