@@ -101,7 +101,23 @@ Guidance: This is a "fail-closed" requirement - if something goes with the VPN c
* Verdict: All system configuration collected is at least as secure/restricted as before the VPN connection started => PASS, otherwise FAIL
* Evidence: Collected system configuration, annotations of any configuration changes explaining why they are more restricted/secure, log messages from tests, method used to force connection to end without allowing shutdown tasks to run
#### 5.2.2.5 Mapping of mitigations to risk factors and security profiles
#### 5.2.2.5 **[MI-CONF-4]** VPN client does not degrade system security
Custom VPN clients shall not require permissions that it does not need.
Guidance: The VPN product should be able to operate without a wide set of permissions - eg, a VPN does not require access to files/folders (like ~/Downloads) nor would it need access to the local network.
* Reference: TR-CONF
* Objective: Operate on a least privilege principle
* Preparation: List all the permissions that may be granted to applications
* Activities:
* Collect all the permissions that may be requested by the VPN.
* For each permission, lookup the state after the product installation.
* Start the VPN connection.
* Collect the permission states again and compare with previous version.
* Verdict: The VPN client did not request any permissions => PASS, otherwise FAIL
* Evidence: Collected permission states, annotations of any permission requests explaining why they are more restricted/secure, log messages from tests
#### 5.2.2.6 Mapping of mitigations to risk factors and security profiles
