Device Bound Session Credentials
A device held key that stops stolen session cookies from working on another computer.
In one line
Can tie your sign in to this device so copied cookies stop working elsewhere
A device held key that stops stolen session cookies from working on another computer.
The site gets short lived cookies refreshed with a signature from a key kept in the TPM or secure hardware. Reveals that the session is tied to one device. Chrome 146 on Windows (Apr 2026); GA for Google Workspace on May 25 2026.
What it can and can't do
What the user does: Nothing. It happens when you sign in on a site that uses it.
It can
- Create a key that stays on your device when you sign in
- Check regularly that the session comes from your device
- Refresh short lived cookies, while your device keeps proving itself
- Cut off a session copied to another computer
It cannot
- Stop someone using your device while you are signed in
- Move the key to another device
- Work in Firefox or Safari
How it differs between platforms: Chrome and Edge on computers only. Firefox, Safari and phones do not support it.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 146 | 2026-03-10 | :Windows first, macOS later (verify) |
| Edge | Supported | 146 | 2026-03-13 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Not supported | Not available | Not listed | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | Secure-Session-Registration and Secure-Session-Response headers; bound session cookie |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Cookie lifetime in minutes, refreshed by key proof until session ends |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Cookie refresh signature
Shape: none
How often: every few minutes
No individual data fields. The signal is the access itself.
Technical limits
- Needs hardware key support (TPM on Windows)
- Chrome only so far, macOS later (verify version)
- Short lived cookie must refresh often
The story
What it is
A device held key that stops stolen login cookies from working on another computer.
For you
You see nothing. In the background your device proves it is the same one that signed in. If malware steals your cookie, it will not work elsewhere.
For makers
It fights account takeover by cookie theft, a growing problem for banks, email and work tools. Makers keep users safer with no extra steps. It also ties a session to a specific device.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | Malware steals your email session cookie, but the attacker cannot use it on their own computer. | None named |
| banking | A bank keeps your session tied to your laptop so a stolen cookie cannot move money. | None named |
| social | A social site stops account takeovers where hackers reuse stolen sessions. | None named |
| enterprise | A company ties staff sessions to company laptops so stolen sessions are useless. | None named |
| games | A game store account protects your items and wallet from hijacked sessions. | None named |
| payments | A payment site keeps the session tied to your device to block fraud. | None named |
| ads | An ad account dashboard stays safe, since stolen sessions are a common way to hijack ad budgets. | None named |
Risks
- Ties session to device
- Chrome only for now
What the platform says
- Chrome: Device Bound Session Credentials. Chrome pitches it as protection that ties a login session to your device, so stolen cookies are useless.
Good uses and abuse
Legitimate uses
- Defence against cookie theft malware
Known abuse
- Device pinning of sessions
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2024-04, Chrome 126: Origin trial begins
- 2026-04, Chrome 146: Shipped on Windows
- 2026-05, all: May 25 2026 GA for Google Workspace
Related capabilities
Related
- Session cookies and tokens. Can keep you signed in between pages with a small ID stored in your browser
Sources
How well checked: Based on official documentation.