The .gov in government websites carries a lot of weight. Citizens expect government websites to be secure, trustworthy, and reliable. Citizens expect anything they read on a .gov website to be official, and they expect any information they submit to that website — especially if they’re submitting personal information — to be sent safely and only to the government.

On today’s Internet, in today’s web browsers, HTTPS (https://) offers the strongest guarantee of reliable information and secure transmission.

That’s why 18F’s policy is to use HTTPS for every .gov website we make. 18F is an in-house government technology team that builds things for the rest of the U.S. federal government, and we’re committed to deploying HTTPS across all of our released websites.

HTTPS URL on desktop

Deciding to use HTTPS everywhere was not difficult. Strong encryption benefits our visitors and our government partners by providing:

  • A secure connection. HTTPS guarantees that visitors are connecting to the official website, and not getting a page that’s been tampered with — or replaced entirely — by someone else. This protects users from being hijacked or having their information stolen, and protects our government partners from being impersonated or used as a vehicle for attack.
  • A private connection. Internet traffic is easily intercepted and easily correlated — there is no such thing as insensitive browsing data. By using HTTPS, a visitor’s browsing activity is kept private. Web pages, URLs, cookies, and HTTP headers are all encrypted.
  • A fast connection. Encryption allows us to use modern protocols like SPDY, an extension to HTTPS that greatly speeds up website loading. SPDY is widely supported by modern browsers, and used today by Twitter, Google, and Facebook. SPDY requires encryption, and is the basis for the upcoming HTTP/2, which will require encryption to support visitors on modern browsers.

Finally, using HTTPS lets us adhere to search engine best practices, as Google’s search algorithms now prefer encrypted websites.

These properties are useful for all of our applications, all of the time — not just when passwords or personal information are involved. By simply deploying HTTPS all of the time, we don’t have to engineer a boundary around “sensitive” parts of the application, or judge where those lines should be drawn.

Our friends across the pond in the Government Digital Service have come to the same conclusion, and require HTTPS in their digital standards for the UK government.

As we build web APIs that we want the public to rely on, secure connections are becoming even more vital. 18F’s API standards recognize this by requiring the use of encryption.

HTTPS has never been faster

The most common concern people raise about HTTPS is performance. Encryption requires computation, and can make some kinds of caching more difficult. Fortunately, in the last several years, there has been tremendous investment in HTTPS by the private sector.

Google has been engineering and publishing major speed improvements to OpenSSL’s encryption and privacy for years, and their work on SPDY allows websites to achieve serious speed improvements over plain HTTP.

As major technology firms like Facebook and Twitter invest in universal encryption, their engineering and best practices have improved the ecosystem for everyone.

In 2014, the biggest performance priority for HTTPS is to just get it deployed more widely so that these optimizations can continue.

Integrating HTTPS into our workflow

A more serious concern with HTTPS is operational: managing certificates, working out the right configuration, and generally not screwing it up. The financial cost of purchasing certificates is small — the maintenance cost of installing, configuring, and rotating them is not. This is arguably the biggest issue with deploying HTTPS today, and contributes to the web’s overall slow and inflexible security response.

Like everything else, managing the mechanics of HTTPS becomes far easier when you commit to it and operationalize it.

We’ve still got a lot to do on this front, but we’re starting out by:

  • Openly documenting our standard HTTPS practices. This forces us to be more thoughtful and rigorous, and we hope it will yield valuable public feedback.
  • Baking a strong nginx configuration into the baseline that 18F uses to create each of our production servers, so that our individual developers don’t have to become HTTPS experts.
  • Keeping up with the web security community as it makes advances in encryption, protocols, and certificate management that can make our lives easier and our applications more secure.

As we grow, we’ll be writing about the tools we use — and open sourcing the tools we make — along the way.

Moving forward

The web’s future is encrypted connections, for all the right reasons. The more people and institutions that push encryption forward, the simpler and faster it will become for everyone. 18F is joining that process.

You’ll soon hear more about our technical practices, and what we’re doing to move the ball forward on web security inside the federal government.