Endpoint

10/18/2018
10:30 AM
Tim Callan
Tim Callan
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Getting Up to Speed with "Always-On SSL"

Websites can avoid the negative consequences of a "not secure" label from Google Chrome 68 by following four AOSSL best practices.

On July 24, Google followed through on its announced plans to mark web pages that did not use HTTPS as "not secure" in Chrome. The Google Chrome 68 "not secure" warning occurs even on pages that don't share or collect any kind of confidential information. The sites labeled "not secure" by the world's most popular browser include those of large brands such as ESPN, Fox News, the NBA, and The Los Angeles Times. The consequences of a "not secure" label can be considerable. Negative trust indicators like this one can stifle use of websites by creating anxiety about their safety. This harmful effect can occur even if it is not a site where transactions take place.

In addition to loss of confidence and decreased transactions, the "not secure" warning can also damage a company's brand. A recent study by research firm DevOps reveals that 97% of active Internet users want to do business with companies that protect their confidential information, and 91% want to do business with companies that invest in best-of-breed security solutions. The presence of an Extended Validation (EV) certificate — or the recognizable "green bar," as it is known — improves consumer perception of a company's stability, level of customer service, and ability to meet its commitments, presumably because they see a clear signal that this company is investing in best-of-breed security solutions to protect its customers. The "not secure" warning has the opposite effect, strongly suggesting that this company is not investing in the best available website security or doing all it can do to protect users. When trust goes away, so does revenue.

Furthermore, distrusted certificates will no longer enable encryption, leaving any shared, sensitive data such as personally identifiable information, credit cards, logins, and personal health information (PHI) exposed to spying and theft.

The solution to Chrome's "not secure" warning is to implement Always-on SSL (AOSSL). AOSSL is the practice of securing all pages on a site with SSL regardless of whether or not they include forms, logins, the ability to make purchases, or the sharing of confidential information. Companies have been perfecting the AOSSL process for the past decade, and today AOSSL can be effective, reliable, easy to implement and maintain, and cost-efficient.

When implementing AOSSL for online properties, these best practices allow for optimal results:

  • Be sure to include EV SSL certificates on your public-facing pages for the highest visitor confidence and maximum transaction rates. In particular, use EV SSL on all pages on which you ask a visitor to purchase, open or login to an account, fill out and submit forms, or share sensitive information.
  • Include a trust seal on your public-facing pages for extra assurance.
  • Apply Domain Validation (DV) certificates on non-public-facing pages for greater cost efficiency without reduction in trust.
  • Use two-year certificates to minimize management overhead and the risk of outage.

Web security has always served two customers. It provides protection not only for the businesses that operate sites but also for the customers, partners, and employees who use them. This second group is critical to the success of any business site, and the level of trust they can maintain goes a long way in determining the success of these sites. All businesses from big to small should make sure they're adopting AOSSL to inspire the greatest confidence possible and keep those revenue numbers going in the right direction.

Related Content:

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Tim Callan has more than 20 years' experience as a strategic marketing and product leader for successful B2B software and SaaS companies. Tim's recent experience includes CMO at SLI Systems (NZX: SLI), VP of Marketing at Verisign (VRSN), CMO at Melbourne IT Digital Brand ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tychotithonus
100%
0%
tychotithonus,
User Rank: Strategist
10/18/2018 | 2:54:45 PM
a counterpoint about EV certs
Great article overall - just one nuance that I'd differ with.

Extended Validation (EV) certificates are probably not needed in most cases. Large-scale UX analysis by the Google team and by researchers have repeatedly demonstrated that users do not notice or care about the additional browser feedback.

https://scotthelme.co.uk/are-ev-certificates-worth-the-paper-theyre-written-on/

https://www.troyhunt.com/extended-validation-certificates-are-dead/
How the US Chooses Which Zero-Day Vulnerabilities to Stockpile
Ricardo Arroyo, Senior Technical Product Manager, Watchguard Technologies,  1/16/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "He just showed up at my doorstep one day without a geotag."
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3906
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 contains hardcoded credentials in the WCF service on port 9003. An authenticated remote attacker can use these credentials to access the badge system database and modify its contents.
CVE-2019-3907
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 stores user credentials and other sensitive information with a known weak encryption method (MD5 hash of a salt and password).
CVE-2019-3908
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 stores backup files as encrypted zip files. The password to the zip is hard-coded and unchangeable. An attacker with access to these backups can decrypt them and obtain sensitive data.
CVE-2019-3909
PUBLISHED: 2019-01-18
Premisys Identicard version 3.1.190 database uses default credentials. Users are unable to change the credentials without vendor intervention.
CVE-2019-3910
PUBLISHED: 2019-01-18
Crestron AM-100 before firmware version 1.6.0.2 contains an authentication bypass in the web interface's return.cgi script. Unauthenticated remote users can use the bypass to access some administrator functionality such as configuring update sources and rebooting the device.