MuleSoft common coding mistakes #3 – Lack of encryption for sensitive data

MuleSoft applications may not encrypt sensitive data, such as passwords, which could result in data breaches. This data may be present anywhere in the Mule code including XML, RAML or properties. Integral Zone’s IZ Analyzer can identify such sensitive information in the properties file and prompt the developers in real-time to encrypt them through Anypoint Studio plugin.

db.user=root
db.password=root123

Built in rule that can identify lack of encrption of sensitve data is

Rule Example(s):
M00151 - PROPERTY/YAML FILE - Sensitive data NOT encrypted