Enable FIPS mode for WPM on remote systems
If FIPS mode is enabled on the Orion server, you can also enable FIPS mode on remote systems that host the Web Transaction Recorder and the WPM Player service by adjusting Windows OS settings.
WPM behaves differently if FIPS mode is enabled. For example, recordings and transactions created in earlier versions of WPM may fail. CPU and memory usage may also be impacted on remote systems. See FIPS compliance in WPM for details.
After enabling FIPS mode on the Orion server, you can use a Group Policy Editor to enable FIPS mode on remote machines:
- For systems that aren't joined to a domain, use the Local Group Policy editor to enable FIPS mode, as described next.
- For systems joined to a domain, ask a System Administrator to update Group Policy settings.
To enable FIPS on a remote system:
- In the left pane of the Group Policy Editor, expand Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
- In the right pane, select "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing."
- In the dialog box that appears, click Enabled, and then click OK.
- Restart the system.
Alternatively, apply Group Policy Objects (GPOs) posted in the Security Technical Implementation Guides (STIGs) Document Library to remote systems to enable FIPS.