Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-P1619] XTS-AES (as defined by IEEE Std 1619-2007 and SP 800-38E) added to FIPS 140-2 Annex A and IG



Correction, I believe. Are you sure the labs can test it as of now? I don't think so.
 
Larry H


From: Matt Ball [mailto:matt.ball@xxxxxxxxxxxx]
Sent: Wednesday, February 03, 2010 11:58 AM
To: STDS-P1619@xxxxxxxxxxxxxxxxx
Subject: [STDS-P1619] XTS-AES (as defined by IEEE Std 1619-2007 and SP 800-38E) added to FIPS 140-2 Annex A and IG

Hi Everyone,

Good news!  As of last week, NIST has added XTS-AES as an Approved Security Function under FIPS 140-2!  FIPS 140-2 Annex A now references SP 800-38E (also, just recently published), which in turn references IEEE Std 1619-2007 for a description of XTS-AES.  It is now possible to get algorithm certificates for XTS-AES, for cryptographic modules currently under test.

See:
Note that the FIPS 140-2IG has a new section (A.7) that describes the requirements for a vendor to assert that the XTS-AES implementation is compliant both to SP 800-38E and IEEE Std 1619-2007.  An interesting part of this is that the following requirement is not testable by the CAVP:

"Provide assurance that the XTS-AES key shall not be associated with more than one key scope."

We had discussed this type of requirement to some length, both in P1619 and P1619.2.  As a rule, we should strive to make 'shall' requirements only for things that you can test, and use statements such as 'should' for recommendations that cannot easily be verified.

Congratulations to everyone who worked in IEEE P1619 to make this possible!

--
Thanks!

Matt Ball, Chair, IEEE P1619 Security in Storage Working Group
Staff Engineer, Sun Microsystems, Inc.
500 Eldorado Blvd, Bldg #5 BRM05-212, Broomfield, CO 80021
Work: 303-272-7580, Cell: 303-717-2717