Evolution Of The Windows File Encryption

As far as the computer world goes. File security is a big deal that is handled with utmost concern. File encryption is one of many ways by which operating systems ensure file security. It is a transparent form of totally restricting attackers from gaining access to files.

Encryption is a form of security that has evolved over the years on Windows systems. However, Windows systems did not have file encryption until the advent of Windows 2000. It was on the NFTS version 3.0 that the Windows file encryption was introduced.

As encryption can be performed on a file, directory or drive; A group policy can also be used to enforce some file encryption settings on some Windows system. Every version of Windows from 2000 has been enabled with a Windows file encryption mechanism.

Drawbacks of Windows File Encryption

Based on the outcome of research and popular opinion, encrypted files can be lost infinitely on systems. Should a reinstallation fail, there is a chance that the key used for encryption will be lost. The encrypted files may be lost forever in such circumstances.

The encryption system on Windows 7 comes with a backward compatibility algorithm. It would be considered as a rigid system if backward compatibility is ever an issue. This is because files encrypted on an older version of windows would not be easily accessed on a newer version of it.

Added Values of Windows File Encryption

The general cover the encryption provides is absolute protection against attacks. This is beneficial to the because only a user that initiates a file encryption can have it decrypted.

Permissions become granted to files based on who has the key to decrypt the particular file. This is a very convenient to maintain a hierarchy of access to files, directories, and drives in an organization.

It means a different level of access can be enforced on a storage facility and whoever has permission to access every part of the system is the administrator. The administrator can also decide who gets access to what.

What this translates to is that; a supervisor’s access to a company’s database might not be as robust as that of the manager while that of the manager might be inferior to that of the director.

The flexibility and ease of configuration also ensure that someone with a particular permission might be assigned a higher level of access without access to a new permission key. This is because the administrator can easily upgrade the user’s status.

Going by the earlier example, a manager can be granted a director’s permission if such need arises. Someone with a higher permission key can readily access what someone with a lower permission can access. This means, the higher your permission, the wider your range of access.