User Guide

18-8

AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide

Chapter 18 Cisco Email Encryption

Determining Which Messages to Encrypt

• Japanese

• Portuguese

• Spanish

Before You Begin

• Create an encryption profile with Cisco Registered Envelope Service as Key Service Type and

envelope localization enabled. See Configuring How a Key Service Handles Encrypted Messages,

page 18-4.

• Make sure that Cisco Registered Envelope Service supports localization of envelopes.

Procedure

Step 1 Click Security Services > Cisco IronPort Email Encryption.

Step 2 Open an existing encryption profile.

Step 3 In the Notification Settings section, choose the locale from the Localized Envelopes drop-down list.

Step 4 Click Submit.

Step 5 Click Commit Changes.

Updating to the Latest Version of the PXE Engine

The Cisco Email Encryption Settings page displays the current versions of the PXE engine and the

Domain Mappings file used by your appliance. You can use the Security Services > Service Updates

page (or the

updateconfig command in the CLI) to configure the Email Security appliance to

automatically update the PXE engine. For more information, see Service Updates, page 33-17.

You can also manually update the engine using the Update Now button of the PXE Engine Updates

section of IronPort Email Encryption Settings page (or the

encryptionupdate command in the CLI).

Determining Which Messages to Encrypt

After you create an encryption profile, you need to create an outgoing content filter that determines

which email messages should be encrypted. The content filter scans outgoing email and determines if

the message matches the conditions specified. Once the content filter determines a message matches the

condition, the Cisco Email Security appliance encrypts the message and sends the generated key to the

key server. It uses settings specified in the encryption profile to determine the key server to use and other

encryption settings.

You can also encrypt messages after they are released after Data Loss Prevention scanning. For more

information, see Defining Actions to Take for DLP Violations (Message Actions), page 17-34.