If the module and its algorithm implementations have been tested by an accredited testing lab, this already provides strong guarantees that all algorithms produce the correct results. If, further, the module’s firmware/software integrity has been tested, and all KAT succeed at the module’s first start-up in the same operational environment, then it is all but impossible that a particular algorithm implementation running in the same operational environment has been corrupted. Thus, performing the KATs at each subsequent start-up, at the same time when the module’s integrity test is performed, does not add to the assurance of the module’s ability to correctly perform the cryptographic operations. While the FIPS 140-2 standard does require that all algorithms are tested by a KAT at power-up, it can be argued that this requirement is met by the combination of lab testing, the testing upon the initial installation of the module on the platform of use which includes the power-up integrity test and the full set of KATs, and the software/firmware integrity test at each power-on of the module.