rewindex

ChangesKeeperTrust page

Keeper: Trust page changed

Trust / securityChanged (not classified) (rule)Changed www.keepersecurity.com (opens in new tab)
Summary

Keeper’s Trust page replaced “Keeper Gateway” with “KeeperPAM Gateway” throughout its connection and session-recording descriptions. This is a naming-only update; the diff shows no changes to functionality or security behavior.

Machine-written from the diff below (Sol; type: wording only). Check the diff before relying on it.

What changed

Struck in red is what Keeper removed; blue is what they added. Muted text is unchanged context.

Changed#1
Before: …established between the local vault client through the Keeper Gateway to the target endpoint. The user can…
After: …established between the local vault client through the KeeperPAM Gateway to the target endpoint. The user can…
Changed#2
Before: …is stored inside the relevant Keeper record. The Keeper Gateway communicates with the Keeper Router through outbound-only…
After: …is stored inside the relevant Keeper record. The KeeperPAM Gateway communicates with the Keeper Router through outbound-only…
Changed#3
Before: …the Keeper Router through outbound-only WebSockets . The Keeper Gateway utilizes Keeper Secrets Manager APIs to retrieve…
After: …the Keeper Router through outbound-only WebSockets . The KeeperPAM Gateway utilizes Keeper Secrets Manager APIs to retrieve…
Changed#4
Before: …passes data through the WebRTC connection to the Keeper Gateway that then uses Guacd to connect to…
After: …passes data through the WebRTC connection to the KeeperPAM Gateway that then uses Guacd to connect to…
Changed#5
Before: …is transmitted through the WebRTC connection to the Keeper Gateway and subsequently forwarded to the target endpoint…
After: …is transmitted through the WebRTC connection to the KeeperPAM Gateway and subsequently forwarded to the target endpoint…
Changed#6
Before: …key ("recording key") which is generated on the Keeper Gateway on every session. The recording key is…
After: …key ("recording key") which is generated on the KeeperPAM Gateway on every session. The recording key is…
Changed#7
Before: …Keeper Connection Manager Docker container or through the Keeper Gateway. Using the Connection Manager Docker container method:…
After: …Keeper Connection Manager Docker container or through the KeeperPAM Gateway. Using the Connection Manager Docker container method:…
Changed#8
Before: …browser using the Apache Guacamole protocol. Using the Keeper Gateway with the Keeper Web Vault or Desktop…
After: …browser using the Apache Guacamole protocol. Using the KeeperPAM Gateway with the Keeper Web Vault or Desktop…
Changed#9
Before: …is stored inside the relevant Keeper record. The Keeper Gateway communicates with the Keeper Router through outbound-only…
After: …is stored inside the relevant Keeper record. The KeeperPAM Gateway communicates with the Keeper Router through outbound-only…
Changed#10
Before: …the Keeper Router through outbound-only WebSockets . The Keeper Gateway utilizes Keeper Secrets Manager APIs to retrieve…
After: …the Keeper Router through outbound-only WebSockets . The KeeperPAM Gateway utilizes Keeper Secrets Manager APIs to retrieve…
Changed#11
Before: …passes data through the WebRTC connection to the Keeper Gateway that then uses HTTP or HTTPS to…
After: …passes data through the WebRTC connection to the KeeperPAM Gateway that then uses HTTP or HTTPS to…
Changed#12
Before: …key ("recording key") which is generated on the Keeper Gateway on every session. The recording key is…
After: …key ("recording key") which is generated on the KeeperPAM Gateway on every session. The recording key is…

Compared with the previous archived version (#5262 to #14510). Text is normalized before comparing: dates, counters and tokens show as ‹date›, ‹count›, ‹tok›, and noise-only edits are hidden. Rewindex shows changed passages with a few words of context, not a copy of the page. View the live page (opens in new tab).

Archive proof

Rewindex commits each page capture it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run () commits it.

History of this page

TodayWednesday, November 4Wed, Nov 4

1 page change

Thursday, October 22

1 page change

Cite this

Trust page changed on Keeper’s Trust page, changed 2026-11-04 08:44 UTC (change 2 of 2).

Title
Trust page changed
Vendor
Keeper
Date
URL
https://rewindex.com/change/p14510

All Keeper changesKeeper profileMarkdownJSON