Email encryption

 

This functionality is not applied to the Exchange Gateway. If your Exchange Gateway is peered with an Email Gateway, the functionality will be displayed in your Gateway UI.

With this configuration you can create a security policy that includes settings for this functionality, and then apply it to the peered Email Gateway. For more information, see Applying Policy to Peer Gateways.

The Email Gateway helps you to set up email encryption policies based on either policy routes or policy content rules:

Email encryption technologies

Email messages can be encrypted using key (S/MIME or PGP) encryption, password encryption, or TLS encryption.

 

If your Email Gateway is operating in FIPS Mode, PGP and password encryption will be unavailable. This is to maintain compliance with the security standards stipulated by FIPS 140-2.

Email signing

Email messages can be signed using S/MIME or PGP keys. The private key of a person is used to digitally sign a message so that the sender or recipient can prove that the message has not been tampered with by the time that it is received.

Signing messages provides the following benefits:

Exchange encrypted email with external partners

To allow external partners to send encrypted email to your organization, you can supply S/MIME or PGP keys by using Mail Initiated Key Exchange (MIKE). This process allows an external partner to request keys directly by email, and an internal user in your organization to forward keys to an external partner by email. Depending on the request and available keys, an external partner will receive your organization's public keys in the form of email attachments.

Tell me about...

How do I...