Commit 33443e77 authored by Joseph Rotolo's avatar Joseph Rotolo
Browse files

Updating 4.X - Risk distribution among components

parent 9c582439
Loading
Loading
Loading
Loading
+18 −3
Original line number Diff line number Diff line
@@ -631,11 +631,26 @@ This table maps the user types to the corresponding use cases and the security l

## 4.X Risk distribution among components

> Risk can be transferred between components, for example a network interface can document that secure update of its firmware must be handled by an external program, such as an operating system. In turn, the operating system can offer the security functionality of secure updates to other components in a system.
This section describes the two-way relationship where the VPN product both delegates risks and provides security functionalities to other components in its ecosystem.

> Describe what risks are delegated to other components, as well as what security functionalities this product offers to things integrated with it.
The security of a VPN product is dependent on a chain of trust that spans across multiple components in its operational environment. Consequently, the VPN product delegates certain risks to other components while offering security functionalities that mitigate risks for those same components.

In the scenario that a VPN may include additional components beyond the scope of the present document, the manufacturer is responsible for conducting due diligence as to the security of those components.
### 4.X.1 Risks Delegated to Other Components

The following risks are delegated by the VPN product to other components within its operational environment:

- **Operating System and Runtime Environment** - A VPN product relies on a secure and stable underlying operating system (OS) to function. The risks associated with OS vulnerabilities or a compromised runtime environment are delegated to the OS.
- **Hardware Integrity** - The VPN product depends on the integrity of the physical hardware for the confidentiality of cryptographic keys and data processing. Risks of physical tampering or hardware-based attacks are delegated to the hardware manufacturer.
- **Identity and Authentication** - The VPN product delegates the risks associated with user credential management to a trusted Identity and Access Management (IAM) system. It relies on this external component for secure authentication and authorization of users.

### 4.X.2 Security Functionalities Offered to Integrated Components


The VPN product offers the following security functionalities to other components in its operational environment:

- **Secure Data Transport** - The primary function of a VPN is to create a secure, encrypted tunnel over an untrusted network. This functionality protects all network traffic originating from the client device or network from eavesdropping and other network-based attacks.
- **Controlled Network Access** - The VPN client acts as a security gatekeeper for the remote network. This functionality protects the remote network by only allowing authenticated and authorized traffic to pass through.
- **Threat Visibility and Logging** - The VPN product serves as a sensor for network activity. It offers the security functionality of providing logs and metadata about connection attempts and traffic flow, which can be consumed by other security components like a SIEM or XDR platform to enhance overall threat visibility.

# 5 Requirements specifications