Skip to main content

Table of Contents

Creating automations that are Federal Information Processing Standard (FIPS) compliant

Pega Robotic Automation 8.0 SP1 and later is compliant with Federal Information Processing Standard (FIPS) 140-2 standards. FIPS is a set of cyber security standards that are defined by the National Institute of Standards and Technology (NIST) and are used by the United States and Canadian governments. The FIPS standard defines the minimum security requirements for securing sensitive but unclassified information. FIPS is mandated in some government agencies and is optionally followed in commercial and non-governmental organizations.

The FIPS 140 standard defines the approved cryptographic algorithms that you can use and establishes the requirements for generating and managing keys. For more information about FIPS, see the National Institute of Standards and Technology website. For more information about how Microsoft operating systems handle FIPS validation, see FIPS 140 Validation.

You do not have to make any changes to Pega Robotic Automation to create automations with FIPS support.

To enable FIPS-compliant encryption on Windows, log in as an administrator and apply a local group policy setting or by editing a registry key.

  • Enable the system cryptography use FIPS-compliant algorithms for encryption, hashing, and signing in the Local Policy security options.
  • Change the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy Windows registry entry to ‘1’.
Suggest Edit
Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us