sym
dope

You missed your connectION. Would you like tO Fly Direct?

Make the switch from Broadcom (aka Symantec) Cloud Secure Web Gateway to dope.swg.
[ fka symantec fka bluecoat ]
NO_MEETING_REQUIRED+++WE_PROMISE

|||||||||||||||||||||||||||||||||

Why should you move from Symantec to dope.swg?

01
01
We’re reliable
Without relying on datacenters allows us to work consistently in every country and network. You’ll never have to worry about datacenter outages again.
02
02
We’re FAST AF
With local SSL inspection, HTTP2 is supported on day one and your connection is never degraded down to HTTP1.1. It’s so smooth, you won’t even notice we’re running in the background.
03
03
We’re PRIVATE
We never do SSL inspection outside of your device’s safe zone. Decryption happens locally, so the only data we save in the cloud are processed transaction records sent to the region of your choice.
SYM_01

||||||||||||||||||||||||||||||||| STOPOVER DATACENTERS
Wait, are datacenters
really that bad?
Well, why would you use them if you didn’t need to? That’s like unnecessarily booking a stopover in another country when you could fly direct. Choosing a stopover is choosing to inspect SSL outside of your device. It’s a huge (SWG) box of red flags.

Datacenters come at a high cost. If there are any outages or degradations around the world, it can have an impact on you.  And if your closest datacenter goes down, your data could be rerouted to a completely different country—slowing you down in the process.
sym_02

||||||||||||||||||||||||||||||||| HTTP2 DOWNGRADED
symantec DOesn’T SUPPORT HTTP2?
WHY iS THAT?
Ask them. Legacy players built the stopover architecture with the proxies they already. Without support for HTTP/2 traffic inspection, all your traffic is getting downgraded to HTTP/1.1 which causes slow loading speeds. Why should you be forced to downgrade?

More importantly, why has it taken so long for these legacy companies to get with the program?