Text of docs.gitlab.com › development › fips_gitlab as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

FIPS 140-2 and 140-3 | GitLab Docs

/ FIPS 140-2 and 140-3 FIPS is short for “Federal Information Processing Standard”, which defines certain security practices for a “cryptographic module” (CM). A cryptographic module is set of hardware, software, or firmware that implements approved security functions (including cryptographic algorithms and key generation) and is contained within a cryptographic boundary. At GitLab, a cryptographic module almost always refers to an embedded software component of another product or package release and is specific to a particular version of a binary.

For example, a particular version of Ubuntu Kernel Crypto API cryptographic module or the OpenSSL project’s FIPS Provider. A module is validated after it completes testing by a NIST-certified laboratory and has an active certificate listed in the Cryptographic Module Validation Program . A cryptographic module must be compiled, installed, and configured according to its CMVP security policy. Regulatory requirements GitLab is committed to releasing software for our customers who are required to comply with FIPS 140-2 and 140-3.

FIPS 140 is a requirement to do business within the U.S. public sector, as well as some non-U.S. public sector organizations and certain industries depending on the use case (healthcare, banking, etc.). FIPS 140-2 and FIPS 140-3 requirements are applicable to all U.S. Federal agencies, including software they purchase whether that be GitLab Self-Managed or cloud. Agencies must use cryptographic-based security systems to provide adequate information security for all operations and assets as defined in 15 U.S.C.

§ 278g-3. Non-validated cryptography is currently viewed as providing no protection to the information or data. In effect, the data would be considered unprotected plaintext. If the agency specifies that the information or data be cryptographically protected, then FIPS 140-2 or FIPS 140-3 is applicable. In essence, if cryptography is required, then it must be validated. Should the cryptographic module be revoked, use of that module is no longer permitted.

The challenge is that the use of FIPS-validated modules requires use of specific versions of a software package or binary. Historically, some organizations would pin or version-lock to maintain compliance. The problem is that these validated modules inevitably become vulnerable, and the long lead time associated with obtaining validation for a new version means it is impractical to consistently achieve both federal mandates: Use of validated modules.

The timely mitigation of vulnerabilities. The regulatory environment and policymaking in this area is dynamic and requires close monitoring by GitLab. Terms to avoid These phases are used extensively at GitLab and among software providers. However, we should aim to avoid using them and update our documentation. “FIPS compliant” or “FIPS compliance”: These are not official terms defined by NIST or CMVP and therefore should not be used because it leaves room for ambiguity or subjective interpretations.

Compliance with FIPS 140 requires adherence to the entire standard and all security requirements for cryptographic modules, including the strict use of CMVP-validated modules, CMVP-approved security functions, CMVP-approved sensitive parameter generation and establishment methods, and CMVP approved authentication mechanisms. This term is often synonymous with using “CMVP-approved security functions”, which is only one aspect of the standard.

Terms to use The following official terms and phrases are approved for use by the CMVP. “FIPS 140-2 Validated” or “FIPS-validated” when referring to cryptographic modules that have a CMVP certificate and number. “FIPS 140-2 Inside” or “FIPS inside” when referring to a product that embeds FIPS-validated modules, such as GitLab, a GitLab software component, or GitLab-distributed software. If a product has a FIPS 140-2 module internal to the product and uses a FIPS official logo, “FIPS 140-2 Inside” and the certificate number must also accompany the logo.

“CMVP-approved security functions” or “FIPS-approved algorithms”: While technically the latter is not an official phrase, it communicates the same thing and provides additional context to those who are unfamiliar with NIST terminology. This is referring to NIST SP 800-140C which specifies the CMVP-approved cryptographic algorithms and their authorized use cases. GitLab implementation of FIPS 140 GitLab is a SaaS First company and, as such, we follow the latest guidance from the Federal Risk and Authorization Management Program (FedRAMP) .

FedRAMP requires cloud service providers to use FIPS-validated cryptographic modules everywhere cryptography is required including for encryption, hashing, random number generation, and key generation. However, per control SC-13 from the FedRAMP security controls baseline, it is acceptable to use a cryptographic module that is not FIPS-validated when: A FIPS-validated version has a known vulnerability. A feature with vulnerability is in use.

A non-FIPS version fixes the vulnerability. The non-FIPS version is submitted to NIST for FIPS validation. That is, listed under Modules In Process or Implementation Under Test on CMVP website. POA&M is added to track approval and deployment when ready. FedRAMP released a draft (read: subject to change) Policy for Cryptographic Module Selection and Use which aims to provide more practical implementation guidance. Notably, the preference to remediate known vulnerabilities through patches or updates over continuing to use known-vulnerable software that is FIPS-validated because the presence of known vulnerabilities creates risks that outweigh the assurance value provided through validation.

As required by CSP01 in this draft policy, GitLab takes the stance of applying patches to cryptographic modules. The order of preference for cryptographic module selection per CSP10 is as follows: Mitigate the vulnerability in the validated module. Use an unvalidated module, in the following order of preference: Module is substantially similar to a FIPS-validated module; validated algorithm. FIPS validation in process for module; validated algorithm.

Expired FIPS validation for a previously validated module; validated algorithm. Module not in FIPS validation process; validated algorithm. Algorithm is approved and tested but not yet validated, and the module is not in FIPS validation process. Validation workflow Third party assessment organizations (3PAOs) validate the use of a FIPS-validated CM by: Checking the certificate number. Validating that the CM is configured in an approved mode and only uses algorithms listed as approved in the CM’s security policy.

GitLab also does internal continuous monitoring and, in the past, has contracted independent auditors to audit our software against the FIPS 140 standard. Results are available in the Trust Center. GitLab FIPS-approved software GitLab currently releases software for Omnibus (Linux package) deployments, cloud-native (Helm chart) deployments, GitLab Runner, security analyzers, and more. As stated above, GitLab follows FedRAMP guidance and, as such, we strive to include FIPS 140-2 validated modules (FIPS inside) when possible but, at minimum, includes FIPS-approved algorithms (CMVP-approved security functions).

GitLab favors security over compliance in situations where it is not possible to achieve both with respect to FIPS 140-2. AI Gateway A FIPS-validated AI Gateway Docker image is available for GitLab Duo Self-Hosted deployments. The image is built on Red Hat UBI 9 and uses the CMVP-validated OpenSSL FIPS provider. For installation instructions, see FIPS-validated images . Unsupported features in FIPS mode Some GitLab features may not work when FIPS mode is enabled.

The following features are known to not work in FIPS mode. However, there may be additional features not listed here that also do not work properly in FIPS mode: Contain

The rest of this page is on the live site.