|
906 | 906 | destruction of keys in some configurations or circumstances.</TSS> |
907 | 907 | <Guidance/> |
908 | 908 | <Tests> |
909 | | - The following tests may require the developer to provide access to a test platform that provides the evaluator with tools that are typically not found on factory products. <h:p/> <mark>What if the methods do not fall into any of the below categories?</mark> <h:p/>The evaluator shall perform the following for each of the key destruction methods described in FCS_CKM.6.2: |
| 909 | + The following tests may require the developer to provide access to a test platform that provides the evaluator with tools that are typically not found on factory products. <h:p/> <h:mark>What if the methods do not fall into any of the below categories?</h:mark> <h:p/>The evaluator shall perform the following for each of the key destruction methods described in FCS_CKM.6.2: |
910 | 910 | <testlist> |
911 | | - <test> <mark>If the key destruction method acts upon keys and keying material held in volatile memory |
| 911 | + <test> <h:mark>If the key destruction method acts upon keys and keying material held in volatile memory |
912 | 912 | that is subject to overwrite by the TOE (whether or not the plaintext key is |
913 | | - subsequently encrypted for storage in volatile or non-volatile memory).</mark> <h:p/> The evaluator shall: <h:ol type="1"><h:li>Record the value of the key or keying material.</h:li> <h:li>Cause the TOE to dump the appropriate memory into a binary file.</h:li> <h:li>Search the content of the binary file created in Step #2 to locate all |
| 913 | + subsequently encrypted for storage in volatile or non-volatile memory).</h:mark> <h:p/> The evaluator shall: <h:ol type="1"><h:li>Record the value of the key or keying material.</h:li> <h:li>Cause the TOE to dump the appropriate memory into a binary file.</h:li> <h:li>Search the content of the binary file created in Step #2 to locate all |
914 | 914 | instances of the known key value from Step #1.<h:p/> |
915 | 915 | Note that the primary purpose of Step #3 is to demonstrate that appropriate |
916 | 916 | search commands are being used for Steps #8 and #9.</h:li> <h:li>Cause the TOE to perform normal cryptographic processing with the key |
|
921 | 921 | stored, in order to choose fragment sizes that are the same or smaller than |
922 | 922 | any fragmentation of the data that may be implemented by the TOE. The |
923 | 923 | endianness or byte-order should also be taken into account in the search.)</h:li></h:ol> <h:p/> Steps #1-8 ensure that the complete key does not exist anywhere in volatile memory. If a copy is found, then the test fails. <h:p/> Step #9 ensures that partial key fragments do not remain in memory. If the evaluator finds a 32-or-greater-consecutive-bit fragment, then fail immediately. Otherwise, there is a chance that it is not within the context of a key (e.g., some random bits that happen to match). If this is the case the test should be repeated with a different key in Step #1. If a fragment is also found in this repeated run, then the test fails unless the developer provides a reasonable explanation for the collision, then the evaluator may give a pass on this test. <h:p/> </test> |
924 | | - <test> <mark>If the key destruction method acts upon keys and keying material held in non-volatile |
925 | | - memory that is subject to overwrite or erasure by the TOE.</mark> <h:ol type="1"><h:li>Record the value of the key or keying material.</h:li> <h:li>Cause the TOE to perform normal cryptographic processing with the key |
| 924 | + <test> <h:mark>If the key destruction method acts upon keys and keying material held in non-volatile |
| 925 | + memory that is subject to overwrite or erasure by the TOE.</h:mark> <h:ol type="1"><h:li>Record the value of the key or keying material.</h:li> <h:li>Cause the TOE to perform normal cryptographic processing with the key |
926 | 926 | from Step #1.</h:li> <h:li>Search the non-volatile memory the key was stored in for instances of the |
927 | 927 | known key value from Step #1. <h:p/> |
928 | 928 | Note that the primary purpose of Step #3 is to demonstrate that appropriate |
|
933 | 933 | stored, in order to choose fragment sizes that are the same or smaller than |
934 | 934 | any fragmentation of the data that may be implemented by the TOE. The |
935 | 935 | endianness or byte-order should also be taken into account in the search).</h:li></h:ol> Step #6 ensures that partial key fragments do not remain in non-volatile memory. If the evaluator finds a 32-or-greater-consecutive-bit fragment, then fail immediately. Otherwise, there is a chance that it is not within the context of a key (e.g., some random bits that happen to match). If this is the case the test should be repeated with a different key in Step #1. If a fragment is also found in this repeated run, then the test fails unless the developer provides a reasonable explanation for the collision, then the evaluator may give a pass on this test. <h:p/> </test> |
936 | | - <test> <mark>If the key destruction method acts upon keys and keying material held in non-volatile |
937 | | - memory that is subject to overwrite or erasure by the TOE.</mark> <h:ol type="1"><h:li>Record memory of the key or keying material.</h:li> <h:li>Cause the TOE to perform normal cryptographic processing with the key |
| 936 | + <test> <h:mark>If the key destruction method acts upon keys and keying material held in non-volatile |
| 937 | + memory that is subject to overwrite or erasure by the TOE.</h:mark> <h:ol type="1"><h:li>Record memory of the key or keying material.</h:li> <h:li>Cause the TOE to perform normal cryptographic processing with the key |
938 | 938 | from Step #1.</h:li> <h:li>Cause the TOE to clear the key. Record the value to be used for the |
939 | 939 | overwrite of the key. </h:li> <h:li>Examine the memory from Step #1 to ensure the appropriate pattern |
940 | 940 | (recorded in Step #3) is used. </h:li></h:ol> The test succeeds if correct pattern is found in the memory location. If the pattern is not found, then the test fails.</test> |
|
3852 | 3852 | <selectables linebreak="yes"><selectable id="fpt_rot_ext.2.2_1" >Stop all execution, or</selectable><selectable id="fpt_rot_ext.2.2_2">Notify an <selectables><selectable id="sel-rot2-admin-notify" >Administrator</selectable><selectable id="fpt_rot_ext.2.2_3" >User</selectable></selectables> by <selectables><selectable id="sel-rot2-audit" >generating an audit event</selectable><selectable id="fpt_rot_ext.2.2_5" ><assignable>other notification method(s)</assignable></selectable></selectables>, and <selectables linebreak="yes"><selectable id="fpt_rot_ext.2.2_6" >Stop all execution</selectable><selectable id="fpt_rot_ext.2.2_7" >Shut down, or</selectable><selectable id="sel-rot2-recovery" >Initiate a recovery process as specified in FPT_RVR_EXT.1</selectable></selectables> <selectables linebreak="yes"><selectable id="fpt_rot_ext.2.2_8" >automatically</selectable><selectable id="sel-rot2-admin-config" >in accordance with Administrator-configurable policy</selectable><selectable id="fpt_rot_ext.2.2_9">by express determination of an <selectables><selectable id="sel-rot2-admin-det" >Administrator</selectable><selectable id="sel-rot2-user-det" >User</selectable></selectables> </selectable></selectables> </selectable></selectables>. </title> |
3853 | 3853 | <ext-comp-def-title><title>The TOE shall take the following actions if an integrity check specified in |
3854 | 3854 | FPT_ROT_EXT.2.1 fails: |
3855 | | - <h:ol type="1"><h:li><mark>Halt,</mark></h:li><h:li><mark>Sometimes stop, sometimes notify, sometimes keep going but skip the bad code</mark></h:li><h:li>Notify an |
| 3855 | + <h:ol type="1"><h:li><h:mark>Halt,</h:mark></h:li><h:li><h:mark>Sometimes stop, sometimes notify, sometimes keep going but skip the bad code</h:mark></h:li><h:li>Notify an |
3856 | 3856 | <selectables><selectable>Administrator</selectable><selectable>User</selectable></selectables> by |
3857 | 3857 | <assignable>notification method</assignable>, and</h:li><h:li><selectables linebreak="yes" onlyone="yes"><selectable>Stop all execution and shut down</selectable><selectable>Initiate a recovery process</selectable></selectables><h:br/><selectables linebreak="yes" onlyone="yes"><selectable>automatically</selectable><selectable>in accordance with Administrator-configurable policy</selectable><selectable>by express determination of an |
3858 | 3858 | <selectables><selectable>Administrator</selectable><selectable>User</selectable></selectables></selectable></selectables></h:li></h:ol>. |
|
0 commit comments