We still find clients with FileMaker Server installed on Servers supporting TLS 1.1., which is not a good situation to be in!

If you’re running FileMaker Server, ensuring a secure connection between clients and your database is crucial. One security risk that still lurks in some configurations is TLS 1.1—a deprecated encryption protocol that should no longer be used.

TLS 1.1 was officially deprecated by the Internet Engineering Task Force (IETF) in 2020 due to multiple security vulnerabilities. It lacks modern cryptographic protections, making it susceptible to attacks such as BEAST (Browser Exploit Against SSL/TLS) and padding oracle attacks. Major browsers and platforms, including Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge, have already stopped supporting it.

FileMaker Server relies on TLS to encrypt data transmissions, ensuring that sensitive information remains protected. Keeping TLS 1.1 enabled weakens this security, leaving your FileMaker database exposed to potential exploits. Additionally, many modern compliance standards, such as GDPR, PCI DSS, and HIPAA, require the use of TLS 1.2 or higher.

Are you in doubt if your server is save, do a check here: https://www.ssllabs.com/ssltest/analyze.html

To maintain security and compliance, you should disable TLS 1.1 on your FileMaker Server and ensure that only TLS 1.2+ is used. By doing so, you safeguard your system from outdated encryption risks and protect your data from unauthorized access.

Need help disabling TLS 1.1? Contact us for guidance on securing your FileMaker Server today or try it yourself and follow the steps below (this is a Windows example):

1. On windows open the REGISTRATION EDITOR.

2. Go to the blow path:

3. Add the following keys and values and restart your server.