Hi Tape Folks,<br><br>It looks like NIST recently changed their FIPS 140-2 Implementation Guidance last January to require &#39;AES Key Wrap&#39; as the only approved symmetric encryption algorithm for key establishment or entry.&nbsp; Previously, we believed that using ESP was adequate for encrypting keys for entry into a tape drive device.<br>
<br>To see NIST&#39;s latest guidance, look at &lt;<a href="http://csrc.nist.gov/groups/STM/cmvp/documents/fips140-2/FIPS1402IG.pdf">http://csrc.nist.gov/groups/STM/cmvp/documents/fips140-2/FIPS1402IG.pdf</a>&gt;<br>Also, see FIPS 140-2 Annex D &quot;Key Establishment Techniques&quot;: &lt;<a href="http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexd.pdf">http://csrc.nist.gov/publications/fips/fips140-2/fips1402annexd.pdf</a>&gt;.<br>
<br>Essentially, NIST is no longer allowing differentiating between the requirements for &#39;Key Entry&#39; vs. &#39;Key Establishment&#39;.&nbsp; It was previously possible to argue with FIPS certification labs that this process was covered under &#39;Key Entry&#39;, and the encryption of the key could use any Approved Mode of Operation (like as used in ESP-SCSI).&nbsp; For &#39;Key Establishment&#39; AES Key Wrap (not CBC, CCM, or GCM) is the only approved symmetric wrapping algorithm.<br>
<br>This has an impact on SSC-3 (or SSC-4 if deferred), and will likely affect existing tape drive products that were expecting to get FIPS 140-2 approval by supporting IKEv2-SCSI with ESP for establishing encryption keys.&nbsp; Double-check with your validation lab (your mileage may vary).<br>
<br>There are several ways to approach this problem.&nbsp; One method will be described in T10/08-155r0.&nbsp; Another approach is to lobby NIST to change their guidance so that existing symmetric encryption modes are sufficient for key transport.&nbsp; Yet another approach is to use the existing RSA and ECC encryption algorithms for Key Entry, if you want to pay for an expense asymmetric key operation each time you enter a key.<br>
<br>If you have received different guidance from your FIPS lab, I would be interested in hearing different angles...<br><br>-- <br>Thanks!<br>Matt Ball, IEEE P1619.x SISWG Chair<br>M.V. Ball Technical Consulting, Inc.<br>
Phone: 303-469-2469, Cell: 303-717-2717<br><a href="http://www.mvballtech.com">http://www.mvballtech.com</a><br><a href="http://www.linkedin.com/in/matthewvball">http://www.linkedin.com/in/matthewvball</a><br><br>