Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

10/2/2017
12:50 PM
50%
50%

Google Tightens Web Security for 45 TLDs with HSTS

Google broadens HTTPS Strict Transport Security to Top Level Domains under its control and makes them secure by default.

Google is buckling down on Web security by extending HTTP Strict Transport Security (HSTS) to Top Level Domains (TLDs) under its control, the company reports.

HTTPS prevents traffic from being intercepted or misdirected in transit. HSTS automatically enforces HTTPS for connections between clients and Web servers. If someone types http://gmail.com, the browser changes it to https://gmail.com before sending the request.

In doing so, it makes connections more secure and prevents threats like downgrade attacks and cookie hijacking. Google has a HSTS preload list, which is built into all major browsers and contains a list of individual domains, subdomains, and TLDs for which browsers automatically enforce HTTPS connections. It operates 45 TLDs including .google, .how, and .soy.

Back in 2015, Google created the first secure TLD by adding .google to the HSTS preload list. Now it's extending HSTS to more of its TLDs, starting with .foo and .dev, making these websites secure by default without additional work for their users.

"Registrants receive guaranteed protection for themselves and their users simply by choosing a secure TLD for their website and configuring an SSL certificate, without having to add individual domains or subdomains to the HSTS preload list," explained Google Registry's Ban McIlwain in a blog post on the news.

This move will also accelerate the security update process. Normally, there are a few months between the time a domain name is added to the list, and the time browser upgrades reach most users. Using a secure TLD means users are immediately protected.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
angelashirley
50%
50%
angelashirley,
User Rank: Apprentice
11/13/2017 | 2:31:30 AM
Google Tightens Web Security for 45 TLDs with HSTS
Your post is very informative for all google product. Thanks for sharing this kinds of post. In case you need third party technical support then contact Gmail technical support and fix your issues instantly.
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
Architectural Analysis IDs 78 Specific Risks in Machine-Learning Systems
Jai Vijayan, Contributing Writer,  2/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9024
PUBLISHED: 2020-02-17
Iteris Vantage Velocity Field Unit 2.3.1 and 2.4.2 devices have world-writable permissions for the /root/cleardata.pl (executed as root by crond) and /root/loadperl.sh (executed as root at boot time) scripts.
CVE-2020-9025
PUBLISHED: 2020-02-17
Iteris Vantage Velocity Field Unit 2.4.2 devices have multiple stored XSS issues in all parameters of the Start Data Viewer feature of the /cgi-bin/loaddata.py script.
CVE-2020-9026
PUBLISHED: 2020-02-17
ELTEX NTP-RG-1402G 1v10 3.25.3.32 devices allow OS command injection via the PING field of the resource ping.cmd. The NTP-2 device is also affected.
CVE-2020-9027
PUBLISHED: 2020-02-17
ELTEX NTP-RG-1402G 1v10 3.25.3.32 devices allow OS command injection via the TRACE field of the resource ping.cmd. The NTP-2 device is also affected.
CVE-2020-9028
PUBLISHED: 2020-02-17
Symmetricom SyncServer S100 2.90.70.3, S200 1.30, S250 1.25, S300 2.65.0, and S350 2.80.1 devices allow stored XSS via the newUserName parameter on the "User Creation, Deletion and Password Maintenance" screen (when creating a new user).