Skip to content

W-23475852-Add-FIPS-compliance-to-ACB-docs-CP #681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Crispy-Salesforce wants to merge 1 commit into
base: MS2026-07-21-ACB-1-24
Choose a base branch
from
+29 −0
Open

W-23475852-Add-FIPS-compliance-to-ACB-docs-CP #681

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions code-builder-home/modules/ROOT/pages/int-run-mule-apps-with-properties.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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[]
28 changes: 28 additions & 0 deletions code-builder-home/modules/ROOT/pages/ref-mule-settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down