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.

Chapter 11 Data Loss Prevention<br />

OL-25136-01<br />

To create the .zip file, click Export DLP <strong>Configuration</strong> on the Data Loss Prevention Settings page.<br />

Enter a name for the .zip file and click Export. The Email Security appliance includes all active DLP<br />

policies assigned to an outgoing mail in the .zip file. Disabled DLP policies and DLP that are not<br />

assigned to an outgoing mail policy are not included in the .zip file.<br />

If the Email Security appliance is part of the cluster, the appliance only exports the policies from the<br />

lowest level of the cluster. For example, if there are DLP policies at both the cluster and machine level,<br />

the appliance only exports the DLP policies from the machine level.<br />

If the appliance is using RSA Enterprise Manager for DLP, you can use these instructions to export the<br />

active DLP policies that Enterprise Manager sent to the appliance.<br />

The file is ready to be imported in Enterprise Manager. See the RSA Enterprise Manager help for<br />

instructions on importing the configuration into Enterprise Manager.<br />

Switching Data Loss Prevention Modes<br />

Message Actions<br />

If you want to go back to using RSA Email DLP for data loss prevention after using RSA Enterprise<br />

Manager, use the Global Settings page to switch back to RSA Email DLP mode by following the steps<br />

in Enabling RSA Email DLP, page 11-3.<br />

The Email Security appliance automatically reverts back to the RSA Email DLP policies it used before<br />

you configured it to use RSA Enterprise Manager mode. If the appliance did not use any local DLP<br />

policies when it was in RSA Email DLP mode, the appliance will continue to use the DLP policies from<br />

Enterprise Manager until you create a local DLP policy.<br />

If you want to use local DLP policies similar to the ones on Enterprise Manager, you can recreate them<br />

using the DLP Policy Manager. The Email Security appliance does not automatically create new policies<br />

based on the ones used by Enterprise Manager and they cannot be imported from Enterprise Manager.<br />

See Creating an Email DLP Policy Based on a Predefined Template, page 11-13 for information on<br />

creating DLP policies using the DLP Policy Manager.<br />

See the RSA Enterprise Manager help for instructions on removing the Email Security appliance as a<br />

partner device in Enterprise Manager if you want to stop using Enterprise Manager to manage the<br />

appliance’s DLP policies.<br />

When the Email Security appliance detects a possible DLP violation in an outgoing message, it needs to<br />

know what to do with the message. Message actions define a primary action for the Email Security<br />

appliance to take with the message, which can be Deliver, Drop, or Quarantine. You can also specify<br />

secondary actions to take on messages. Secondary actions include:<br />

Sending a copy to a system quarantine if you choose to deliver the message. The copy is a perfect<br />

clone of the original, including the Message ID. Quarantining a copy allows you to test the RSA<br />

Email DLP system before deployment in addition to providing another way to monitor DLP<br />

violations. When you release the copy from the quarantine, the appliance delivers the copy to the<br />

recipient, who will have already received the original message.<br />

Encrypting messages. The appliance only encrypts the message body. It does not encrypt the<br />

message headers.<br />

Altering the subject header of messages containing a DLP violation.<br />

Adding disclaimer text to messages.<br />

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

11-5

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

Saved successfully!

Ooh no, something went wrong!