GoAnywhere Can be Configured to Run in FIPS 140-2 Compliance Mode
Security Requirements for Cryptographic Modules are formalized in the Federal Information Processing Standard (FIPS publication 140-2), developed by the US National Institute of Standards and Technology (NIST) and Canadian Communication Security Establishment (CSE).
GoAnywhere can be configured to run in FIPS Compliance Mode. This setting will help prevent users from encrypting files with anything other than validated FIPS 140-2 compliant cryptographic algorithms (e.g. AES).
The FIPS 140-2 certified algorithms in GoAnywhere MFT are provided by an embedded Bouncy Castle module and apply to all SSH and SSL communications within GoAnywhere MFT including SFTP, SCP, FTPS, PeSIT, and HTTPS protocols.
Bouncy Castle Provides an open-source cryptographic API supported by Keyfactor. By leveraging Bouncy Castle's extensive experience with encryption technology and compliance criteria, GoAnywhere is able to satisfy the stringent requirements for FIPS 140-2.
The Bouncy Castle security module in GoAnywhere MFT is unmodified and is certified under NIST Certification 3514, which was last validated Feb. 8, 2022.
Note: GoAnywhere MFT helps its users comply with FIPS 140-2 through its use of the underlying FIPS-certified security module, Bouncy Castle.