[email protected] vault Documentation
description

[email protected] Vault is a new generation software for highly secure data protection and transmission.

The operating principle of the main algorithm is based on the rescheduling of the binary structure of the source files to be secured, and not on the conventional principles and algorithms of data encryption.

Once the data is encoded, the user will obtain as a result a secured main vault file as well as 3 key files that allow its opening, as it is the case, for example, in Swiss banks.

During the process of securing, some parts of the binary code of the source files are transposed by our algorithms and removed in the output files.

In other words, the output files do not contain enough information to regenerate the source files.

The missing parts are impossible to reconstruct without the use of the [email protected] Vault software and without having all the authorizations required for accessing the protected data.

This is one of the reasons why the output files do not have in the end any coherence and cannot give any indication on the nature of the protected data.

Therefore, the output files can be exposed to the public without ever compromising their security. Access remains impossible until one knows which physical keys open which safes and until one has all of the decoding permissions.

In addition to initial data security, the [email protected] Vault application has multiple options for restricted and limited access to protected files, providing absolute and irreversible protection of the information.

Elapsed time is used as a random security factor, as well as the generation and the factorization of very large prime numbers used as encryption keys (3 000, 9 000 and up to 27 000 bits in length).
Hardware restrictions can be applied on the storage media on which the secured data are to be stored.

It is possible to physically limit the machines that can access the information by the usage of the Ex0-UiD system restriction.

There are three basic protection modes describing the three levels of vaults detailed as follows :

  • Encoding Vault Level 1 in blue
  • Encryption Vault Level 2 in yellow
  • Encryption Vault Level 3 in red

Thanks to [email protected] Vault, it is possible to protect and transmit any type of file (i.e.: Office documents / multimedia files / archive files / or any other type of numeric data) with absolute security.

The time requirement for the data protection process can vary greatly depending on the nature and size of each source file selected.

The size of the protected files will also vary depending on the nature of the input files and they may end up being larger than the source files themselves.

[email protected] vault level 1

Vault Level 1 – Encoding Protection

The data is encoded by the algorithm [email protected] Data Fragmentation, which was developed in absolute secrecy.

To decode the secured data, one needs to have the Main-Vault-File (*.atd) and its three corresponding Physical-Key-Files (*.atk1 / *.atk2 / *.atk3).

Each time the same source input files are encoded, it results in the exact same binary structure of the output files.

The security of protected files is guaranteed by the absolute necessity of having at the same time and in the same place the Main-Vault-File and the three corresponding Physical-Key-Files.

If any of the files are missing or damaged, the data will be lost forever and no one will be able to retrieve it, not even [email protected] developers.

Indeed, in this context, it becomes completely impossible to retrieve the information, because there isn’t any longer a way to examine the secured data and to find clues which would reconstruct the original information.

[email protected] vault level 2

Vault Level 2 – Encoding Protection with Temporal Encryption

The data, in addition to being encoded thanks to the [email protected] Data Fragmentation algorithm, is also encrypted thanks to a dynamic random factor which relies on the passage of time in perpetual evolution and in an irreversible way.

To decode the secured data, the user will need to have the Main-Vault-File (* .atd) and its three corresponding Physical-Key-Files (* .atk1 / * .atk2 / * .atk3).

The user will need the correct PIN code in TEXT or QR-Code format that represents the time factor used during the encryption process.

Each time the same source input files are encrypted, the resulting binary structure of the output files will be different.

This is because time is used as a dynamic random factor for binary rescheduling of the information during the data securing process.

The security of protected files is guaranteed on the one hand by the absolute necessity of having at the same time and in the same place the Main-Vault-File as well as its three corresponding Physical-Key-Files, and on the other hand by owning or knowing the PIN code necessary for decryption.

If any of the files are missing or damaged, or if one does not have the correct Time PIN, it’s impossible to decrypt the protected data, even by [email protected] developers.

Indeed, in this context, it becomes totally impossible to retrieve the information, because there isn’t any longer a way to find any analysable or apprehensible consistency which would reconstruct the original information.

[email protected] vault level 3

Vault Level 3 – Encoding Protection plus Temporal Encryption and Personal Password

The data, in addition to being encoded thanks to the algorithm [email protected] Data Fragmentation, is also encrypted thanks to a dynamic random factor which relies on the passage of time in perpetual evolution and in a non-reversible way.

The time-related random factor is itself modulated by the addition of a password to customize the security level.

To decode the secured data, one will need to have the Main-Vault-File (*.atd) and its three corresponding Physical-Key-Files (*.atk1 / *.atk2 / *.atk3).

The user will also need the correct PIN code in TEXT or QR-Code format that represents the time factor used during the encryption process and will need to know the correct password to open the set.

Each time the same source input files are encrypted, the resulting binary structure of the output files will be different.

This is because time is used as a dynamic random factor for binary rescheduling of the information during the data securing process and because it is additionally subject to a unique additional modulation related to the password defined by the user (the more complex it is, the more security increases).

The security of protected files is guaranteed on the one hand by the absolute necessity of having at the same time and in the same place the Main-Vault-File as well as its three corresponding Physical-Key-Files, and on the other hand by having both the PIN code and the password required for decryption.

If any of the files are missing or damaged, or if one does not have the correct Time PIN or the correct password, it’s impossible to decrypt the protected data, even by [email protected] developers.

Indeed, in this context, it becomes totally impossible to retrieve the information, because there is no longer any way to find any analysable or apprehensible consistency which would reconstruct the original information.

[email protected] vault ex0-uid

The Ex0-UiD is a one-way hardware identification system that cannot be reversed elsewhere than on the machine where it has been generated.

This identifier permits to establish with certainty if a machine is indeed what it claims to be (Anti-Spoofing) at the time when the test is performed on the machine itself and nowhere else.

This system does not collect or transmit any personal or reversible information.

The information used by the Ex0-UiD system is retrieved from the machine identifiers, such as those relating the computer hardware and some other logical information about the installation ID’s of the Microsoft Windows operating system plus the name of the computer.

Once algorithmically transformed, the information about the actual machine identifiers becomes impossible to reconstruct anywhere else than from the source machine itself (i.e. the user’s computer only).

The only information transparently available in the Ex0-UiD is the name of the computer, as it cannot be used for strict identification purposes, since it can be changed at any time by users.

The name of the computer is only available for convenience when passing on the Ex0-UiD to a third party, so that it may be loaded into the list of  machines that are physically authorized to access secure data when setting
the restriction options.

To generate the Ex0-UiD, our algorithm substitutes the information relating to the real hardware and logical identifiers of the computer, in order to obtain equivalences in NON-Reversible HASH codes.

This transposition operation in HASH code is performed without keeping the correspondence tables with the original real identifiers.

It becomes impossible to use the Ex0-UiD in order to reconstitute the user’s real identifiers, because it cannot be checked and it can only return a coherent information on the computer from which it was generated.

The number of possibilities to find the original real matching table of the identifiers in the right sequence is so large that a single and same Ex0-UiD possesses billions of billions of billions of potentially real correspondence
tables.

At best, it is possible to certify that the machine is one of these billions of possibilities — which is of no interest for the user’s identification, because identifying means, above all, being able to precisely target.

On the other hand, when analyzed on the machine from which it was generated, the Ex0-UiD allows by a simple and extremely quick operation to assert with certainty and without any possible error that it comes from this machine and from no other.

The Ex0-UiD system thus has an absolutely reliable identification function of a physical machine without exposing its confidentiality by a reversible system, as it is probably the case for all the current identification systems using hardware identifiers.

This absolute control reliability serves on the one hand to protect our own software license management systems against hacking, and on the other hand to significantly increase the security of the user’s own data.

With the Ex0-UiD system, it is impossible to cheat, either the user’s machine can exploit this or that type of information, or it simply cannot!

Invite & Earn

Signup to start sharing your link
Signup