Get Discount
alph@tav vault Documentation
description

Alph@TaV 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 Alph@TaV 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 Alph@TaV 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 Alph@TaV 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.

alph@tav vault level 1

Vault Level 1 – Encoding Protection

The data is encoded by the algorithm Alph@TaV 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 Alph@TaV 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.

alph@tav vault level 2

Vault Level 2 – Encoding Protection with Temporal Encryption

The data, in addition to being encoded thanks to the Alph@TaV 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 Alph@TaV 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.

alph@tav 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 Alph@TaV 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 Alph@TaV 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.