Verified Commit a510bb12 authored by Aki Braun's avatar Aki Braun
Browse files

Early sketch: Use cases, Risk factors

parent e9b36840
Loading
Loading
Loading
Loading
+140 −42
Original line number Diff line number Diff line
@@ -146,7 +146,7 @@ In the present document "**shall** ", "**shall not** ", "**should** ", "**should

# Executive summary

The purpose of this document is to provide essential cybersecurity requirements for the design, development, and production of Virtual Private Networks intending to be placed on the European Union market. By demonstrating conformity with the present document's requirements, manufacturers of VPNs benefit from a presumption of conformity with Regulation (EU) 2024/2847 of the European Parliament and of the Council, colloquially known as the Cyber Resiliance Act.
The purpose of this document is to provide essential cybersecurity requirements for the design, development, and production of Virtual Private Networks intending to be placed on the European Union market. By demonstrating conformity with the present document's requirements, manufacturers of VPNs benefit from a presumption of conformity with Regulation (EU) 2024/2847 of the European Parliament and of the Council, colloquially known as the Cyber Resilience Act.

# Introduction

@@ -288,6 +288,10 @@ For the purposes of the present document, the terms given in [TK document from C

'software bill of materials' means a formal record containing details and supply chain relationships of components included in the software elements of a product with digital elements;

'on-premises infrastructure' means the collection of servers, switches, and other hardware used to connect company-owned resources to internal and external networks. Unless specified otherwise, applies to equipment located within a corporate campus, inside of a multi-tenant data centre, inside of a single tenant data centre, or any combination of the three.

'cloud' means a data centre or collection of data centres operated entirely by a third party which rents out space and time on their equipment, as well as providing services for managing infrastructure from outside networks.

## 3.2 Abbreviations

For the purposes of the present document, abbreviations given in [TK document from CEN-CENELEC WG9], [TK document from STF701] and the following apply:
@@ -307,7 +311,7 @@ For the purposes of the present document, abbreviations given in [TK document fr
The types of product with digital elements listed in the section do not fall within the scope of the the Regulation (EU) 2024/2847 (Cyber Resilience Act), and are not covered by this standard:

1. Services, except for the remote data processing solutions for a covered product as defined in CRA recitals 11-12; article 3, 2 <a href="#_ref_i.1">[i.1]</a>;
2. Products specifically designed or procured for national security and defence purpose as defined in CRA recitals 14 and 26; article 2, 7-8 <a href="#_ref_i.1">[i.1]</a>;
2. Products developed or modified for national security and defence purpose, or for processing classified material, as defined in CRA recitals 14 and 26; article 2, 7-8 <a href="#_ref_i.1">[i.1]</a>;
3. Products developed for or used exclusively for internal use by public administration as defined in CRA recital 16; article 5, 2 <a href="#_ref_i.1">[i.1]</a>;
4. Non-commercial free and open source software as defined in CRA recitals 17-21; article 13, 5 <a href="#_ref_i.1">[i.1]</a>;
5. Medical Devices and Software as defined in CRA recital 25; article 2, 2 [a-b] <a href="#_ref_i.1">[i.1]</a>;
@@ -333,11 +337,11 @@ As a holistic product, a Virtual Private Network includes, at minimum, VPN clien

### 4.2.2 Architecture

Virtual Private Networks can differ in topologies used to transmit data and distribute configuration. Two common distinct topologies are hub-and-spoke networks and mesh networks; in practice, networks can use more complex mixed topologies that fall somewhere in between the two extemes.
Virtual Private Networks can differ in topologies used to transmit data and distribute configuration. Two common distinct topologies are hub-and-spoke networks and mesh networks; in practice, networks can use more complex mixed topologies that fall somewhere in between the two extremes.

In a hub-and-spoke network, multiple clients connect to a single VPN server/gateway, which provides both management and routing capabilities to the clients.

![A diagram illustrating a hub-and-spone network.](./media/hubspoke.drawio.png)
![A diagram illustrating a hub-and-spoke network.](./media/hubspoke.drawio.png)

In a mesh network, clients and gateways establish direct tunnels between each other. A management server is used to authenticate VPN clients and gateways, and to configure them.

@@ -361,7 +365,7 @@ Management server provides a way for network administrators to control configura
* Access control: policies that permit or deny certain traffic within the network.
* Monitoring and logging: configuration logs, network logs, telemetry used for troubleshooting.

Management server typically mantains configuration of the whole network, and provides configuration to individual clients as they connect (authentication, address assignment, routes, etc).
Management server typically maintains configuration of the whole network, and provides configuration to individual clients as they connect (authentication, address assignment, routes, etc).

In VPNs using a hub-and-spoke topology, management server is often implemented as part of the VPN server.

@@ -375,61 +379,155 @@ In VPNs using a hub-and-spoke topology, management server is often implemented a

This list of use cases is an informative resource to the manufacturer to simplify choosing a set of security requirements. Each use case is mapped to a security level, which is a collection of risks and the security requirements necessary to mitigate them.

### 4.4.2 VPN software intended for enterprise workforce deployment
XXX VPN client software

XXX VPN server software
            ——
          / | XXXX enterprise hardware
 risk    /  | XXXX enterprise-controlled cloud
transfer \  | XXXX manufacturer hardware
          \ | XXXX manufacturer cloud
            ——
XXX VPN management

### 4.X.X VPN clients

All VPN clients carry with them the inherent risk of being the entry point to a private network.

* **UC-UR-1** Small business staff accessing office resources from off-site
  * connections likely brief, task-driven
  * endpoint hardware is unmanaged

* **UC-US-2** Students accessing university resources off-campus
  * connections likely brief, task-driven
  * endpoint hardware is unmanaged

* **UC-US-3** Enterprise remote workforce - managed
  * connecting for most or all of their workday
  * endpoint hardware is managed by MDM
  
* **UC-US-3** Enterprise remote workforce - BYOD
  * connecting for most or all of their workday
  * endpoint hardware is unmanaged

* **UC-UR-4** Software for mesh VPN node
  * always-on connection for maximum benefit

### 4.X.X Mesh VPN node

Control plane in mesh VPNs: typically managed by vendor/manufacturer?

* **UC-ME-1** TK TODO

### 4.X.X Managing distributed workforces

#### 4.X.X.1 VPN server and gateway installed on enterprise-managed infra

* **UC-OP-1** VPN management deployed on-premises
  * Installed and set up by enterprise network admins or IT
  * Network access and permissions managed by enterprise IT
  * Installed on equipment physically accessible by network administration
    * HQ, multi-tenant data centre, or single-tenant data centre
  * Positioned on the private network side of firewall

* **UC-OP-2** VPN deployed fully or in-part to "cloud" infrastructure
  * Installed and set up by enterprise network admins or IT
  * Network access and permissions managed by enterprise IT
  * Access controls managed without physical access to network

- [TK-A-1] VPN server
  - Professionally administration by enterprise IT
  - Authenticated access is limited to approved roles
  - Physical access is usually limited by data center access
  - May include on-prem hardware, software intended for on-prem hardware, or cloud services
#### 4.X.X.2 VPN server and gateway as a service (manufacturer infra)

- [TK-A-2] VPN gateway, VPN concentrator
  - Enables site-to-site VPN, combining two or more disparate physical networks as one
  - Deployed to high traffic, high complexity environments
  - Offers an advanced version of VPN server functionality, with more effective scaling
  - May be put on the market on its own dedicated hardware (concentrator)
* **UC-CL-1** VPN-as-a-service
  * TK TODO

- [TK-A-3] VPN Client
  - Software deployed to endpoints
  - Endpoints are typically managed devices
  - Software is typically preconfigured, providing limited opportunity for end user error in configuration
  - Carries significant risk due to its entrypoint into a private network
### 4.X.X Connecting data centres

### 4.4.3 VPN software connecting data centres
* **UC-DC-2** Always-on data centre VPN
  * Used to securely connect on-premises equipment with cloud data centres
  * Managed by IT or software operations
  * Provides backup and disaster recovery, cloud bursting, and centralised identity management
  * Common in hybrid cloud setups
  * Used for ongoing activities, such as real-time data synchronisation, identity federation, or persistent application connectivity.

- [TK-B-1] Site-to-site VPN
  - Professionally administration by software developers or operations
  - Deployed to cloud data centres or on-prem data centres
  - Prioritises high throughput
* **UC-DC-1** On-demand data centre VPN
  * Used to securely connect on-premises equipment with cloud data centres
  * Managed by IT or software operations
  * Provides backup and disaster recovery, cloud bursting, and centralised identity management
  * Activated for discrete tasks, for example, during backup operations, scheduled data transfers, or specific maintenance windows.

### 4.4.4 VPN software intended for high-security enterprise
### 4.X.X IoT VPNs

- Financial institutions? Healthcare?
- TODO Graham Wallace
* **UC-IT-1** IoT-Specific VPNs
  * TK TODO

### 4.X.X Networks with higher security needs

* **UC-HR-1** Hospitals, healthcare
  * TK TODO

* **UC-HR-2** Financial institutions
  * TK TODO

## 4.5 Risk factors

### 4.5.1 List of risk factors

XXX client risks

BYOD policies

XXX mesh untrusted device risks

XXX management risks

XXX access risks

XXX target risks

====

USERS

XXX end users
XXX administrators
XXX operations

The risk factors identified by the risk assessment in Annex C are grouped into risk categories and assigned unique identifiers below.

* Users with private network access
  * **[USR-L-0]** Restricted to few users with strong cybersecurity background
  * **[USR-L-1]** Restricted to devices fully managed by enterprise MDM
  * **[USR-L-2]** User-controlled hardware with a fully preconfigured VPN client
  * **[USR-L-3]** User-controlled hardware with user-selected VPN client
  * **USR-L-0** Restricted to limited users with managed devices and strong cybersecurity background
  * **USR-L-1** Restricted to devices fully managed by enterprise MDM
  * **USR-L-2** Accessible by user-controlled hardware with a fully preconfigured VPN client
  * **USR-L-3** Accessible by user-controlled hardware with user-selected VPN client

* Client configuration
  * **CFG-L-0** Client is fully preconfigured by enterprise IT, remote endpoints and public keys updated by MDM 
  * **CFG-L-1** Client has limited user configuration options, such as choosing a region to connect to 
  * **CFG-L-2** End user is provided clear configuration instructions and client software is supplied directly by manufacturer or MDM
  * **CFG-L-3** End user is provided configuration information for any protocol-appropriate client

* Client authorisation
  * **AUT-L-0** Client requires multi-factor authentication
  * **AUT-L-1** Restricted to devices fully managed by enterprise MDM
  * **AUT-L-2** Accessible by user-controlled hardware with a fully preconfigured VPN client
  * **AUT-L-3** Accessible by user-controlled hardware with user-selected VPN client

* Users with administrative access
  * **[ADM-L-0]** Restricted to limited IT professionals with a physical presence on the private network
  * **[ADM-L-N]** TK a description of a scenario where the VPN is entirely cloud-based so admin _cannot_ have a physical presence
  * **[ADM-L-N]** Administrators can access VPN management portal via the VPN
  * **ADM-L-0** Restricted to limited IT professionals with a physical presence on the private network
  * **ADM-L-N** TK a description of a scenario where the VPN is entirely cloud-based so admin _cannot_ have a physical presence
  * **ADM-L-N** Administrators can access VPN management portal via the VPN

* Physical access to data processing
  * **[PHY-L-N]**
  * **[PHY-L-N]**
  * **[PHY-L-N]**
  * **PHY-L-N**
  * **PHY-L-N**
  * **PHY-L-N**

### 4.5.1 Mapping of use cases to risk factors and security levels

| Use case | USR | CFG | AUT | ADM | Sec Lev |
|----------|-----|-----|-----|-----|---------|
| UC-TK-1  | L-0 | L-0 | L-1 | L-0 | SC-TK-1 |

### 4.5.1 Mapping of use cases to risk factors and security levels

## 4.6 Security levels

@@ -482,10 +580,10 @@ VPNs can be expected to operate in a network environment alongside other Importa

This section describes the different classes of users for VPN products, differentiating them by their security expertise, goals, and the threats they are most likely to face.

#### 4.8.1.2 Consumers
#### 4.8.1.2 University student

**USER-1**
: This user type is characterized as having low security expertise and utilizes VPN products for personal purposes on personal devices. Their expectation is for a simple, pre-configured product that requires minimal user intervention.
: This user type is not expected to have high security expertise and utilizes VPN products for accessing university resources while away from campus. Their expectation is for a simple, pre-configured product that requires minimal user intervention.

#### 4.8.1.3 Enterprise IT / Administrators