Merge branch 'denjell-working-tree' into 'main'

# Dependencies

node_modules/

npm-debug.log*

yarn-debug.log*

yarn-error.log*

pnpm-debug.log*

lerna-debug.log*

mermaid-filter.err 

# Build outputs

dist/

dist-ssr/

build/

out/

*.local

# Environment files

.env

.env.local

.env.*.local

.env.development

.env.test

.env.production

# IDE files

.vscode/*

!.vscode/extensions.json

!.vscode/settings.json

.idea/

*.swp

*.swo

*~

# macOS

.DS_Store

.AppleDouble

.LSOverride

Icon

._*

.DocumentRevisions-V100

.fseventsd

.Spotlight-V100

.TemporaryItems

.Trashes

.VolumeIcon.icns

.com.apple.timemachine.donotpresent

.AppleDB

.AppleDesktop

Network Trash Folder

Temporary Items

.apdisk

# Logs

logs/

*.log

npm-debug.log*

yarn-debug.log*

yarn-error.log*

pnpm-debug.log*

# Testing

coverage/

.nyc_output/

*.lcov

.cache/

# TypeScript

*.tsbuildinfo

.tsc-cache/

# Package managers

.npm

.yarn/

.pnp.*

# Misc

*.pid

*.seed

*.pid.lock

.eslintcache

.stylelintcache

*.tgz

# Temporary files

*.tmp

*.temp

*.bak

# Lock files (uncomment if you don't want to commit them)

# package-lock.json

# yarn.lock

# pnpm-lock.yaml

 No newline at end of file

<div align="center">

ETSI EN 304-618 V0.0.1 (2025-08)

</div>

![~~CAPTION~~](media/etsi-coverpage-logo.png)

HARMONISED EUROPEAN STANDARD  

<div align="center">

CYBER; CRA; <br />

Essential cybersecurity requirements for password managers 

</div>

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<div align="center">

Reference<br />

&lt;Workitem><br />

Keywords<br />

&lt;keywords><br />

ETSI<br />

650 Route des Lucioles<br />

F-06921 Sophia Antipolis Cedex - FRANCE<br />

Tel.: +33 4 92 94 42 00   Fax: +33 4 93 65 47 16<br />

Siret N° 348 623 562 00017 - APE 7112B<br />

Association à but non lucratif enregistrée à la<br />

Sous-préfecture de Grasse (06) N° w061004871<br />

</div>

<br />

<div align="center">

**_Important notice_**

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format on [ETSI deliver](ETSI deliver) repository.

Users should be aware that the present document may be revised or have its status changed, this information is available in the [Milestones listing](Milestones listing).

If you find errors in the present document, please send your comments to<br />the relevant service listed under [Committee Support Staff](Committee Support Staff).

If you find a security vulnerability in the present document, please report it through our

[Coordinated Vulnerability Disclosure (CVD)](Coordinated Vulnerability Disclosure (CVD)) program.

<br />

**_Notice of disclaimer & limitation of liability_**

The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of experience to understand and interpret its content in accordance with generally accepted engineering or

other professional standard and applicable regulations.

No recommendation as to products and services or vendors is made or should be implied.

No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness for any particular purpose or against infringement of intellectual property rights.

In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use of or inability to use the software.

<br />

**_Copyright Notification_**

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI yyyy.

All rights reserved.<br />

</div>

# Contents

<br />

# Intellectual Property Rights

Essential patents

IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations pertaining to these essential IPRs, if any, are publicly available for **ETSI members and non-members** , and can be found in ETSI SR 000 314: _"Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards"_ , which is available from the ETSI Secretariat. Latest updates are available on the [ETSI IPR online database](https://ipr.etsi.org/).

Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Trademarks

The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.

**DECT™**, **PLUGTESTS™**, **UMTS™** and the ETSI logo are trademarks of ETSI registered for the benefit of its Members. **3GPP™**, **LTE™** and **5G™** logo are trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. **oneM2M™** logo is a trademark of ETSI registered for the benefit of its Members and of the oneM2M Partners. **GSM®** and the GSM logo are trademarks registered and owned by the GSM Association.

# Foreword

This Group Report (GR) has been produced by ETSI Industry Specification Group <long ISGname> (<short ISGname>).

# Modal verbs terminology

In the present document "**should** ", "**should not** ", "**may** ", "**need not** ", "**will** ", "**will not** ", "**can** " and "**cannot** " are to be interpreted as described in clause 3.2 of the [ETSI Drafting Rules](https://portal.etsi.org/Services/editHelp/How-to-start/ETSI-Drafting-Rules) (Verbal forms for the expression of provisions).

"**must** " and "**must not** " are **NOT** allowed in ETSI deliverables except when used in direct citation.

# Executive summary

# Introduction

This European harmonised standard defines cybersecurity requirements applicable to password managers.

This document will provide security requirements and assessment criteria covering all elements defined in CRA Annex I Part 1 and Part 2 for password managers for ICT common use, as mentioned in CRA Annex III Class I important products.

This work item intends to produce an EN as candidate for harmonisation, under the standardisation request in support of the implementation of the CRA (M/606).

<br />

# 1 Scope

This standard focuses on password managers. These are designed to securely store and retrieve passwords, locally on a device or on a remote server, with a view to facilitate password management. 

## 1.1	Password managers 

Password managers can be built on top of secret managers and function as a comprehensive management service. 

When a password manager includes password rotation it transcends being just a storage tool and becomes an active service that proactively manages credentials over time, this makes it a management service rather than simply a storage tool. 

## 1.2	What is a password 

Passwords are typically associated with user accounts and are a form of secret that users know and use to authenticate themselves to a system. They play a role in secure authentication and access control and verify a user's identity or authorisation to access a system or resource. They are integrated into applications, systems and services to verify user identity during login processes. The activity of using a password is the entering of this secret information at authentication points to gain authorised access to protected information. 

## 1.3 Use cases

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.

On mobile platforms, this integration manifests differently across ecosystems. Some provide a native keychain-style service with cloud-backed synchronization, delivering a uniform experience across devices within that ecosystem. Others adopt a more open model in which the password management provider may be selected from multiple services through system APIs or plugins, increasing choice but potentially creating ambiguity about which component is responsible for managing credentials.

These distinctions reflect the evolution of password management from a basic browser convenience to a mature security capability. Each approach entails specific tradeoffs among convenience, security, and flexibility. For the purposes of scope, this document considers solutions across these user segments, synchronization models, and deployment models, with particular attention to the interactions and overlaps among them.

# 2 References

## 2.1 Normative references

Normative references are not applicable in the present document.

## 2.2 Informative references

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

> NOTE:    While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity.

The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding but are not required for conformance to the present document.

- <a name="_ref_i.1">[i.1]</a>

# 3 Definition of terms, symbols and abbreviations

## 3.1 Terms

For the purposes of the present document, the [following] terms [given in ... and the following] apply:

## 3.2 Symbols

For the purposes of the present document, the [following] symbols [given in ... and the following] apply:

Password managers: products with digital elements designed to store passwords, locally on a device or on a remote server, with a view to facilitate password management, including activities such as generation of passwords as well as password sharing and integration with local or third-party applications for usage of passwords. This category includes but is not limited to local password managers, browser-based password managers, enterprise password managers as well as hardware-based password managers.

Likelihood: The probability or frequency of a threat event occurring. This is influenced by various likelihood factors.

Impact: The magnitude of harm if a threat event materialises. This is determined by various impact factors.

Intended purpose: [to be defined]

Operational environment/categories of users: [to be defined]

Reasonably foreseeable use: [to be defined]

## 3.3 Abbreviations

For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:

LPM: Local Password Managers

BBPM: Browser-Based Password Managers

EPM: Enterprise Password Managers

HBP: Hardware-Based Password Managers

TPM: Trusted Platform Module

API: Application Programming Interface

# 4	Compliant Products

## 4.1	Password Manager

A password manager is a product with digital elements designed to store passwords, locally on a device or on a remote server, with a view to facilitate password management, including activities such as generation of passwords as well as password sharing and integration with local or third-party applications for usage of passwords.

### 4.1.1	In-Scope components

The following components are within the product boundary of the standard:

- [to be defined]

- Standalone apps, OTP service, local storage, team management, CI/CD secrets, browser extension

- Service, application, product

- Other identity provider services

### 4.1.2	Out-of-scope components

The following are considered outside the product boundary but may be security-relevant environmental components:

- [to be defined]

- Secure element in and of itself is not a password manager

- Secrets, API keys, Passwords relate to the authentication of a user with a “password”

    - Keys are NOT passwords, but they can help us understand. 

- Generating one-time-passwords (just a token, valid only once, two-factor) is different as opposed to static password

# 5 Representative Use Cases

## 5.1 Purpose and Rationale

In accordance with the proportionality principle mandated by the CRA, this clause defines representative use cases for password managers. These use cases illustrate typical deployment contexts that influence the selection and applicability of security requirements.

Each use case is associated with a general risk level, derived directly from the application of the risk assessment methodology detailed in Annex A. This risk management level serves as a foundational element for determining the stringency of security requirements. While these use cases are representative, specific deployment scenarios will necessitate a more granular and detailed risk assessment, also guided by Annex A.

## 5.2 Use Cases for Password Managers

UC-PM1: Passwords managers on edge device for isolated, non-critical functions

- Description: 

- Example environments: 

- Risk level: (see Annex ??)

UC-PM2: Enterprise private cloud password managers

- Description: 

- Example environments: 

- Risk level: (see Annex ??)

UC-PM3: Cloud password managers in multi-tenant IaaS

- Description: 

- Example environments: 

- Risk level: (see Annex ??)

UC-PM4: Operating system “keychain” type managers

- Description: 

- Example environments: 

- Risk level: (see Annex ??)

<br />

# Annex A: <br>Title of annex

<br />

# Annex B: <br>Title of annex

## B.1 First clause of the annex

## B.1.1 First subdivided clause of the annex

<br />

# Annex: Bibliography

<br />

# Annex : Change history

| Date       | Version | Information about changes |

|------------|---------|---------------------------|

|&lt;Month year>|   <#>   | &lt;Changes made are listed in this cell> |

|            |         |                           |

|            |         |                           |

|            |         |                           |

<br />

# History

| Version      | Date         | Milestone      |

|--------------|--------------|---------------|

| <Month year> | <#>          | <Changes made>|

|              |              |               |

|              |              |               |