Home > Forefront TMG 2010, Forefront UAG 2010, Remote Access, Security, Threat Management Gateway, Unified Access Gateway > Recommended Forefront TMG 2010 SSL and TLS Configuration

Recommended Forefront TMG 2010 SSL and TLS Configuration

September 8, 2014

Last year I wrote an article for ISAserver.org that provided detailed guidance for improving security for SSL and TLS protected web sites using Forefront TMG 2010. Many people have reached out to me recently to ask about enabling forward secrecy, which my original article did not include because, at the time, it was not recommended to enable it. However, as times have changed, it is now recommended to enable forward secrecy so I recently wrote a short post with guidance on how to do that. The post was written with a very narrow scope and addressed only the enabling of forward secrecy for TLS. Many of you have since asked for guidance on overall security best practices with regard to SSL and TLS along with adding support for forward secrecy. In addition to the configuration changes detailed in my original ISAserver.org article, I also recommend the following list of SSL and TLS cipher suites be explicitly enforced using the method outlined here.

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256
TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
TLS_DHE_DSS_WITH_AES_128_CBC_SHA
TLS_DHE_DSS_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA

Using this configuration, the Forefront TMG 2010 firewall should receive an A rating from the SSL Labs test site (at the time of this writing).

Forefront TMG 2010 SSL Security Configuration

Enabling and supporting the above list of cipher suites will provide the best overall protection and performance for your SSL protected web sites. Note that the list above does not include support for SSL 3.0. If you need to support SSL 3.0 you should add the following cipher suites to the end of the list.

TLS_RSA_WITH_RC4_128_SHA
TLS_RSA_WITH_RC4_128_MD5

Please note that this configuration may not work with older browsers on old, unsupported operating systems, for example Internet Explorer 6 on Windows XP. Before deploying this configuration in production I would encourage you to conduct some testing with your supported clients to ensure operability.

  1. Mark Haddon
    November 13, 2014 at 1:11 am

    This has been very useful to us but could it be updated to include the new cipher suites introduced by KB2992611?
    I would also find an article explaining why the suites are in a specific order very useful to help me to understand this. I’m assuming the order is Exchange, Encryption and then Hash with each item sorted in descending order?

  2. December 3, 2014 at 5:22 am

    Thanks for the suggestion Mark. I’ll have a look at that soon and update the article accordingly. To learn more about cipher suites, I’d suggest reading Ivan Ristic’s new book entitled Bulletproof SSL and TLS. You’ll find it includes all the information you’ll need regarding cipher suites and SSL/TLS implementation.

    Thanks! 🙂

  3. Mark Haddon
    December 3, 2014 at 5:47 am

    cheers Richard. I see if I can dig it out 🙂 Gotta be worth a read just for the Feisty Duck

  4. Mark Haddon
    November 25, 2015 at 7:07 am

    Just chancing my hand here in case you have an insight into this but https://www.ssllabs.com/ssltest has started showing a fail of 3. Extra Download under Certification Paths: Path #2: Trusted when scanning SSL sites. We still get an A rating from SSLLabs but PCI scans have failing as Untrusted in the last week? Any ideas?
    we get
    SSL Certificate – Signature Verification Failed Vulnerability
    Exception:
    If the server communicates only with a restricted set of clients who have the server certificate or the trusted CA certificate, then the server or CA certificate may not be available publicly, and the scan will be unable to verify the signature.
    Solution:
    Please install a server certificate signed by a trusted third-party Certificate Authority.
    Result:Certificate #0 CN=REDACTED, OU=Domain_Control_Validated unable to get local issuer certificate

  5. November 25, 2015 at 8:05 am

    Hi Mark,

    Can you email me the URL you are testing so I can view the results for myself?

  1. September 23, 2014 at 7:05 am
Comments are closed.