 Server Policies and Master Keys
We have a several PGP users in the office. There are two things that we might like to see in a company-wide solution.
Server Policies.
It is on a per-person basis at the moment, but it would be nice to have rules set up (much like spam filter rules) that can make decisions on when to sign, and when to encrypt. I expect most of our users will want to continue using their mail readers and not use the web client. But how would they, then, tell Zimbra to encrypt their email?
The policy rules are built on rather simple building blocks: header values, items in subject line. (Examples: If Sensitivity header is "confidential", then encrypt message. If subject starts with "[GPG]" and Priority is High, then encrypt.)
There should also be rules that run on a failure to find a key. So that it can reject emails it could not encrypt.
On a global level, I would like to see the ability to enforce some items, like make everyone sign every mail that goes out. (A possible corporate policy).
Master Keys
We found that PGP's concept of Master Keys can be quite useful. These are keys that are added to every encrypted message you send. In most cases, it is so that you can always include your own key. This allows you to always decrypt anything you send, even if you did not send it to yourself. But, it could also be used to include a corporate key. This could solve the problem of personal keys leaving with people. If an important business email was encrypted from or to an ex-employee, it would give administrators a way to decrypt it and make sure that information was given to the new employee in that role.  |