Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 630
Chapter 12      IronPort Email Encryption
12-398
Cisco IronPort AsyncOS 7.1 for Email Configuration Guide
OL-22158-02
Updating the PXE Engine
The IronPort Email Encryption Settings page displays the current versions of the 
PXE engine and the Domain Mappings file used by your appliance. In previous 
versions of AsyncOS, you had to update AsyncOS in order to update the PXE 
engine. Now, you can use the Security Services > Service Updates page (or the 
updateconfig
 command in the CLI) to configure the IronPort appliance to 
automatically update the PXE engine. For more information, see 
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).
Figure 12-4
PXE Engine Updates on the IronPort Email Encryption Settings 
Page
Configuring the Encryption Content Filter
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 
IronPort 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.
Using a TLS Connection as an Alternative to Encryption
Based on the destination controls specified for a domain, your IronPort appliance 
can securely relay a message over a TLS connection instead of encrypting it, if a 
TLS connection is available. The appliance decides whether to encrypt the