O3.09.2Password-manager concentration tradeoffdesignresearch

Password managers reduce memory burden but introduce concentration risk

Aliases: password vault risk · manager single point · password vault tradeoff

What it is

The password-manager concentration tradeoff places many independent random secrets in one vault, greatly reducing memory and reuse while concentrating availability and confidentiality in the master authentication, unlocked devices, sync account, and recovery. Concentration is not automatically insecurity; it changes failure modes and protective priorities.

Why it happens

A manager generates different passwords and fills by domain, reducing typing and relay to fake sites. Vault compromise, master-credential phishing, sync takeover, or lost recovery material can affect many accounts, while service outage can create broad lockout. Strong local encryption, device binding, MFA, export backup, and rehearsed recovery mitigate different risks with convenience tradeoffs.

Studying it

Have participants complete setup, cross-device login, wrong-domain recognition, device loss, offline access, recovery, and provider migration. Measure unique-password use, misfill, recovery success, lockout time, and threat understanding. Security assessment must inspect vault encryption, key derivation, sync, and recovery; manager use alone does not prove every account secure.

Where it stops holding

Browser, operating-system, enterprise, and independent managers have different trust boundaries, and cloud sync is not mandatory. Passwordless credentials may still concentrate in a credential manager. A written offline backup can fit some users. Compare whole-system alternatives instead of returning to broad reuse merely because a single point exists.

Applying it

  • Support standard autofill and generation; do not break managers with unusual fields, paste bans, or unnecessary reauthentication.
  • Protect the vault with strong primary authentication, device inventory, anomaly notice, and rehearsed recovery, explaining sync boundaries.
  • Support encrypted export or portable backup and state what happens if all devices and recovery material are lost.
  • Emphasize the target registered domain during fill and prevent pages from reading other-site entries; test fake domains, frames, and overlays.

Related

  • Same group: O3.09.1 Password-reuse pressure · O3.09.4 Allowing paste
  • Adjacent: O3.02.2 Recovery-path security floor · O3.07 Device loss
  • Search terms: password manager threat model · password vault recovery · credential autofill

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/O3.09.2