Specifications
52
of stored TSF executable code through the use of the TSF-provided cryptographic services.
6.1.39 FPT_TST.1(1) TST Testing (for cryptography)
FPT_TST.1.1(1) The TSF shall run a suite of self tests in accordance with FIPS PUB 140-2 and Appendix C of
the PP during initial start-up (on power on), at the request of the cryptographic administrator
(on demand), under various conditions defined in section 4.9.1 of FIPS 140-2, and
periodically (at least once a day) to demonstrate the correct operation of the following
cryptographic functions:
a) key error detection;
b) cryptographic algorithms;
c) RNG/PRNG
FPT_TST.1.2(1) The TSF shall provide authorized cryptographic administrators with the capability to verify
the integrity of TSF data related to the cryptography by using TSF-provided cryptographic
functions.
FPT_TST.1.3(1) The TSF shall provide authorized cryptographic administrators with the capability to verify
the integrity of stored TSF executable code related to the cryptography by using TSF-
provided cryptographic functions.
6.1.40 FPT_TST.1(2) TSF Testing (for key generation components)
FPT_TST.1.1(2) The TSF shall perform self tests immediately after generation of a key to demonstrate the
correct operation of each key generation component. If any of these tests fails, that generated
key shall not be used, the cryptographic module shall react as required by FIPS PUB 140-2
for failing a self-test, and this event will be audited.
FPT_TST.1.2(2) The TSF shall provide authorized cryptographic administrators with the capability to verify
the integrity of TSF data related to the key generation by using TSF-provided cryptographic
functions.
FPT_TST.1.3(2) The TSF shall provide authorized cryptographic administrators with the capability to verify
the integrity of stored TSF executable code related to the key generation by using TSF-
provided cryptographic functions.
6.1.41 FTA_SSL.3 TSF-Initiated Termination
FTA_SSL.3.1 The TSF shall terminate a local interactive or wireless session after an administrator
configurable time interval of user inactivity.
Application note: For administrative sessions (not wireless sessions), the “local interactive” session is
understood here to mean the ‘interactive’ (CLI or GUI) session that is established with and
maintained ‘locally’ on the controller (via SSH or TLS).
6.1.42 FTA_TAB.1 Default TOE Access Banners
FTA_TAB.1.1 Before establishing a user session, the TSF shall display an advisory warning message
regarding unauthorized use of the TOE.
Application note: This SFR applies only to interactive administrative interfaces (the Controller CLI, and the
Controller GUI), and does not apply to the SNMPv3 interface.