SummaryGoogle Encrypted traffic is encrypted traffic to/from Google services, but the Exinda cannot see more information about it.
OverviewStarting in 2013, there was a large push for websites to use SSL by default in order to be more secure on the internet. As a result, many websites enable SSL access by default and will automatically redirect non SSL traffic to their SSL port. Google is one of the sites that will do this automatically. As a result, on the Exinda, an application definition was made called "Google Encrypted" in order to properly classify the traffic going to Google's servers that was Encrypted.
It is possible in the Exinda to see a significant number of "Google Encrypted" connections being made, alongside other standard definitions such as "Google Docs" and "Google Drive". These Google Encrypted connections are the parts of each service that are encrypted.
However, due to the nature of SSL encryption, the Exinda is unable to monitor any more specific information about the traffic. The encryption key is specific to the client-server key exchange done between the end user and the Google servers. This encrypted traffic is passed through the Exinda, and while there is a footprint to know in general what type of traffic it is, it cannot look at the more detailed information to know specifically what service it is going to in Google's enterprise.