In FIPS mode, certain self-tests are performed on start of the client system when the MCCM module is loaded.
If FIPS self-tests fail, the system responds in one of these ways:
If the MCCM FIPS component fails the self-test, the system doesn't activate or enforce policies.
If the Trellix FRP driver fails the self-test, the driver performs a bug-check (crash).
Note
FIPS 140-2 defines minimum requirements for entropy during key generation. This might lead to key generation errors during Removable Media device initialization when using offline access support, CD/DVD/ISO creation, self-extractor creation, user local key creation, and when changing authentication methods for removable media where insufficient entropy (randomness) is available at the point of key generation. To avoid this, connect to a network with sufficient network activity to allow entropy generation.