Data protection has at least two components: security and privacy protection and data integrity protection.

The security of a system contains many aspects. Each one of them is very technical and does not has a short or an open answer. V-NET uses modern and well known security technologies and measures (like strong password protection, TLS data encryption, etc.) and will continue to improve our security technology and policy to protect data of our users.

Based on that, the artitecture of V-NET can be leveraged to add new security measures. For example, the above mentioned policy of not allowing data to stay on the service side, which reduces the risk of data leaks if our service side gets compromised by an intruder. V-NET has effectively a multi-factor user identity authentication system that can be utilized to reduce many kinds of known security attacks.

Many security breaches are not due to the fact that an intruder finds a weakness in the system itself but because of the result of social engineering or human error, like leaking the password of an account. However leaking a password does minimal damage to a data due to the directed data exchange of our system. The intruder that has the password of a user will still not be able to trick the endpoints controlled by the owner to exchange data with the ones under the control of the intruder without been exposed early on. There are measures for the owner of the account to recover quickly if that happen.

Data integrity check is not performed by most current data exchange means. In V-NET, it is a default behaviour when sending data to an app client. However, for browser endpoints, integrity check can not be performed for data targeting to them when the non-V-NET download agents (see the following) is used to receive the data. Details about it can be found inside the help page of the data sink page when login (V-NET) from a browser.