Tuesday, February 25, 2014

Connectwise System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

 source: http://ipswitchft.force.com/kb/articles/FAQ/Windows-Platform-FIPS-validated-crypto-message-appears-trying-to-access-Login-aspx-1307565986146

Answer/Solution:
 
Your Windows environment may be configured to use FIPS encryption that is conflicting with WebInspect.
To correct this you will need to disable the "Local Security Setting System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" policy in Windows.
  1. Go to Start > Control Panel > Administrative tools > Local Security Policy. The Group Policy dialog appears. 
  2. Under the "Local Policies" heading, select "Security Options" and look for the entry, "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing." 
  3. If entry this is enabled, disable it.
Also, open the registry editor and browse to the following path.  Make sure this registry subkey is set to 1:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy
ASP.NET 2.0 uses the RijndaelManaged implementation of the AES algorithm when it processes view state data. The ReindaelManaged implementation has not been certified by the National Institute of Standards and Technology (NIST) as compliant with the Federal Information Processing Standard (FIPS). Therefore, the AES algorithm is not part of the Windows Platform FIPS validated cryptographic algorithms.

2 comments:

  1. Thank you so much, I've referred to this document multiple times!!

    ReplyDelete
  2. Thanks, I eventually permanently resolved the issue by re-installing Win 8 on my PC - I am now able to use both Cisco AnyConnect and connectwise with the default settings of FIPS

    ReplyDelete