SSL Offloading Question

The security team and I are having a debate on how we want to setup the new Exchange system.  We will be using an F5 LB and they want traffic after the load balancer to be over port 80 instead of encrypted on 443.  The attached picture is how it would look.  

SSL Offloading
I would prefer to use SSL Bridging since it would be secure all the way through.

SSL Bridging
What are the security risks of doing SSL Offloading?

What would be the benefits of SSL Bridging vs SSL Offloading?

Thanks!
Sedgwick_CountyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam FarageEnterprise ArchCommented:
here are a few of the arguments I use for SSL bridging vs offloading:

- If you are doing SSL offloading, additional configurations need to be done at the IIS level for Exchange. During patches (for example, each CU in Exchange 2013 or SP in Exchange 2010 / 2007) these changes need to be backed up and reconfigured as IIS will be reset. This can cause additional downtime, along with complexity into the network. SSL bridging is mainly used for context routing (routing each request to the proper virtual directory) but re-encrypts the traffic, so configuration to the Exchange server is minimal.
- If you have a Rogue employee with a packet sniffer, all context of the Exchange packets (including passwords for some services) are sent via clear text. Someone on the internal network can figure out valuable PII and password data.

A big warning about SSL offloading, and that is proxy to a different site *will not work* for Exchange ActiveSync or OWA. So lets say you are having connections go into Site 1, but are going to proxy to a non-internet facing site (in this case, Exchange with the ExternalURL set to $NULL but the InternalURL set to something of value) then this wont work. The /proxy/ virtual directory will only accept connections over TCP 443, and not over TCP 80. Depending on your configuration, you might need to do SSL bridging only.
0
Sedgwick_CountyAuthor Commented:
Thank you for the response that helps a lot!  You mentioned that some passwords are sent clear text for some services, do you know by chance what services those are?
0
Adam FarageEnterprise ArchCommented:
So any CAS related service that comes into the environment (or from the client machines themselves) over TCP 443 would then be decrypted by the load balancer, and then transmitted to the load balanced CAS over TCP 80.

This means the following services:

- Outlook Anywhere
- Outlook Web App / Exchange Control Panel
- PowerShell (if you are load balancing it through there)
- Exchange ActiveSync
- Exchange Web Services
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSL / HTTPS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.