MyGate has begun the phased disablement of the TLS 1.1 and lower encryption protocol. To continue uninterrupted access to MyGate after the disablement date, we require that all customers support a more secure version of TLS. TLS 1.2 will be the new minimum standard security protocol used by MyGate in order to align with industry-wide best practices for security and data integrity.
What is TLS?
TLS stands for “Transport Layer Security.” It is a protocol that provides privacy and data integrity between two communicating applications. It’s the most widely deployed security protocol used today, and is used for web browsers and other applications that require data to be securely exchanged over a network. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification. The versions of TLS, to date, are TLS 1.0, 1.1 and 1.2.
MyGate web console and API connections use TLS as a key component of their security.
What is the change?
MyGate is requiring an upgrade to TLS 1.2 by November 1, 2017. On that date, we will begin disabling the TLS 1.1 and lower encryption protocols, which will prevent customers still using it from accessing MyGate services.
How will customers be impacted?
After MyGate disables TLS 1.1 and lower, any inbound connections to MyGate services that rely on TLS 1.1 or lower will fail. This will impact MyGate services access to websites and API’s.
How can customers avoid a service disruption?
The action required by your organization will depend on which channels are used to access your MyGate services. See the relevant topic below for the required actions.
You and your users will experience issues accessing MyGate web console if you have disabled the supported encryption protocols or if a browser other than the supported browsers* is being used
- Microsoft® Internet Explorer® version 9, 10, and 11
- Apple® Safari® version 10.x on macOS
- Microsoft Edge for Windows® 10
- The most recent stable versions of Mozilla® Firefox®
- The most recent stable versions of Google Chrome™
If you experience errors, you need to ensure your browsers are compatible with TLS 1.2. If your browser is not compatible with TLS 1.2 after we make this change, your users will NOT be able to access MyGate web console. We recommend that you begin planning to support TLS 1.2 as soon as possible.
If you have any API Integrations, please ensure that the TLS 1.1 and/or TLS 1.2 encryption protocol is enabled in those integrations.
If your integrations that use connections to MyGate API integrations do not have TLS 1.2 enabled after we make this change, your integrations may experience disruption. We recommend that you begin planning to support TLS 1.2 as soon as possible.
Why is this happening?
At MyGate, Trust is our number one value and MyGate is focused on continually helping our customers improve their security by using the latest security protocols. On November 1, 2017, MyGate will require TLS 1.2 encryption protocol in an effort to maintain the highest security standards and promote the safety of customer data.
Where can I find more information?
You can read more about this on the PCI Security Standards Council blog at https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls