We’ve asked the companies in our Who Has Your Back Program what they are doing to bolster encryption in light of the NSA’s unlawful surveillance of your communications. As of now, eight companies—Dropbox, Facebook, Google, Microsoft, Sonic.net, SpiderOak, Twitter, and Yahoo—are implementing five out of five of our best practices for encryption. See the infographic.
By adopting these practices, described below, these service providers have taken a critical step towards protecting their users from warrantless seizure of their information off of fiber-optic cables. By enabling encryption across their networks, service providers can make backdoor surveillance more challenging and require the government to go to courts and use legal process.
While not every company in our survey has implemented every recommendation, each step taken helps, and we appreciate those who have worked to strengthen their security. We hope that every online service provider adopts these best practices and continues to work to protect their networks and their users.
Crypto Survey Results
|Encrypts data center links||Supports HTTPS||HTTPS Strict (HSTS)||Forward Secrecy||STARTTLS|
|in progress for select domains, see notes|
planned Q2 2014
default for Mail; planned 2014 for all
yahoo.com; planned 2014 for all
Notes: The information in this chart comes from several sources; the companies who responded to our survey questions; information we have determined by independently examining the listed websites and services, and published reports. Some of the surveyed companies did not respond to the survey.
Recognizing that some of these steps will take time to implement, we gave credit to companies that either (1) have implemented or (2) have concrete plans to implement the listed encrytion process, as noted.
For STARTTLS, the red and grey shading indicates whether or not the company is a major email service provider. While encourage all companies to implement STARTTLS, even if they only provide email for their own employees, the issue is most critical for companies that provide email communications to the public.
Google implements HSTS on accounts.google.com for all browsers that support HSTS, which at the time of this writing are Chrome, Chromium, Firefox, Opera, and Safari. HSTS on other Google domains is only functional in Chrome, Chromium, and Safari.
This graphic is also available as an image file.
Updates to This Chart
The first version of this chart was published in November, 2013. Since then, we've continuously updated it as companies have provided more information and made changes to their implementation plans.
November 20, 2013: Facebook and Tumblr have provided further information to supplement the Encrypt the Web Report. We're pleased to report that Tumblr is planning to upgrade its web connections to HTTPS this year and implement HSTS by 2014, and Facebook is working on encrypting data center links and implementing STARTTLS.
November 22, 2013: Google has provided further information to supplement the report on its use of HSTS. See the updated chart below and the notes for more information.
December 5, 2013: Microsoft has provided further information, announcing a plan to expand encryption across all its services, including encrypting links between data center and implementing forward secrecy by the end of 2014.
December 16, 2013: Microsoft has informed us that it is planning to support HSTS for public facing services that host or transmit email, personal or business documents and media, messaging, contacts, and credentials. This is an important step to make it more challenging for attackers to defeat security by bypassing encryption. In addition, Microsoft is planning to roll out STARTTLS in its outlook.com email service. This means that emails between outlook.com users and other email services that use STARTTLS, like Gmail, will be encrypted in transit.
December 19, 2013: An earlier version of this report incorrectly stated that the HSTS preload list in Firefox for Google domains was non-functional due to a bug. Firefox enables HSTS preloading but intentionally rejects domains that do not send an HSTS header with expiration time greater than 18 weeks. As far as we can tell, there are no Google domains that meet this requirement. We urge Google to change their HSTS implementation so that Firefox and Opera users receive the security benefits of HSTS.
March 13, 2014: Twitter has implemented STARTTLS for emails sent from its service to users—an especially important step, given that the contents of Direct Messages may be included in these updates. We've updated the chart to recognize their work in that category, bringing the company to a full five checkmarks.
Tumblr has released optional SSL as a setting for logged in users viewing their dashboards, and plan to roll it out as a default in the next several months. HSTS support is still planned in 2014.
April 2, 2014: Yahoo has announced a number of improvements to its security offerings, bringing it up to a full five checkmarks.
June 6, 2014: As part of the Reset The Net campaign, Automattic has announced that all subdomains of Wordpress.com—including the huge number of user blogs there—will be served exclusively over HTTPS by the end of 2014. Its HTTPS implementation supports perfect forward secrecy.
July 2, 2014: Microsoft has implemented several of its planned changes, including bringing STARTTLS to Outlook.com and enabling forward secrecy on those connections and on connections to its OneDrive system.
November 4, 2014: We've removed the "planned" designation from Facebook's HSTS checkmark to acknowledge that they've fully implemented that feature. Currently Facebook only delivers the HSTS header to browsers on a supported whitelist, which means that some tests may not reflect that it is implemented.
Why Crypto Is So Important
The National Security Agency’s MUSCULAR program, which tapped into the fiber-optic lines connecting the data centers of Internet giants like Google and Yahoo, exposed the tremendous vulnerabilities companies can face when up against as powerful an agency as the NSA. Bypassing the companies’ legal departments, the program grabbed extralegal access to your communications, without even the courtesy of an order from the secret rubber-stamp FISA court. The program is not right, and it’s not just.
With that in mind, EFF has asked service providers to implement strong encryption. We would like to see encryption on every step of the way for a communication on its way to, or within, a service provider’s systems.
For starters, we have asked companies to encrypt their websites with Hypertext Transfer Protocol Secure (HTTPS) by default. This means that when a user connects to their website, it will automatically use a channel that encrypts the communications from their computer to the website.
We have also asked them to flag all authentication cookies as secure. This means cookie communications are limited to encrypted transmission, which directs web browsers to use these cookies only through an encrypted connection. That stops network operators from stealing (or even logging) users' identities by sniffing authentication cookies going over insecure connections.
To ensure that the communication remains secure, we have asked companies to enable HTTP Strict Transport Security (HSTS). HSTS essentially insists on using secure communications, preventing certain attacks where a network pretends that the site has asked to communicate insecurely.
All of these technologies are now industry-standard best practices. While they encrypt the communications from the end user to the server and back, the MUSCULAR revelations have shown this is not enough. Accordingly, we have asked service providers to encrypt communications between company cloud servers and data centers. Anytime a user's data transits a network, it should be strongly encrypted, in case an attacker has access to the physical data links or has compromised the network equipment.
In addition, we have asked for email service providers to implement STARTTLS for email transfer. STARTTLS is an opportunistic encryption system, which encrypts communications between email servers that use the Simple Mail Transfer Protocol (SMTP) standard. When a user emails someone on a different provider (say, a Hotmail user writing to a Gmail user), the mail message will have to be delivered over the Internet. If both email servers understand STARTTLS, then the communications will be encrypted in transit. If only Gmail does but Hotmail does not (the current situation), they will be in the clear and exposed to eavesdropping, so it’s critical to get as many email service providers as possible to implement the system.
Finally, we have asked companies to use forward secrecy for their encryption keys. Forward secrecy, sometimes called ‘perfect forward secrecy,’ is designed to protect previously encrypted communications, even if one of the service providers’ keys is later compromised. Without forward secrecy, an attacker who learns a service provider’s secret key can use it to go back and read previously incomprehensible encrypted communications—perhaps ones that were recorded months or years in the past.