I recommend two courses of action. First, check the security of the recipient's machine. Is it easy to gain physical...
access? Is there a strong password policy in force? I would make the suspect change their current logon password. You should also run full virus and spyware scans to check that the machine is not infected in any way. Second, issue digital certificates, which require your employees to digitally sign and encrypt their e-mail messages. Therefore, if somebody intercepted an e-mail they couldn't read it contents, because they would not have the correct private key to decrypt it.
With a signed e-mail, only the body of the message is used to create the hash value, which means as long as someone does not tamper with the From field the verification process will remain in tact. I could, for example, change the To field to make it look like the e-mail was sent to somebody else, as the recipient's digital certificate is not required for a message that is only digitally signed. However, if I change the From field, a warning is provided as the sender information in the From field is matched to the X.509 subject name on the digital certificate used to sign the e-mail message. Overall, it would be beneficial to have a security policy stating that all important documents or messages must be signed and encrypted to ensure that they cannot be altered in any way. In cases where the person to whom you are sending such an e-mail does not have a digital certificate, meaning that you can only sign the e-mail, I would add a salutation with the date and time in the e-mail body and ensure that the context of the message is clear. You can send messages with secure receipt requests to verify that the recipient is validating your digital signature. When the message is received and saved (even if it is not yet read) but your signature is verified, a receipt is returned. However, because they are not signed, these receipts are most likely of little use.
Dig Deeper on PKI and Digital Certificates
Related Q&A from Michael Cobb
Open source NoSQL MongoDB database faced 30,000 insecure instances. Expert Michael Cobb explains the misconfiguration that led to this, and how to ...continue reading
A new Veracode report offers details on common mobile application security risks. Expert Michael Cobb explains these flaws, and what developers can ...continue reading
Juniper firewall products were found to have two backdoor vulnerabilities. Expert Michael Cobb explains how a cryptographic algorithm and hardcoded ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.