- CAVS would become unresponsive if Modify New Submission was selected several times. This has been corrected.
- On the Modify New Submission screen, some words were not displayed fully. This has been corrected.
- The algorithm validation numbers are now checked to assure they are numeric. If they are not, an error message is displayed.
- When preparing change request, if any information was updated EXCEPT the implementation type information, the implementation type information was cleared. This has been corrected.
- Added this instruction to the Submission Guidance Jan 2017 for New Cryptographic Algorithm Implementation, Submission Guidance Jan 2017 for Cryptographic Algorithm Implementation Change Request, and Submission Guidance Jan 2017 for Cryptographic Algorithm Implementation Update Request: The email must be in plaintext format.
Â
The transition period ends April 30, 2017. This means CAVS21.0 can be used up until April 30, 2017. After that, CAVS21.2 must be used.
As has been the policy in the past:
- EFFECTIVE IMMEDIATELY on any new validation requests for implementations of TDES, AES, SHA, HMAC, CCM, CMAC, DRBG 800-90A, Key Agreement Scheme (KAS) FFC, KAS ECC, GCM 800-38D (including GMAC and XPN), FIPS186-4 DSA, FIPS186-4 ECDSA, FIPS186-4 RSA, XTS, the ECC DLC Primitive Component, SP800-108 KDF, the KDFs in SP800-135, RSA Signature Generation Component testing for PKCS1.5 and/or PKCS PSS, the ECDSA2 Signature Generation Component, the RSADP component, the SP 800-38F Key Wrapping and/or SHA-3 or SHAKE, the CST lab must use the CAVS21.1 to validate the IUT.
- For any algorithm validation request where a lab has used a version of CAVS prior to CAVS 21.2 to create files and has already sent the sample and request files to the vendor, CAVS 21.2 shall be used to validate the response files. The files generated with CAVS 21.1 are compatible with CAVS 21.2. NIST will accept files generated with CAVS 21.1 up through April 30, 2017. They should all be validated with CAVS 21.2.
- For any algorithm validation request where a lab has used a version of CAVS prior to CAVS 21.2 to create files and has already sent the sample and request files to the vendor, CAVS 21.2 shall be used to validate the response files. The files generated with CAVS 21.1 are compatible with CAVS 21.2. NIST will accept files generated with CAVS 21.1 up through April 30, 2017. They should all be validated with CAVS 21.2
- Effective immediately, CAVS 21.2 shall be used to submit change and update requests UNLESS the lab making the change/updated does not have the original submission files.
The CAVP will also review special conditions on a case-by-case basis.