[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fwzDUqlbQrv2na2A3RaeWo1n751Djk0Clp9WRLQgQ2tk":3},{"item":4},{"id":5,"idKnowledge":6,"slug":7,"title":8,"description":9,"bodyMarkdown":10,"bodyHtml":11,"author":12,"date":13,"createdAt":14,"topics":15,"image":17,"hasDownload":18,"fileName":19},"38","47E5969D-3EB9-F44A-BCD1-D92AF078EBC9","your-filemaker-server-still-on-tls-1-1","Your FileMaker Server still on TLS 1.1?","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 […]","We still find clients with FileMaker Server installed on Servers supporting TLS 1.1., which is not a good situation to be in!  \n  \nIf 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.\n\nTLS 1.1 was officially **deprecated by the [Internet Engineering Task Force](https:\u002F\u002Fwww.ietf.org\u002F) (IETF) in 2020** due to multiple security vulnerabilities. It lacks modern cryptographic protections, making it susceptible to attacks such as **[BEAST](https:\u002F\u002Fdocs.digicert.com\u002Fen\u002Fcertcentral\u002Fcertificate-tools\u002Fdiscovery-user-guide\u002Ftls-ssl-endpoint-vulnerabilities\u002Fbeast.html#:~:text=In%20a%20BEAST%20attack%2C%20the,e.g.%2C%20HTTP%20authentication%20cookies\\).) (Browser Exploit Against SSL\u002FTLS)** and **padding oracle attacks**. Major browsers and platforms, including **Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge**, have already stopped supporting it.\n\nFileMaker 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**.  \n  \nAre you in doubt if your server is save, do a check here: [https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html](https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html)\n\nTo 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.\n\n**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):  \n  \n1\\. On windows open the REGISTRATION EDITOR.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_2.png)\n\n2\\. Go to the blow path:\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_3.png)\n\n3\\. Add the following keys and values and restart your server.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_4.png)","\u003Cp>We still find clients with FileMaker Server installed on Servers supporting TLS 1.1., which is not a good situation to be in!  \u003C\u002Fp>\n\u003Cp>If you’re running \u003Cstrong>FileMaker Server\u003C\u002Fstrong>, ensuring a secure connection between clients and your database is crucial. One security risk that still lurks in some configurations is \u003Cstrong>TLS 1.1\u003C\u002Fstrong>—a deprecated encryption protocol that should no longer be used.\u003C\u002Fp>\n\u003Cp>TLS 1.1 was officially \u003Cstrong>deprecated by the \u003Ca href=\"https:\u002F\u002Fwww.ietf.org\u002F\">Internet Engineering Task Force\u003C\u002Fa> (IETF) in 2020\u003C\u002Fstrong> due to multiple security vulnerabilities. It lacks modern cryptographic protections, making it susceptible to attacks such as \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fdocs.digicert.com\u002Fen\u002Fcertcentral\u002Fcertificate-tools\u002Fdiscovery-user-guide\u002Ftls-ssl-endpoint-vulnerabilities\u002Fbeast.html#:~:text=In%20a%20BEAST%20attack%2C%20the,e.g.%2C%20HTTP%20authentication%20cookies).\">BEAST\u003C\u002Fa> (Browser Exploit Against SSL\u002FTLS)\u003C\u002Fstrong> and \u003Cstrong>padding oracle attacks\u003C\u002Fstrong>. Major browsers and platforms, including \u003Cstrong>Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge\u003C\u002Fstrong>, have already stopped supporting it.\u003C\u002Fp>\n\u003Cp>FileMaker Server relies on \u003Cstrong>TLS to encrypt data transmissions\u003C\u002Fstrong>, ensuring that sensitive information remains protected. Keeping \u003Cstrong>TLS 1.1 enabled weakens this security\u003C\u002Fstrong>, leaving your FileMaker database exposed to potential exploits. Additionally, many modern compliance standards, such as \u003Cstrong>GDPR, PCI DSS, and HIPAA\u003C\u002Fstrong>, require the use of \u003Cstrong>TLS 1.2 or higher\u003C\u002Fstrong>.  \u003C\u002Fp>\n\u003Cp>Are you in doubt if your server is save, do a check here: \u003Ca href=\"https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html\">https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>To maintain security and compliance, you should \u003Cstrong>disable TLS 1.1 on your FileMaker Server\u003C\u002Fstrong> and ensure that only \u003Cstrong>TLS 1.2+\u003C\u002Fstrong> is used. By doing so, you safeguard your system from outdated encryption risks and protect your data from unauthorized access.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Need help disabling TLS 1.1?\u003C\u002Fstrong> Contact us for guidance on securing your FileMaker Server today or try it yourself and follow the steps below (this is a Windows example):  \u003C\u002Fp>\n\u003Cp>1. On windows open the REGISTRATION EDITOR.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_2.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>2. Go to the blow path:\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_3.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>3. Add the following keys and values and restart your server.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_4.png\" alt=\"\">\u003C\u002Fp>\n","jeroen","2025-02-12",1781519870000,[16],"FileMaker","\u002Fapi\u002Fknowledge\u002Fimage\u002F38\u002F?v=d4846d7f770f",false,""]