How password managers are built for Privacy and Security
summary
Password vaults encrypt locally with a key derived from a master password that is never sent or stored, enforcing a zero-knowledge architecture so company servers hold only ciphertext. Activity logs are client-side anonymized and timestamps are trimmed to prevent correlation. A cross-functional data privacy committee reviews new telemetry, retention and deletion flows are automated, and external testing runs via HackerOne bug bounty alongside code signing, least-privilege access and hardware protections like secure enclave to reduce supply‑chain and device compromise risk.
AI-written summary · about
chapters (5)
related talks
07mEnhancing Cybersecurity with Enterprise Password Vaults (EPVs) for Financial Institutions...
28mPasswordless zero-knowledge services
30mBehind Closed Doors: Managing Passwords in a Dangerous World
35mSecurity After Death -- Not your problem, or is it?
44mDraining Your Credentials From Popular MacOS Password Managers
26mHow To Keep A Secret
51mIntroduction to Vault
01h 28mData privacy vault 101