@@ -168,12 +168,28 @@ Some VPN node shall detect when multiple VPN clients are using credentials that
* Verdict: Notification of both VPN clients or only one connection is active at a time => PASS, otherwise FAIL
* Evidence: Configuration of clients, log messages showing notifications and/or connection status
#### 5.2.X.x **[MI-AUTH-5]** Forced revocation of authorization of endpoints
The VPN service shall provide a method to force revocation, temporary or permanent, of authorization of an endpoint by an authorized user. The revocation of authorization of the VPN client shall end the VPN connection for that client by the time the revocation indicates it has completed.
* Reference: TR-AUTH
* Objective: Protect VPN connection from unauthorized use
* Preparation: None
* Activities: Authorize an endpoint to connect to the VPN, connect it to the VPN, revoke its authorization, then attempt to access the VPN connection from the revoked client
@@ -281,6 +304,14 @@ The VPN provider shall by default not establish routes between different client
* Verdict: Connection not possible or connection fails => PASS, otherwise FAIL
* Evidence: Log messages, packet capture
| Risk factors | Requires mitigations |
|--------------|----------------------|
| all | EISO |
| Security Profile | Requires mitigations |
|------------------|----------------------|
| all | EISO |
### 5.2.X **TR-TRAF**: No traffic through the node unless explicitly approved
The VPN client shall not route traffic through the endpoint from sources/destinations other than the endpoint without the user's explicit informed consent, and such routing shall not be necessary for the use of any unrelated function.
@@ -332,13 +363,13 @@ The VPN client shall not require routing of traffic from sources/destinations ot
#### 5.2.X.x Mapping of mitigations to risk factors and security profiles
@@ -393,9 +424,9 @@ The VPN provider shall not store any PII of the user on remote data processing s
FIXME is this useful? Is there a use case where the VPN client sends PII to the provider but the provider doesn't store the PII? For now, don't include as a mitigation for any use cases.