When installing and configuring TIBCO Statistica on a secure Windows environment that runs a Security Technical Implementation Guides (STIG - software checks and modifications to ensure the system meets security requirements), running a Python and/or R node will prompt us a message: "This implementation is not part of the Windows Platform Federal Information Processing Standard (FIPS) validated cryptographic algorithms."




Below are the steps to know if the FIPS algorithm is enabled or disabled on the Windows machine where the issue occurs:

• Open Local Security Policy editor (search for it in start menu)
• Select *Local Policies\Security Options to the left
• See Security setting for policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” is set to "Enabled"

TIBCO Statistica is not FIPS compliant for versions 13.6 and lower.

NOTE: Microsoft .NET Framework 4.8 introduced automatic redirect from managed to 'native' FIPS-compliant methods for some APIs. With this change, managed cryptography classes will not throw a Cryptography  Exception error in FIPS mode.

A potential workaround would be to install .NET 4.8 (before or after TIBCO Statistica is installed) and use the switch in the application configuration file as documented on official Microsoft website:
https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/retargeting/4.7.2-4.8#managed-cryptography-classes-do-not-throw-a-cryptographyexception-in-fips-mode