Sharon Keller, Director CAVP, NIST
Steve (?), CAVP, NIST
The CAVP takes over after NIST picks a new algorithm, the CAVP takes over and figures out how to test it. They need to evaluate the algorithm from top to bottom - identify the mathematical formulas, components, etc.
The CAVP develop and implement the algorithm valdiation test suite. Which requirements are addressable at this level? They develop the test metrics for the algorithm and exercise all mathematical elements of the algorithm. If something fails - why? Is there an error in the algorithm, or an intentional failure - or is there an error in the test?
The next stop is to develop user documentaion and guidance, called validation system document (VS), documents test suite and provides instructions o implementing validation tests. There is cross validation, and make sure that both teams come up with the same answers - a good way to check their own work.
The basic tests are Known Answer Tests (KAT) , Multi-block Message Test (MMT), and Monte Carlo Tests. KATs are designed to verify the components to algorithms. MMT will test algorithms where there may be chaining of information from one block to the next and make sure it still works. The Monte Carlo Tests are exhaustive, checking for flaws in the UI or race conditions.
Additionally need to test the boundaries - what happens if you encrypt the empty string? What if we send in negative inputs?
There are many documents for validation testing - one for each algorithm or algorithm mode.
The goals of all these tests? Cover all the nooks and crannies - prevent hackers from taking advantage of poorly written code.
Currently, the CAVP is working on tests for SP 800-56C, SP 800-132 and SP800-56A (Rev2).
In the future, there will be tests for SP 800-56B (rev1), SP 800-106 and SP800-38A. Which ones of these is more important for you to get these tests completed?
Upcoming algorithms that are still in draft, FIPS 202 (Draft) for SHA3, SP800-90A (Rev2) for DRBG, SP800-90B for Entropy Sources and SP 800-90C for construction of RBGS. Ms. Keller has learned the hard way - her team cannot write tests for algorithms until they are a published standard.
No One Will EVER KNOW - To quote absolutely no one, *piping mistakes happen*. A slip of the wrist, a miscommunication, a minor earthquake - for whatever reason, sometimes things...