Google Introduces Device Bound Session Credentials in Chrome 146 to Enhance Security

Google has rolled out Device Bound Session Credentials (DBSC) for Chrome 146 on Windows, aiming to combat session theft. This feature ties authentication sessions to specific devices, reducing the risk of unauthorized access.

Google has made Device Bound Session Credentials (DBSC) generally available for all Windows users of its Chrome web browser, following several months of testing in open beta. Currently, this feature is limited to users on Chrome 146, with plans for expansion to macOS in future releases.

Understanding Session Theft

Session theft is a significant security concern, involving the covert extraction of session cookies from web browsers. Attackers can exploit these cookies, which often have long lifespans, to gain unauthorized access to victims’ online accounts without needing their passwords. This typically occurs when users unknowingly download malware designed to steal information, such as Atomic, Lumma, and Vidar Stealer.

How DBSC Works

First announced in April 2024, DBSC aims to mitigate session theft by cryptographically linking authentication sessions to specific devices. This is achieved through hardware-backed security modules like the Trusted Platform Module (TPM) on Windows and the Secure Enclave on macOS. The system generates a unique public/private key pair that cannot be exported from the device. New short-lived session cookies are issued only when Chrome can prove possession of the corresponding private key to the server.

Impact and Future Plans

Google reports a notable decrease in session theft incidents since the introduction of DBSC, indicating the effectiveness of this security measure. The company intends to broaden the availability of DBSC across more devices and enhance its capabilities for better integration within enterprise environments.

Privacy Considerations

Google has emphasized that the DBSC architecture is designed with privacy in mind. The unique key approach prevents websites from using session credentials to track user activity across different sessions or sites. Additionally, the protocol is structured to minimize information exchange, ensuring that it does not leak device identifiers or attestation data beyond the necessary per-session public key.

This article was produced by NeonPulse.today using human and AI-assisted editorial processes, based on publicly available information. Content may be edited for clarity and style.

Avatar photo
NOVA-Δ

A guardian of the digital threshold. NOVA-Δ specializes in breaches, vulnerabilities, surveillance systems, and the shifting politics of online security. Part sentinel, part investigator, she writes with sharp skepticism and a commitment to exposing hidden risks in an increasingly connected world.

Articles: 166