Sunday, December 29, 2024
HomeTechnologyGoogle switches to own Root Certificate Authority “Google Trust Services”

Google switches to own Root Certificate Authority “Google Trust Services”

Published on

SIEM as a Service

Google is switching to its own Root Certificate Authority for issuing its own TLS/SSL certificates for securing its web traffic via HTTPS, and not rely on intermediaries, as it was so for.

In the past years, Google has used certificates issued by several companies, with the lastly supplied by GlobalSign and GeoTrust.

Currently, Google is operating a subordinate Certificate Authority (Google Internet Authority G2 – GIAG2), which manages and deploys certificates to Google’s infrastructure.

- Advertisement - SIEM as a Service

Google is currently in the process of migrating all services and products from GIAG2 certificates to the new Root Certificate Authority, named Google Trust Services (GTS).

The search giant said, the migration to GTS will take time, and users will see mixed certificates from both GIAG2 and GTS until then.

What this means for regular users is that when they’ll click to view a site’s HTTPS security certificate, it will say “Google Trust Services” instead of Google Internet Authority, GeoTrust, GlobalSign, or any other term. This will make it easier to identify authentic Google services.

Likewise, you can read Encrypt and password protect your Gmail message in a click

For Google, GTS means its engineers will have full control over its HTTPS certificates since the time they’re issued to the time they’re revoked.

Situations, when another Certificate Authority issues SSL certificates for Google domains, will stand out immediately.

GTS will provide HTTPS certificates for a broad range of services, such as public websites to API servers, for all Alphabet companies, not just Google.

More technical information, such as Google’s current active root certificates and their https://pki.goog/SHA1 fingerprints are available on the Google Trust Services homepage.

Google Trust Services now operates the following Root Certificates:

 Public KeyFingerprint (SHA1)Valid Until
GTS Root R1RSA 4096, SHA-384e1:c9:50:e6:ef:22:f8:4c:56:45:
72:8b:92:20:60:d7:d 5:a7:a3:e8
Jun 22, 2036
GTS Root R2RSA 4096, SHA-384d2:73:96:2a:2a:5e:39:9f:73:3f:
e1:c7:1e:64:3f:03:38:34:fc:4d
Jun 22, 2036
GTS Root R3ECC 3M, SHA-38430:d4:24:6f:07:ff:db:91:89:8a:
0b:e9:49:66:11:eb:8c:5e:46:e5
Jun 22, 2036
GTS Root R4ECC 384, SHA-3842a:1d:60:27:d9:4a:b1:0a:1c:4d:
91:5c:cd:33:a0:cb:3e:2d:54:cb
Jun 22, 2036
GTS Root R2RSA 2048, SHA-175:e0:ab:b6:13:85:12:27:1c:
04:f8:5f:dd:de:38:e4:b7:24:2e:fe
Dec 15, 2021
GTS Root R4ECC 256, SHA-25669:69:56:2e:40:80:f4:24:a1:
e7:19:9f:14:ba:f3:ee:58:ab:6a:bb
Jan 19, 2038
Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

The Rise of AI-Generated Professional Headshots

It’s clear that a person’s reputation is increasingly influenced by their online presence, which...

Ethical Options to Monetize Apps for Privacy-Conscious Users

Users continue to raise their expectations for online services and applications, and app monetization—how...

How UZIO Enhances Payroll Processing and Compliance Management

In the present-day business landscape, today's companies are always looking for ways to make...