How can I prevent someone from modifying the contents of an email they received and then forwarding it to others? Some employees cheat managers by changing the content of emails and forwarding the modified email to them. I need a policy that prevents this backdoor.
|
|
Email is an insecure communication channel. The "to" and "from" headers can be set to anything. Anything can be written into the body of an email message. This includes changing the quote text. The first issue of manipulating "to" and "from" headers can be prevented in a closed environment such as company internal mail. The company mail server can verify that the "from" header matches the account used to send the email. And it can verify that the visible "to" header matches the real recipient. But there is no easy and reliable way to prevent manipulation of quoted text. You could use GPG / PGP or s/mime signatures. But rolling out a public/private key infrastructure is usually not worth the costs. SummaryThere is no simple technical solution. Use a social or legal approach ("Cheating a manager" sounds serious enough to warrant a talk with the human resources department). |
|||
|
|
|
Email is unsafe -- deal with it. Email can be made safe for an adequately defined value of "safe", through the use of signatures (S/MIME or OpenPGP). This is not as easy as it seems (I mean, it does not look easy, but in reality it is worse). The cornerstone of the system is that unsigned emails should be rejected automatically; human users should never see them at all, because if they read them, they will always believe them a little, regardless of how much you may have explained to them how insecure and unsafe plain emails are. Therefore, switching to signed emails is like a big jump into the unknown. In practice, it is essentially a way to break emails (or to induce users to switch to gmail...). What you can do is to educate and then to educate again:
|
|||
|
|
|
This is what cryptographic signatures are for. GPG or PGP signed messages ensure integrity of the messages. |
|||
|
|
|
Besides the very valid answer of having managers sign communications, referencing sources would be the other appropriate way of handling things. If there's a debate about the content of an email, the sent messages archive is the better reference for each party. If you have an email archiving system, then the server's copy of the message would be best. At that point, we're back to the human element. If you forge an email and the server shows that you wrote something which wasn't really sent then you can forget about having a job. One last comment on signing: a caveat with signing is that you'll run into issues where the message is signed, then altered, then sent. If the receiver doesn't verify every signature, then nothing would really be "valid." |
|||
|
|
|
Archive it - this is what archiving is for. People treat email like it's gospel but it's so easy to manipulate (as you've identified). There are some off the shelf solutions, or you can get some consultancies to roll out a whole apparatus just for archiving - SaaS sort of thing. |
||||
|
|