Application Based File Encryption: Generic corruption message for encrypted files
For application based file encryption, if a user manually encrypts a file that is not specified within the policy as a designated file type that is automatically encrypted, the user can not view the encrypted data. Sophos GES informed me that the product is designed to function this way, which makes no sense. I recommend giving the user ability to not only encrypt any file they choose, but also be able to open/read the file. My second complaint is that if the file is encrypted but not a designated file type within the policy, the user will get a generic message stating the file is corrupted. Shouldn't a Safeguard message pop up and state the file is encrypted, and in order to view the contents it will need to be decrypted? Please fix at least one of these two issues so we can avoid help desk tickets asking for file restores due to supposed 'corrupted' files that are in reality encrypted.