VeriStand software validates hardware and performs embedded software test for hardware-in-the-loop applications.
VeriStand is used by engineers to reduce test time and costs by connecting models to physical systems. This hardware-in-the-loop (HIL) approach reduces the need for in-field physical testing.
NI has released the following statement on FIPS compliance in VeriStand:
Microsoft Windows has a setting that enables FIPS compliance checking. When enabled, Windows will check that any encryption being used is FIPS-140 approved. This is intended to prevent systems from using encryption that less than secure. Windows detects an encryption algorithm in VeriStand that does not meet FIPS-140 requirements and blocks VeriStand from running. VeriStand uses MD5 which is does not comply with FIPS 140. However, VeriStand is not using it for encryption. It is being used by VeriStand to detect file changes. When Windows enforces FIPS encryption on VeriStand, it is not improving the security of the system. It is blocking a non-encryption function that looks like encryption. NI engineers are working to implement a different file change detection system in VeriStand that will not fail the FIPS check. This will be available in an upcoming release of VeriStand. Additionally, NI engineers are working to add encryption technologies to make VeriStand more secure. These encryption technologies will be FIPS 140 compliant. Thank you for patience as we work through this issue. |