@@ -167,6 +167,37 @@ Passwords are typically associated with user accounts and are a form of secret t
Password managers can be characterized along several dimensions that influence how users interact with them and the benefits they provide. At a high level, these tools address distinct user segments: solutions for individual use, solutions for family groups that require selective sharing while preserving privacy, and basic enterprise configurations in which credentials may be injected into connections dynamically to provide a transparent experience for end users.
```mermaid
---
Title: Password Manager Types
---
flowchart TB
A[Password Manager] --> S1[User Segments]
A --> S2[Synchronization]
A --> S3[Deployment]
subgraph S1
U1[Individual]
U2[Family]
U3[Enterprise]
end
subgraph S2
SY1[Cloud Sync]
SY2[Native Sync]
SY3[Local Only]
end
subgraph S3
D1[Browser]
D2[OS Level]
D3[Standalone]
subgraph M[Mobile]
M1[Native Keychain]
M2[Open Model]
end
end
```
Synchronization is a central point of differentiation. Some solutions synchronize credentials across devices through general-purpose cloud services, enabling access from any device associated with the user’s account. Others provide synchronization that is native to the password manager itself, resulting in a more integrated but potentially narrower ecosystem. A third category comprises non-synchronized deployments that operate as resident or standalone systems, retaining all credentials locally on a single device or within a defined environment.
The deployment model also varies by where the solution resides in the technology stack. Browser-integrated managers provide convenience for web authentication. Operating system level managers offer deeper integration across applications and services. Standalone managers operate as independent applications, typically offering greater flexibility and feature breadth, while requiring separate management by the user. The boundary between browser level and operating system level solutions has become increasingly indistinct as platform integrations have deepened.
@@ -136,6 +141,10 @@ In the present document "**should** ", "**should not** ", "**may** ", "**need no
"**must** " and "**must not** " are **NOT** allowed in ETSI deliverables except when used in direct citation.
\pagenumbering{arabic}
\setcounter{page}{1}
\resetlinenumber
# Executive summary
@@ -167,6 +176,8 @@ Passwords are typically associated with user accounts and are a form of secret t
Password managers can be characterized along several dimensions that influence how users interact with them and the benefits they provide. At a high level, these tools address distinct user segments: solutions for individual use, solutions for family groups that require selective sharing while preserving privacy, and basic enterprise configurations in which credentials may be injected into connections dynamically to provide a transparent experience for end users.
Synchronization is a central point of differentiation. Some solutions synchronize credentials across devices through general-purpose cloud services, enabling access from any device associated with the user’s account. Others provide synchronization that is native to the password manager itself, resulting in a more integrated but potentially narrower ecosystem. A third category comprises non-synchronized deployments that operate as resident or standalone systems, retaining all credentials locally on a single device or within a defined environment.
The deployment model also varies by where the solution resides in the technology stack. Browser-integrated managers provide convenience for web authentication. Operating system level managers offer deeper integration across applications and services. Standalone managers operate as independent applications, typically offering greater flexibility and feature breadth, while requiring separate management by the user. The boundary between browser level and operating system level solutions has become increasingly indistinct as platform integrations have deepened.
