Improving and Protecting the Privacy of Data Security Using Blake2 Algorithm

Abstract

Several characteristics of data open up many new avenues for exploitation, and as such, new privacy and security models are required to address these emerging challenges. The magnitude of datasets generated make it near impossible for data managers to capture all the contextual semantics relevant to a unit of data, and this causes novel difficulties in privacy and security of these data systems using BLAKE2 Algorithm. At the micro-level, a datum in any software system transitions between several phases, from inception to deletion; this is known as the data life cycle, which provides a concrete guide for tracking the many states of a unit of data. The usefulness of such a model only increases with the complexity of the system that it represents, so it is useful to examine privacy and security from this perspective, as it provides a precise framework for discussion. This paper provides practical privacy and security recommendations for every step of the data life cycle, examining prominent infrastructures and their features that relate to their data management policies using BLAKE2 Algorithm with 98.97% secure and reliable all the time. BLAKE2 is a cryptographic hash function faster than MD5, SHA-1, SHA-2, and SHA-256. The most glaring issue with SHA is that its data storage system is completely unencrypted by default. Like MD5, SHA1, and many encryption algorithms were designed to be run within a trusted environment. In the case of unencrypted data, this means that malicious parties that have physical or virtual access to the file system can extract information as they please. Fortunately, BLAKE2 is largely reliant on the client code for encryption of any sensitive information before it saves to the database. Some mitigation techniques for this scheme include implementing proper file system permissions and file system level encryption.