Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 5 subscribers
  • Views 5834 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Determining FIPS compliance for SafeGuard 6.00.1

BzlBob

Hi,

My organization is using SafeGuard 6.00.1.  Is there a way to determine on my client whether or not the installation is FIPS compliant?

Thanks in advance,

Bob

:45313


This thread was automatically locked due to age.
  • 0

    Hi Bob,

    to achive FIPS 140-2 compliance, you need to install the SafeGuard Enterprise Client with a specific parameter (example: msiexec /i D:\Software\SGNClient.msi FIPS_AES=1). Once the SafeGuard Client was installed and encrypted, you can check the clients registry and confirm the algorithm used to encrypted the volumes using the information below: 

    AES128 (FIPS):            HKLM\Software\Utimaco\CRYPTENG\AES\DllName = CEAESN
    AES256 (FIPS):            HKLM\Software\Utimaco\CRYPTENG\AES256\DllName = CEAES2N


    AES128 (Gladman):    HKLM\Software\Utimaco\CRYPTENG\AES\DllName = CEGAESN
    AES256 (Gladman):    HKLM\Software\Utimaco\CRYPTENG\AES256\DllName = CEGAES2N

    Hope that helps.

    Regards,

    Chris

    :45383
Unfiltered HTML