Previous Topic: OverviewNext Topic: SecureMail Integration and Quarantine Manager


Requirements

Note the following requirements for CA Data Protection integration with Voltage SecureMail:

Voltage SecureMail

When you enable integration with Voltage SecureMail, CA Data Protection policy engines can access unencrypted versions of emails that were encrypted by Voltage SecureMail clients or the Voltage Zero Download Messenger.

CA Data Protection integrates with the following versions of Voltage SecureMail:

Voltage SecureMail Server

You must supply your policy engines with connection details and a shared secret for the Voltage SecureMail web service

Voltage SecureMail Gateway

(Optional) CA Data Protection integration with Voltage SecureMail does not directly require a SecureMail Gateway. However, if you use the CA Data Protection Quarantine Manager to quarantine suspect emails, you must deploy a SecureMail Gateway on your network. The SecureMail Gateway ensures that emails released from quarantine are re-encrypted before they are forwarded to external recipients.

Which agents can detect SecureMail-encrypted emails?

The following CA Data Protection agents can detect and apply policy to emails encrypted by Voltage SecureMail:

Policy engines and SSL certificates

CA Data Protection policy engines use the Secure Sockets Layer protocol (SSL) to establish a secure connection to the Voltage SecureMail web service. To ensure that the policy engine and SecureMail web service trust each other, each policy engine must hold a copy of the root certificate that was used to generate the SecureMail certificate.

More information:

Establish an SSL Connection to the SecureMail Web Service