First Advanced Encryption Standard (AES) DES

First Advanced Encryption Standard (AES) DES

Volume 104, Number 1, January–February 1999 Journal of Research of the National Institute of Standards and Technology [J. Res. Natl. Inst. Stand. Technol. 104, 97 (1999)] Conference Report algorithms. This conference served as the formal kick-off of the first AES public evaluation and analysis FIRST ADVANCED period (“Round 1”), which runs through April 15, 1999. ENCRYPTION STANDARD (AES) CANDIDATE 2. Background and Context: the Advanced Encryption Standard CONFERENCE Development Process Ventura, CA Since 1977, NIST’s Data Encryption Standard (DES) August 20-22, 1998 [1] has been the Federal Government’s standard method for encrypting sensitive information. In addi- Report prepared by tion, it has gained wide acceptance in the private sector and has been implemented in a wide variety of banking Edward Roback and applications. The algorithm specified in this standard Morris Dworkin has evolved from solely a U.S. Government algorithm into one that is used globally. However, with recent Information Technology Laboratory, successful key exhaustive attacks, the useful lifetime of National Institute of Standards and Technology, DES is now drawing to a close. Anticipating this even- Gaithersburg, MD 20899-0001 tuality, in 1996 NIST officials began preparing for development of a successor standard. In outlining these Available online: http://www.nist.gov/jres plans, NIST sought to construct an open process to engage the cryptographic research community and build confidence in the successor algorithm. 1. Introduction On January 2, 1997, NIST announced the initiation of a process to develop the AES [2], which would On August 20-22, 1998, 200 members of the global specify the Advanced Encryption Algorithm (AEA) cryptographic research community gathered in Ventura, and serve as an eventual successor to the venerable CA for the First Advanced Encryption Standard (AES) DES. Basic criteria that candidate algorithms would Candidate Conference (AES1). The conference focused have to meet were proposed, in addition to required on 15 cryptographic algorithms being considered elements in the nomination packages to be submitted to for the Federal Government’s Advanced Encryption NIST. Over thirty sets of comments were received from Standard. Sponsored by the National Institute of U.S. Government agencies, vendors, academia, and Standards and Technology’s (NIST) Information individuals. Additionally, NIST sponsored an AES Technology Laboratory, AES1 provided an opportunity workshop on April 15, 1997 to discuss the comments for the submitters of candidate algorithms to brief their received and obtain additional feedback to better define proposals and answer initial questions. The purpose the request for candidate algorithms. This input was of of the conference was to introduce participants in the great assistance to NIST in preparing its formal call for analysis and evaluation process to the various candidate algorithms and evaluation criteria. 97 Volume 104, Number 1, January–February 1999 Journal of Research of the National Institute of Standards and Technology On September 12, 1997, NIST published its formal Twenty-one algorithms were submitted to NIST by call for algorithms. [3] Candidate algorithms had to the June 15, 1998 deadline. After review, NIST deter- meet three basic requirements: 1) implement symmetric mined that 15 of these met the minimum acceptability (secret) key cryptography, 2) be a block cipher, and 3) requirements and were accompanied by a complete support cryptovariable key sizes of 128 bits, 192 bits, submission package. These algorithms were made and 256 bits with a block size of 128 bits. The algorithm public by NIST on August 20, 1998 at AES1 for the first could also support additional key and block sizes. In evaluation period. At the conference, submitters of the addition to the above requirements, submitters had to 15 candidate algorithms were invited to provide brief- provide the following: ings on the candidates and answer any initial questions. NIST also announced its request for comments on the 1. Complete written specifications of the algorithm, candidates, due April 15, 1999. These comments will help NIST narrow the field of candidates to approxi- 2. Statements of the algorithm’s estimated computa- mately five or fewer for the second round of public tional efficiency, evaluation. The public analysis of the candidates will be the subject of the Second AES Candidate Conference 3. Known answer test values for the algorithm, and (AES2), scheduled for March 22-23, 1999. Following code to generate those values, its study of the second round analysis, NIST intends to select one algorithm (or possibly more than one, if 4. Statement of the algorithm’s expected crypto- warranted) to be proposed for inclusion in the AES. graphic strength, 5. Analysis of the algorithm with respect to known 3. Conference Purpose, AES Development attacks, Overview, Announcement of Candidates and Review of Evaluation 6. Statement of advantages and limitations of the Criteria algorithm, 7. Reference implementation of the algorithm, Mr. Miles E. Smid, Manager of the Security specified in ANSI C, Technology Group of the Computer Security Division in NIST’s Information Technology Laboratory, welcomed 8. Optimized implementations specified in Java and the AES1 participants and noted that the primary ANSI C, and purpose of the conference was to provide an opportu- nity for each of the submitters to formally present their 9. Signed statements that a) identified any pertinent candidate algorithms and design philosophy. After patents and patent applications and b) provided for sketching the history of the AES development process, the royalty-free use of that intellectual property he noted that NIST received and reviewed 21 packages. should the candidate selected be selected for In each case, NIST checked whether: 1) the legal inclusion in the AES. documents were completed; 2) the submissions were responsive to all requirements; and 3) the given code, In its call for candidates, NIST made clear that security when run, passed the Known Answer Test.” Six of the would be the most important criterion by which packages were incomplete; thus, 15 candidates were algorithms are evaluated, followed by efficiency and formally accepted into the AES development process. other characteristics. In the spirit of DES’ success, Mr. Smid noted NIST did not perform any cryptanalysis NIST’s goal in the AES development effort is to specify and, therefore, acceptance by NIST of an algorithm into an algorithm that will have a lifetime of at least thirty the process did not signify anything regarding the years, that will be used extensively throughout the U.S. strength of a candidate. A list of the six incomplete Government, and that will be also be available in the submissions was read to the audience and posted to private sector, on a royalty-free basis worldwide. NIST’s AES website. 98 Volume 104, Number 1, January–February 1999 Journal of Research of the National Institute of Standards and Technology Mr. Smid then formally unveiled the accepted Security is, of course, the paramount consideration in candidates, as follows: the AES selection process and encompasses such issues as the relative security of one candidate as compared to Country Algorithm Submitter(s) the others, and the extent to which the algorithm output of Origin is indistinguishable from a random permutation on the Australia LOKI97 Lawrie Brown, Josef Pieprzyk, input block. Each submitter had to provide NIST with an Jennifer Seberry estimate of the strength of their candidate. Therefore, Belgium RIJNDAEL Joan Daemen, Vincent Rijmen any attacks demonstrating that the actual security of an algorithm is less than the claimed strength will factor Canada CAST-256 Entrust Technologies, Inc. into NIST’s AES decision. DEAL Richard Outerbridge, Lars Cost includes licensing requirements, computational Knudsen efficiency, memory requirements and flexibility. Each Costa Rica FROG TecApro Internacional S.A. candidate submitter had to sign license agreements provided by NIST identifying any known intellectual France DFC Centre National pour la Recherche Scientifique (CNRS) property (i.e., patents or patent applications) that may be infringed by the practice of the particular candidate. Germany MAGENTA Deutsche Telekom AG If such property was identified, the owner of the intel- Japan E2 Nippon Telegraph and Telephone lectual property had to agree in writing to allow for Corporation (NTT) its worldwide royalty-free use, should the candidate be Korea CRYPTON Future Systems, Inc. included in the AES. (Use of the algorithms for the purposes of AES evaluation also had to be granted.) USA HPC Rich Schroeppel NIST hopes to address any other intellectual property MARS IBM issues that may arise during the public comment process RC6 RSA Laboratories before selecting the AES algorithm. SAFER+ Cylink Corporation Computational efficiency (i.e., speed) is also a cost TWOFISH Bruce Schneier, John Kelsey, consideration. NIST tests the candidate algorithms on a Doug Whiting, David Wagner, common platform to compare performance characteris- Chris Hall, Niels Ferguson tics. In the first AES evaluation round, this will focus UK, Israel, SERPENT Ross Anderson, Eli Biham, primarily upon the 128 bit key size, while in the second Norway Lars Knudsen round (with about five candidates), this will be expanded to include the 192 bit and 256 bit key sizes and hard- Mr. Smid then briefly reviewed the principal goals ware performance estimates. Memory

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    9 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