top of page

Google Aims to Stop Cookie Theft Forever

In the ever-evolving landscape of cybersecurity, browser cookie theft has been a persistent threat, undermining user privacy and security. However, Google is taking significant strides to combat this issue with a groundbreaking feature for the Chrome browser, known as "Device Bound Session Credentials" (DBSC). This initiative represents a proactive step towards enhancing online security and could potentially revolutionize the way we protect our digital identities.

hand taking spice cookie from pan

The Mechanics of DBSC

The DBSC system is ingeniously simple yet effective. It leverages public key cryptography to bind authentication cookies to the user's device. When a user initiates a login session, the browser generates two cryptographic keys: a public key, which is shared with the website, and a private key, which remains securely stored on the user's device. This pairing ensures that even if a cookie were to be stolen, it would be useless without the corresponding private key.


Google's implementation plans to utilize the Trusted Platform Module (TPM) chip found in modern PCs, which is designed to securely store cryptographic keys. This chip not only safeguards the keys but also verifies the integrity of the operating system, providing an additional layer of security.


A Step Towards a Safer Internet

Google's efforts to integrate DBSC into Chrome align with its broader strategy to phase out third-party cookies. By focusing on device-bound credentials, Google aims to significantly reduce the success rate of cookie theft malware. This approach necessitates that attackers must have local access to the device, thereby making detection and cleanup by antivirus software or enterprise management tools more effective.


The DBSC project is being developed transparently on GitHub, with the intention of establishing it as an open web standard. This collaborative approach invites the tech community to contribute and refine the system, ensuring its robustness and adaptability.

Male female couple baking cookies together sugar cookie shapes

Implications for Users and Developers

For users, the introduction of DBSC promises a more secure browsing experience, where their login sessions are protected against remote hijacking attempts. It also complements existing security measures, such as two-factor authentication, by adding a hardware-based verification layer.


Developers, on the other hand, will need to adapt to this new standard. They will have to ensure their websites are compatible with the DBSC system and may need to update their authentication protocols accordingly.


The Road Ahead

Google's initiative is currently in the prototype stage, with a trial run protecting some Google Account users on Chrome Beta. The company anticipates supporting DBSC for approximately half of desktop users, based on current hardware capabilities. The full implementation is expected to be ready by the end of 2024.

oven mitts pulling out muffins kitchen safety

This proactive measure by Google is a testament to the company's commitment to user security and privacy. As cyber threats continue to evolve, it is imperative for tech giants to innovate and implement solutions that stay ahead of malicious actors. The DBSC system is a promising step in that direction, potentially setting a new standard for browser security in the years to come.

Though efforts such as those by Google are important as we fight those who would harm us, a solid security program is how we ensure we have full coverage of risk management for our organizations. Does your organization have a solid security program in place? If you’re not certain, now is an excellent time to contact Webcheck Security for a free discussion of your needs and a tailored quote for assistance from our expert and highly experienced Fractional Information Security Officers (FISOs)—also known as consulting or virtual Chief Information Security Officers (CISOs).

4 views0 comments


bottom of page