From 633b31b5d271a9ba5ef700c70a57ec5459a4b96a Mon Sep 17 00:00:00 2001 From: Brian Wood Date: Tue, 21 May 2019 11:17:33 -0400 Subject: [PATCH] FCS_CKM_EXT.5 app note misspelled "is" removed "m" from "mis" --- input/fileencryption.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/input/fileencryption.xml b/input/fileencryption.xml index 13992f9..1f950e4 100644 --- a/input/fileencryption.xml +++ b/input/fileencryption.xml @@ -2214,7 +2214,7 @@ The following sections describe any modifications that the ST author must make t The FAK shall be protected in a manner conformant to FCS_COP_EXT.1(6). The intent of this requirement is to describe the different - methods that a FAK can be created and formed. FCS_CKM_EXT.5.1 details how a FAK mis stored. FCS_CKM_EXT.5.2 requires that each resource to be encrypted + methods that a FAK can be created and formed. FCS_CKM_EXT.5.1 details how a FAK is stored. FCS_CKM_EXT.5.2 requires that each resource to be encrypted has a unique FAK, and that this FAK is generated by the TSF. If the encrypted resource is a set of files encrypted under one FAK, additional requirements on the initialization vectors and cipher modes must be adhered to in Section 4.2.