Mattermost provides encryption-in-transit and encryption-at-rest capabilities. This page guides you through setting up appropriate encryption security.
Encryption is not required for GDPR, although it can be used as an additional safeguard against data breach.
Mattermost supports TLS encryption including AES-256 with 2048-bit RSA on all data transmissions between Mattermost client applications and the Mattermost server. You may either set up TLS on the Mattermost Server or install a proxy such as NGINX and set up TLS on the proxy. Refer to our configuration guide for more details.
Connections to Active Directory/LDAP can optionally be secured with TLS or stunnel.
In a High Availability mode, Mattermost supports encryption of cluster data in-transit when using the gossip protocol.
The encryption uses AES-256 by default, and it is not configurable. However, it is possible to manually set the value in the
Systems table for the
ClusterEncryptionKey row. A key is a byte array converted to base64. It can be set to a length of 16, 24, or 32 bytes to select AES-128, AES-192, or AES-256 respectively.
Encryption-at-rest is available for messages via hardware and software disk encryption solutions applied to the Mattermost database, which resides on its own server within your infrastructure. Encryption options at the disk level are documented both for MySQL and PostgreSQL.
For local storage or storage via Minio, encryption-at-rest is available for files stored via hardware and software disk encryption solutions applied to the server.
For Amazon’s proprietary S3 system, encryption-at-rest is available via server-side encryption with Amazon S3-managed keys in Enterprise Edition E20.