27.11.2012 Views

IronPort - Configuration Guide - AsyncOS 7.6.1

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

11-6<br />

Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email <strong>Configuration</strong> <strong>Guide</strong><br />

Chapter 11 Data Loss Prevention<br />

Sending messages to an alternate destination mailhost.<br />

Sending copies (bcc) of messages to other recipients. (For example, you could copy messages with<br />

critical DLP violations to a compliance officer’s mailbox for subsequent examination.)<br />

Sending a DLP violation notification message to the sender or other contacts, such as a manager or<br />

DLP compliance officer.<br />

Message actions can be taken on all DLP policy severity levels except Ignore. See Setting the Severity<br />

Levels, page 11-15 for more information on severity levels for RSA Email DLP.<br />

Note These actions are not mutually exclusive: you can combine some of them within different DLP policies<br />

for various processing needs for different user groups. You can also configure different treatments based<br />

on the different severity levels in the same policy. For example, you may want to quarantine messages<br />

with critical DLP violations and send a notification to a compliance officer but deliver messages with<br />

low severity levels.<br />

Creating a Message Action<br />

For RSA Email DLP, specify the message actions you want your DLP policies to use when creating or<br />

editing the policies using the DLP Policy Manager. See DLP Policy Manager, page 11-11 for more<br />

information.<br />

For RSA Enterprise Manager, create the message actions on your Email Security appliance first. The<br />

appliance sends the names and metadata of the message actions to Enterprise Manager, allowing you to<br />

use the actions in the DLP policies you create and manage in Enterprise Manager. See the RSA<br />

Enterprise Manager technical documentation for more information.<br />

If you upgrade an appliance with existing DLP policies to <strong>AsyncOS</strong> 7.6, the operating system<br />

automatically converts the actions defined in the existing policies into message actions and updates the<br />

policies accordingly. <strong>AsyncOS</strong> generates names for the message actions but you can rename them using<br />

the DLP Message Actions page in the GUI. For information on renaming actions, see Editing a Message<br />

Action, page 11-8.<br />

The DLP Message Actions page displays a list of the actions on your appliance. Click the Policies link<br />

in the Message Actions table to see the policies to which each action is assigned. Click the Description<br />

link to see a description of each action.<br />

Figure 11-1 List of Actions on an Email Security Appliance<br />

Step 1 Select Mail Policies > DLP Message Actions.<br />

Step 2 Click Add Message Action. The Add Message Action page is displayed.<br />

OL-25136-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!