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
 

Recommended Reading:

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.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.
CVE-2020-24343
PUBLISHED: 2020-08-13
Artifex MuJS through 1.0.7 has a use-after-free in jsrun.c because of unconditional marking in jsgc.c.