FPT_FLS.1 Failure with preservation of secure state
User application notes
The term "secure state" refers to a state in which the TSF data are consistent and the TSF continues correct enforcement of the TSP. The "secure state" is defined in the TSP model. If the developer provided a clear definition of the secure state and the reason why it should be considered secure, the dependency from FPT_FLS.1 to ADV_SPM.1 can be argued away.
Although it is desirable to audit situations in which failure with preservation of secure state occurs, it is not possible in all situations. The PP/ST author should specify those situations in which audit is desired and feasible.
Failures in the TSF may include "hard" failures, which indicate an equipment malfunction and which may require maintenance, service or repair of the TSF. Failures in the TSF may also include recoverable "soft" failures, which may only require initialisation or resetting of the TSF.
Operations
Assignment:
For FPT_FLS.1.1, the PP/ST author should list the types of failures in the TSF for which the TSF should "fail secure," that is, should preserve a secure state and continue to correctly enforce the TSP.