@@ -161,7 +161,7 @@ The activity of browsing can be defined in the following steps:
## 1.1 Browser
### 1.1.1 Standalone
Standalone browsers are standalone applications that fulfil the functions of browsing.
Standalone browsers are applications that fulfil the functions of browsing.
They are monolithic programs with features that enable their users to undertake the activity of “browsing” as described above. A standalone browser may be used for everyday tasks such as reading email, managing a calendar, or consuming the news.
@@ -198,8 +198,7 @@ The following referenced documents may be useful in implementing an ETSI deliver
For the purposes of the present document, the [following] terms [given in ... and the following] apply:
Browsers: In the context of this category of products, browsers are software products with digital elements that enable end users to access and interact with web content hosted on servers that are
connected to local and remote networks.
Browsers: In the context of this category of products, browsers are software products with digital elements that enable end users to access and interact with web content hosted on servers that are connected to networks such as the Internet.
Embedded Browsers: Embedded browsers are browsers that are intended for integration into another system or application.
@@ -207,6 +206,12 @@ Standalone Browsers: Standalone browsers are standalone applications that fulfil
Likelihood: The probability or frequency of a threat event occurring. This is influenced by various likelihood factors.
Browser Extension:
Progessive Web Application:
Impact: The magnitude of harm if a threat event materialises. This is determined by various impact factors.
Intended purpose: [to be defined]
@@ -244,6 +249,7 @@ The following are considered outside the product boundary but may be security-re
# 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.
