Security Requirements for the IT EnvironmentAppendix A Common Criteria Environment: Security Requirements 675FPT_TST_CIMC.3 Software/firmware load testFPT_TST_CIMC.3.1 A cryptographic mechanism using a FIPS-approved orrecommended authentication technique (e.g., an authentication code, keyed hash,or digital signature algorithm) shall be applied to all security-relevant software andfirmware that can be externally loaded into the CIMC.FPT_TST_CIMC.3.2 The IT environment shall verify the authentication code,keyed hash, or digital signature whenever the software or firmware is externallyloaded into the CIMC. If verification fails, the IT environment shall [not enable theTOE].Rationale: This component is necessary to specify a unique requirement forcertificate issuing and management components that is not addressed by the CC. Itsatisfies the security objective O.Integrity protection of user data and software andO.Periodically check integrity.Trusted path/channels (FTP)FTP_TRP.1 Trusted pathFTP_TRP.1.1 The IT environment shall provide a communication path betweenitself and [local] users that is logically distinct from other communication pathsand provides assured identification of its end points and protection of thecommunicated data from modification or disclosure.FTP_TRP.1.2 The IT environment shall permit [local users] to initiatecommunication via the trusted path.FTP_TRP.1.3 The IT environment shall require the use of the trusted path forinitial user authentication, [and no other services].CIMC TOE Access Control PolicyThe TOE shall support the administration and enforcement of a CIMC TOE accesscontrol policy that provides the capabilities described below.Subjects (human users) will be granted access to objects (data/files) based uponthe:1. Identity of the subject requesting access,2. Role (or roles) the subject is authorized to assume,3. Type of access requested,
