FIPS 140-2 precludes the use of unvalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as providing no protection to the information or data - in effect the data would be considered unprotected plaintext. If the agency specifies that the information or data be cryptographically protected, then FIPS 140-2 is applicable. In essence, if cryptography is required, then it must be validated.
To check which Cryptographic engine you are using with Symantec Endpoint Encryption, right-click the "PGPce.dll" file in the "c:\Program Files\Symantec\Endpoint Encryption Clients\Drive Encryption" folder, and click the "Details" tab to check the "File Version" value. If the value is 4.3 as mentioned above, the client is covered by FIPS validation. The SEE client is always running with the FIPS validated module.
For Symantec Endpoint Encryption 8.2.1 and FIPS validation information, see article HOWTO101701.
For Symantec Encryption Desktop 10.x and Symantec Encryption Management Server 3.x and FIPS validation information, see article TECH164126.
Subscribing will provide email updates when this Article is updated. Login is required.