Family behaviour
The family defines the requirements for the self-testing of the TSF with respect to some expected correct operation. Examples are interfaces to enforcement functions, and sample arithmetical operations on critical parts of the TOE. These tests can be carried out at start-up, periodically, at the request of the authorised user, or when other conditions are met. The actions to be taken by the TOE as the result of self testing are defined in other families.
The requirements of this family are also needed to detect the corruption of TSF executable code (i.e. TSF software) and TSF data by various failures that do not necessarily stop the TOE's operation (which would be handled by other families). These checks must be performed because these failures may not necessarily be prevented. Such failures can occur either because of unforeseen failure modes or associated oversights in the design of hardware, firmware, or software, or because of malicious corruption of the TSF due to inadequate logical and/or physical protection.
Component levelling
FPT_TST.1 TSF testing, provides the ability to test the TSF's correct operation. These tests may be performed at start-up, periodically, at the request of the authorised user, or when other conditions are met. It also provides the ability to verify the integrity of TSF data and executable code.
Management: for FPT_TST.1
The following actions could be considered for the management functions in FMT:
a) management of the conditions under which TSF self testing occurs, such as during initial start-up, regular interval, or under specified conditions;
b) management of the time interval if appropriate.
Audit: for FPT_TST.1
The following actions should be audited if FAU_GEN Security audit data generation is included in the PP/ST:
a) Basic: Execution of the TSF self tests and the results of the tests.