GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||
GeezerVison is showing csrc.nist.gov — Cryptographic Algorithm Validation Program | CSRC
You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to https://csrc.nist.gov. 
Official websites use .gov 
Secure .gov websites use HTTPS Cryptographic Algorithm Validation Program CAVPProject LinksOverviewThe NIST Cryptographic Algorithm Validation Program (CAVP) provides validation testing of Approved (i.e., FIPS-approved and NIST-recommended) cryptographic algorithms and their individual components. Cryptographic algorithm validation is a prerequisite of cryptographic module validation. The list of FIPS-approved algorithms can be found in SP 800-140C and SP 800-140D. Vendors may use any of the NVLAP-accredited Cryptographic and Security Testing (CST) Laboratories to test algorithm implementations. An algorithm implementation successfully tested by a lab and validated by NIST is added to an appropriate validation list, which identifies the vendor, implementation, operational environment, validation date and algorithm details. Validation Testing Through ACVTS
The CAVP offers two Automated Cryptographic Validation Test Systems (ACVTS) for interested users to test cryptographic algorithm implementations. A Demo ACVTS server is available at no cost to interested parties. See Accessing the ACVTS for details. The Production ACVTS server is only available to NVLAP-accredited testing laboratories, and is the only way to create algorithm validation certificates listed on the Algorithm Validation Page. The CAVP, through ACVTS, will generate test vectors to match the capabilities of a given implementation under test. The CAVP is not responsible for running those test vectors through the implementation.
Test Methods
Through ACVTS, the CAVP can focus on generating interesting test cases to ensure correctness and robustness of cryptographic algorithm implementations. Testing is performed by first providing ACVTS with a set of capabilities for a particular cryptographic algorithm that the implementation supports. For example, the message lengths supported for a hash function. ACVTS will generate test cases that match these capabilities and provide the inputs to the implementation under test. The implementation runs the inputs through the corresponding cryptographic function and provides the outputs back to ACVTS. ACVTS then validates the outputs are correct before returning a verdict. Once this is completed for all algorithms in the test session, the implementation can submit to appear on the Algorithm Validation Page if the testing was performed through a lab on Production ACVTS. Due to this structure, ACVTS testing is entirely black-box. The implementation is never provided to NIST or the CAVP in order to receive a validation certificate. For more information on ACVTS, which algorithms are supported, and how testing is performed, see the Automated Cryptographic Validation Protocol Documentation.
AlgorithmsCurrently, CAVP tests the following cryptographic algorithms*. Follow the links to algorithm specifications, validation testing requirements, validation lists and test vectors.
Other algorithm testing has been retired: DES, MAC, Skipjack (encryption only), and ANSI X9.17,RNG. * Note: this table lists Approved algorithms that have tests available in both CAVS (deprecated by ACVTS) and ACVTS.
Relationship of Algorithm Validation to FIPS 140 Module ValidationA cryptographic module validated to FIPS 140 shall implement at least one Approved security function used in an Approved mode of operation. For an algorithm implementation to be listed on a cryptographic module validation certificate as an Approved security function, the algorithm implementation must meet all the requirements of FIPS 140 and must successfully complete the cryptographic algorithm validation process. However, a product or implementation does not meet the FIPS 140 module validation requirements by simply implementing an Approved security function and acquiring validations for each of the implemented algorithms. For more information, see the Cryptographic Module Validation Program.
Further Information
The CAVP was established in July 1995 by NIST and the Government of Canada's CCCS. NIST Computer Security Division's Security Testing, Validation, and Measurement Group (STVM) manages the validation testing of cryptographic modules and their underlying cryptographic algorithms through the CAVP and CMVP. Project LinksAdditional PagesContacts Chris Celi - Program Manager - NIST GroupCryptographic TechnologyTopicsSecurity and Privacy: assurance, cryptography, testing & validation Additional PagesAccessing the ACVTS Algorithm Prerequisite Testing Validation Search Block Ciphers Block Cipher Modes Digital Signatures Key Derivation Key Management Key Establishment Message Authentication Random Number Generators Secure Hashing Component Testing Retired Testing Contacts
Chris Celi - Program Manager - NIST GroupCryptographic TechnologyTopicsSecurity and Privacy: assurance, cryptography, testing & validation
Created October 05, 2016, Updated September 22, 2026
| ||||||||||||||||||||||||||
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |
