TD0349: Update to FPT_MCD_EXT.1.2
FPT_MCD_EXT.1.2 does not allow for the option of automatically blocking unsigned, untrusted, or unverified Mobile Code without giving the user the option to keep it.
The Application Software EP for Web Browsers v2.0 is modified as follows:
FPT_MCD_EXT.1.2 is modified as follows:
The browser shall [selection: automatically discard, provide the user with the option to discard] unsigned, untrusted or unverified [selection:
[assignment: other mobile code types supported by the browser]
] mobile code without executing it.
The Guidance for FPT_MCD_EXT.1.2's Assurance Activity is modified as follows:
If "provide the user with the option to discard" is selected, the evaluator shall examine the operational guidance to verify it provides configuration instructions for each of the supported mobile code types. The operational guidance shall also describes the alert that the browser displays to the user when unsigned, untrusted, or unverified mobile code is encountered and the actions the user can take.
The Test for FPT_MCD_EXT.1.2's Assurance Activity is modified as follows:
Test 1: The evaluator shall construct a web page containing correctly signed mobile code and show that it is accepted and executes. The evaluator shall then construct three web pages containing unacceptable mobile code: the first web page contains mobile code that is unsigned; the second web page contains mobile code that is untrusted; the third web page contains mobile code that is unverified. The evaluator shall then attempt to load the mobile code from each of the three web pages, and observe that either 1) the code is rejected, or 2) the user is prompted to accept or reject the code; when the user rejects the code, the code is not executed.
See issue description.