To keep up with security trends and threats, growing privacy concerns, and emerging technologies, we continually assess and update our SSL infrastructure. These changes often involve removing the ability to connect using outdated SSL ciphers.

What ciphers do we support?

Now that we have completed our hosting service improvements, only the following SSL ciphers are permitted:

• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

How do you make sure you're in compliance?

There are two primary areas of concern:

• Java: If you are using a current, up-to-date version of Java to run the EPIC data sync tool and/or your Integration Agent applications, there should be no further action required. If you are running an older version, you may need to update your Java security files to not allow the weaker ciphers listed above.
• REST requests: If you are using cURL (or PHP or another scripting language) to submit REST requests, make sure you update your cURL (or NSS libraries) to the latest version.

Of course, the best way to prepare for any kind of TLS or SSL change is to simply ensure that your applications and security protocols are kept up-to-date.