---
schema_version: "1"
id: 53f28d722a5510b8134d7c48714d88a8c19380deb022378427fc61ffcbf08104
title: Hardening Mule Runtime on Runtime Fabric
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/2.10/configure-hardening.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/2.10/configure-hardening
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 822b01eaf7528948d13734f220bad0fb265d702ee5c33cea3f356ec3ec31cd04
description: MuleSoft Documentation Site
release: "2.10"
latest: false
---
---
product: Runtime Fabric
version: 2.10
---

# Hardening Mule Runtime on Runtime Fabric

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

By design, Runtime Fabric automatically applies and enables hardening measures for your Mule
applications. By following containerization best practices, isolation at the Mule and application
level is achieved by default.

The following hardening checklist provides additional information and best practices for Mule
hardening with Runtime Fabric.

## Hardening Checklist

<table><caption>Table 1. Mule Hardening Procedure</caption> <colgroup><col> <col></colgroup><thead><tr><th>Hardening Step</th><th>Action Required</th></tr></thead><tbody><tr><td><p>Run Mule as a non-privileged User.</p></td><td><p>Runtime Fabric provides this functionality.</p></td></tr><tr><td><p>Install Mule as a Service</p></td><td><p>Runtime Fabric provides this functionality by deploying a Mule runtime engine for each application within its own container.</p></td></tr><tr><td><p>Configure Mule to write logs or temporary files within appropriate locations. Configure logs, passwords, and keystore files.</p></td><td><p>Runtime Fabric provides this functionality. Mule writes to a temporary file system that is deleted when the application terminates. Monitoring information is collected from a sidecar agent in a specific location on disk where metrics are outputted and stored. Logs are collected from standard output streams.</p></td></tr><tr><td><p>In some situations, you must configure usernames, passwords, and keystores on Mule. Usually, these settings are made available externally, so that DevOps can change these settings.</p></td><td><p>Runtime Fabric provides this functionality. Refer to <a href="https://docs.mulesoft.com/runtime-fabric/2.10/manage-secure-properties">Manage Secure Properties in Runtime Fabric</a> for additional information.</p></td></tr><tr><td><p>Manage certificates in a keystore file.</p></td><td><p>This is supported on Runtime Fabric, but you must import the certificates into the keystore.</p></td></tr><tr><td><p>Use a separate property file to store usernames and passwords and secure it using file system permissions.</p></td><td><p>Runtime Fabric provides this functionality. Refer to <a href="https://docs.mulesoft.com/runtime-fabric/2.10/manage-secure-properties">Manage Secure Properties in Runtime Fabric</a> for additional information.</p></td></tr></tbody></table>