---
schema_version: "1"
id: 0486800113f0bf35d12f9e9f271e72793a33949b4d124a8ce87fa59b41629a2e
title: Configuring FIPS Compliance in Anypoint Code Builder
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/start-fips-compliance.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/start-fips-compliance
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 6a6539e13fba7ea862660ee61435f3caf0e2ad96acb0cdd3fd408d0ff781e3f0
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Configuring FIPS Compliance in Anypoint Code Builder

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Configure Anypoint Code Builder to run in FIPS 140-2 or FIPS 140-3 compliant environments. When FIPS
mode is enabled, Anypoint Code Builder configures the embedded JVM to use Bouncy Castle FIPS
(BCFIPS) cryptographic modules and generates a FIPS-compliant keystore for your Mule applications.

FIPS support in Anypoint Code Builder is functionally equivalent to FIPS support in Anypoint Studio.
The configuration experience reflects the VS Code settings interface.

## Before You Begin

- [Install and set up Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-acb-desktop).

- Make sure the Mule runtime you use is FIPS 140-3 compliant. Mule runtime 4.9 (LTS) or 4.10 and
  later supports FIPS 140-3 compliance.

- Use Java 17 when running Mule runtime 4.9.

## Configure FIPS Compliance

Enable FIPS mode in Anypoint Code Builder settings:

1.  Open MuleSoft Settings:

    \+ .Show me how

- From the Anypoint Code Builder panel, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-settings-gear.png) (gear) icon.

- From the activity bar, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-settings-gear.png) (gear) icon, select
  **Settings**, and search for `mule` in the **Settings** tab.

- Provide the command `MuleSoft: Open ACB Settings` in the
  [Command Palette](https://docs.mulesoft.com/anypoint-code-builder/start-use-command-palette).

1.  Find the **Mule > Runtime: Fips Enabled** setting.

2.  Select the checkbox to enable FIPS compliance mode.

    When enabled, the embedded JVM is configured to use Bouncy Castle FIPS modules. This setting is
    required for regulated PCE and GIA2H environments.

3.  In the **Mule > Runtime: Fips Mode** dropdown, select the FIPS compliance level:

    - **FIPS 140-2**

    - **FIPS 140-3**

      This setting only applies when FIPS compliance mode is enabled.

4.  Optionally, set a path in **Mule > Runtime: Fips Custom Cacerts Path** if you need to use a
    custom `cacerts` file.

    If not specified, the default `cacerts` from the JDK is used. When FIPS mode is enabled, this
    file is automatically converted to BCFKS format.

## FIPS Mode Effects

When you enable FIPS mode, Anypoint Code Builder automatically configures the following:

- BCFIPS libraries

  Bouncy Castle FIPS JARs are included in the Mule runtime boot classpath to provide FIPS-validated
  cryptographic implementations.

- Custom `java.security` file

  A `java.security` file is dynamically generated to configure the JVM to use BCFIPS providers for
  all security operations. The file supports both FIPS 140-2 and FIPS 140-3.

- BCFKS keystore

  A keystore in Bouncy Castle FIPS KeyStore (BCFKS) format is created based on your existing or
  default keystore. BCFKS is the recommended FIPS-compliant format for storing keys and
  certificates.

- Run configuration

  Each Mule application run configuration is updated with the required FIPS parameters.

## See Also

- [MuleSoft Settings](https://docs.mulesoft.com/anypoint-code-builder/ref-mule-settings)

- [Pass Runtime Properties and Arguments to Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-run-mule-apps-with-properties)