Filter Blogs expand_more
Blog add
Authors add
Markets add
Solutions add
Products add
Product Categories add
21 Results for 'HTTP'
Blog

By Bruce Morton

April 09, 2015

The approval of HTTP/2 by the Internet Engineering Steering Group (IESG) back in mid-February 2015 marked the next major version of the network protocol used by the web. This blog covers how HTTP/2 will affect Internet security.
Blog

By Bruce Morton

March 09, 2018

In Chrome 68, which will be released in July 2018, we can expect "Not secure" to be provided for all HTTP pages.
Blog

By Stephen Demone

October 18, 2016

The concept of HTTPS and SSL/TLS certificates has gone mainstream, with thousands of times more SSL/TLS certificates on the Internet today than in 1996 leading to the development of new Free SSL companies that offer unpaid SSL/TLS certificates over the past two years. How will this change the Internet as we know it today? 
Blog

By Bruce Morton

May 01, 2011

Throughout this blog I appear to use (or misuse) the terms SSL, TLS and HTTPS interchangeably. From time to time I catch myself and say, “Which one should I be using?” Frankly, my default is to use SSL. When I reference an article or site, I do tend to side with the term it prefers. So what’s the difference?
Blog

By Bruce Morton

July 26, 2016

Emerging vulnerabilities underscore the argument for creating a safer Internet for everyone including domain owners by using HTTPS Everywhere, as called for by Google in 2014. The HTTPoxy vulnerability sends us yet another signal to use HTTPS Everywhere, including internal sites.
Blog

By Diana Gruhn

May 22, 2018

These are the three things marketers need to know as Chrome 68 closes in.            
Blog

By Diana Gruhn

February 27, 2018

The Point of No Return for HTTPS Arrives in the Google Chrome 68 Release Expected in July 2018.
Blog

By Bruce Morton

September 08, 2015

In June 2015, the US chief information security officer (CIO) issued a memorandum to mandate HTTPS-only to secure Federal websites and web services. This policy is also known as Always-On SSL and HTTPS everywhere. The majority of Federal websites use HTTP; however the CIO states that HTTP is susceptible to interception, manipulation and impersonation. This vulnerability can be mitigated by implementing an HTTPS-only policy which must be implemented to all existing sites and services by December 31, 2016. 
Blog

By Entrust Datacard

January 21, 2013

In 2011, Google added public key pinning to Chrome. They white-listed the certification authority public keys that could be used to secure Google domains.
Blog

By Bruce Morton

August 24, 2016

At Black Hat USA 2016, doctoral candidates Mathy Vanhoef and Tom Van Goethem presented HEIST, an SSL/TLS vulnerability. HEIST is short for “HTTP Encrypted Information can be Stolen through TCP-windows.”
Page 1 of 3