The Assurance Activity for FCS_COP.1 (1) is being revised for clarity due to confusing wording in the current AA. 

1. Change the TSS Assurance Activity for FCS_COP.1(1) to read:

Requirement met by the platform

The evaluator examines the TSS to determine that it lists the APIs used by the TOE to invoke the required functionality on the platform.

Requirement met by the TOE

If multiple modes are supported, the evaluator examines the TSS to determine how a specific mode/key-size is chosen by the end user.

2. Change the Guidance Assurance Activity for FCS_COP.1(1) to read:

Requirement met by the TOE

If multiple modes are supported, the evaluator examines the Operational Guidance to determine how a specific mode/key-size is chosen by the end user.

3. Change “These tests are only for data encryption provided by the application:” in the Test TSS activity to “Requirement met by the TOE”.

4. Add the following to the TSS Assurance Activity:

Requirement met by the platform

The evaluator examines the ST of all platforms claimed in the TOE ST to determine that the specific modes and key-sizes are supported by the underlying platform, and that the APIs listed in the TSS section are those that were exercised on each underlying platform.

The current version of FCS_COP.1(1) is unclear with respect to the specification and testing the encryption/decryption functionality for both the TOE and the TOE platform, so the Assurance Activity is revised to provide clarification.