From 1502f912b12fa179102f7abb84333a786870e1fc Mon Sep 17 00:00:00 2001 From: Cristian Date: Thu, 16 Jul 2026 17:41:46 -0300 Subject: [PATCH] W-23475852-Add-FIPS-compliance-to-ACB-docs-CP --- .../int-run-mule-apps-with-properties.adoc | 1 + .../modules/ROOT/pages/ref-mule-settings.adoc | 28 +++++++++++++++++++ 2 files changed, 29 insertions(+) diff --git a/code-builder-home/modules/ROOT/pages/int-run-mule-apps-with-properties.adoc b/code-builder-home/modules/ROOT/pages/int-run-mule-apps-with-properties.adoc index 8b808d731..4094b19ca 100644 --- a/code-builder-home/modules/ROOT/pages/int-run-mule-apps-with-properties.adoc +++ b/code-builder-home/modules/ROOT/pages/int-run-mule-apps-with-properties.adoc @@ -417,6 +417,7 @@ Then update the single workspace-level key reference and all projects work immed * xref:int-create-secure-configs.adoc[] * xref:int-run-multiple-mule-apps.adoc[] * xref:ref-mule-settings.adoc#setting-mule-args[Mule › Runtime: Default Arguments] +* xref:ref-mule-settings.adoc#setting-fips[Mule › Runtime: FIPS Compliance] * xref:int-global-config-elements.adoc[] * xref:start-workspaces.adoc[] * xref:mule-runtime::configuring-properties.adoc[] diff --git a/code-builder-home/modules/ROOT/pages/ref-mule-settings.adoc b/code-builder-home/modules/ROOT/pages/ref-mule-settings.adoc index b906346e9..1fbc0ef20 100644 --- a/code-builder-home/modules/ROOT/pages/ref-mule-settings.adoc +++ b/code-builder-home/modules/ROOT/pages/ref-mule-settings.adoc @@ -84,6 +84,34 @@ Typically, the default of *1g* (1 GB) is sufficient. However, you can change the If you are using the cloud IDE, be aware of the memory available to the container before changing this value. //TODO: HOW WOULD THEY KNOW +[[setting-fips]] +== Mule › Runtime: FIPS Compliance + +Use Mule runtime FIPS settings to configure local runtime behavior for regulated environments. + +[%header,cols="35,65"] +|=== +|Setting |Description + +|`mule.runtime.fipsEnabled` +|Enables FIPS runtime behavior when set to `true`. The default is `false`. + +|`mule.runtime.fipsMode` +|Selects the compliance mode, such as FIPS 140-2 or FIPS 140-3. + +|`mule.runtime.fipsCustomCacertsPath` +|Optional path to a custom `cacerts` file for FIPS workflows. +|=== + +When FIPS is enabled, Mule runtime initialization can include FIPS-specific startup behavior and keystore handling required for compliant execution. + +This setting doesn't, by itself, certify an application as compliant. Configure Mule runtime and dependencies to meet your organization and regulatory requirements. + +For Mule runtime requirements and setup instructions, see: + +* xref:mule-runtime::fips-140-2-compliance-support[] +* xref:mule-runtime::fips-140-3-compliance-support[] + [[setting-region]] == Mule: Control Plane