U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you're on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Skip to page content

HTTP vs HTTPS: Is it Time For a Change?

The beginning of a secure https URL shown in an web browser's address bar; the s on https and padlock are red.

Data. Security. Privacy.

These are the cornerstones of many discussions concerning technology. The security of citizen information when interacting with the federal government will be increasingly important as we progress into the future.

A few agencies have begun to use Hyper Text Transfer Protocol Secure (HTTPS) in lieu of the standard HTTP. For these agencies, this transition to HTTPS is seen as a step in the right direction and is one way for the government to address the security of citizen information. For others, the transition to HTTPS is seen as something that would require additional maintenance and is unnecessary, especially for websites that do not deal with sensitive or personally identifiable information (PII).

Argument For HTTPS

On one side of the argument, protecting all websites with HTTPS is seen as a necessary step because having security is imperative, despite the additional workload. Joseph Wicentowski, Digital History Advisor in the Bureau of Public Affairs at the Department of State, believes that the use of HTTPS is important for all government websites.

“I would argue that offering HTTPS connections on all pages is particularly important for government sites,” Wicentowski said. “Some may argue that the SSL encryption is only necessary for password-protected portions of websites. But, SSL [provides an extra level of security] and prevents any 3rd party from seeing, recording, or tampering with the content of the user’s session. By offering HTTPS, we allow our security-cognizant users to be 100% confident that no attacker is monitoring or tampering with the contents of their session.”

Another interesting point in the debate is that Google has begun using HTTPS as a ranking signal. In other words, websites that are using the HTTPS protocol are appearing higher on the list of search results.

HTTPS provides a secure, fast and private connection between the user and the website, but there are a few considerations for agencies to ponder before taking the plunge. For some, the full scale implementation of HTTPS is seen as a possible solution for security challenges, but it has a few drawbacks that should be considered when making the decision.

Argument Against HTTPS

On the other end of the argument, there is the belief that not every website needs HTTPS because not every agency deals with the transmission of sensitive information or PII. Some believe that HTTPS is an option, but you must consider things like certificate maintenance before making the decision.

When the question of HTTP vs HTTPS was posed to agencies via the Content Managers Listserv, a few of the responses hinted at the difficulty and extra costs in terms of time and resources that would be needed for an extra level of encryption.

Creative abstract SSL

SSL certificates are files that encrypt the connection from a web server to a web browser. Certificate maintenance requires the installation, configuration and rotation of SSL certificates to ensure that a website’s information is encrypted and up to date. The management of these certificates has high operational costs.

In terms of performance, an additional level of encryption requires more server resources because each visitor must connect to the server in order to exchange the information required to establish a secure connection. Compared to the loading time of a page with HTTP, this process of exchanging information can take a little more time, especially if the server is dealing with multiple visitors at once.

With these extra costs, such as certificate maintenance and a slight decrease in site performance, one must consider if the extra level of encryption is worth implementing.

In this article, we have only began to delve into the debate about the subject of HTTP vs HTTPS. For our next piece on the topic, we will share an agency’s full scale implementation of HTTPS. We will highlight some other issues in this debate, including but not limited to website performance, privacy, security, and hardware.

Do you believe that is it time for a full-scale implementation of HTTPS despite the considerations listed above? Are those considerations just a small cost in the bigger picture of ensuring privacy?

The White House is soliciting feedback from agencies on the topic of a full scale HTTPS implementation until March 31st. Visit the site and share your thoughts!

Tags: , , , ,

GitHub LogoEdit
Top