---
schema_version: "1"
id: ca23a5e85d9504fa34427bd14a4756a203e6241df946bc4402bbe58c1e9c3a64
title: Enabling FIPS 140-2 on Mule Applications
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/2.7/enable-fips-140-2-compliance.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/2.7/enable-fips-140-2-compliance
source_site: docs.mulesoft.com
content_type: documentation
content_hash: dccaeb1a41885bc45703225028c1aac8d1a8f247ae83f2da47f9ff0ff68df5b9
description: MuleSoft Documentation Site
release: "2.7"
latest: false
---
---
product: Runtime Fabric
version: 2.7
---

# Enabling FIPS 140-2 on Mule Applications

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

You can configure Mule application containers to run in FIPS 140-2 compliance mode.

These instructions assume that you are familiar with
[FIPS 140-2](https://csrc.nist.gov/files/pubs/fips/140-2/upd2/final/docs/fips1402.pdf), the US
government security standard that requires that compliant parties use only cryptographic algorithms
and techniques that have been certified by NIST.

## Enable FIPS 140-2 Compliance Mode

1.  Using `kubectl`, patch the `custom-properties` secret in the `rtf` namespace by setting the
    `FIPS_ENABLED` key to `true`:

    ```copy
    # kubectl patch secret custom-properties -n rtf -p='{"stringData":{"FIPS_ENABLED": "true"}}'
    ```

    After making this change, when you deploy new applications or restart existing applications,
    their containers run in FIPS 140-2 compliance mode.

2.  To verify an application is running in FIPS 140-2 compliance mode, review the application’s
    startup log:

    ```copy
    # kubectl logs <app-pod-name> -n <env-id> -c app -f| grep -i fips

    Running in FIPS mode
    * Security model: fips140-2                                          *
    *  - mule.security.model = fips140-2
    ```