---
schema_version: "1"
id: a4bd29ed83dd82442d9cab168a078513e6b14ece4c08d61732e5c31c5d3aa6c0
title: Security
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-sdk/latest/security-best-practices.md
canonical_url: https://docs.mulesoft.com/mule-sdk/latest/security-best-practices
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 089b162d0a7615880a819f88dbb33afd1d98d6a5983d5b738b847884524c083b
description: MuleSoft Documentation Site
release: "1.13"
latest: true
---
---
product: Mule SDK
version: 1.13
is-latest-version: true
---

# Security

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

The module **must** follow all standard security best practices.

In particular, the following **should** be given special consideration:

- Protect against XXE attacks

- Always sanitize information from untrusted sources

- When reading files from the local file system, make sure not to access secrets of the host
  environment nor enable path traversal

- When possible, use CSRF tokens

- When executing queries to a database, make correct use of PreparedStatement class to avoid SQL
  injection attacks.

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [Mule SDK Development Best Practices](https://docs.mulesoft.com/mule-sdk/latest/best-practices)