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 />

You can also use the following additional command-line switches:<br />

-org <br />

-orgunit <br />

-title <br />

-validity <br />

To use client and server certificates for the SSL connection:<br />

1. Add the certificate authority to the appliance using the Networks > Certificates page. If you<br />

generated a client/server certificate using the tool provided by RSA, import the .pem file.<br />

1. Upload the client and server certificate(s) to the Email Security appliance using the Networks ><br />

Certificates page. See the “Customizing Listeners” chapter in the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for<br />

Email Advanced <strong>Configuration</strong> <strong>Guide</strong> for more information. You can use the same certificate for the<br />

client and server. If you generated a certificate using the RSA tool, import the .p12 certificate and<br />

use it for both the client and server certificate.<br />

2. The common name of the client and server certificates must be the hostname of the Email Security<br />

appliance.<br />

3. When configuring the SSL connection using the DLP Global Settings, assign the client certificate<br />

to the Email Security appliance and the server certificate to Enterprise Manager. See Data Loss<br />

Prevention Global Settings, page 11-2 for more information.<br />

If Enterprise Manager manages the connected Email Security appliances at the group or cluster level,<br />

the appliances should each have their own certificate with a common name that matches their appliance’s<br />

hostname, but all of the certificates should have the same certificate name. Use the Network ><br />

Certificates page on the appliances to make sure that the certificate names match. If a certificate cannot<br />

be found on the Email Security appliance, Enterprise Manager disconnects the appliance.<br />

LDAP User Distinguished Name Query<br />

Message Actions<br />

When the Email Security appliance sends data to Enterprise Manager on DLP incident, the appliance<br />

must include the complete distinguished names for the message senders. To acquire the sender name for<br />

Enterprise Manager, create a user distinguished name query for your LDAP server and add the query to<br />

the listeners that send outgoing messages on your Email Security appliance. The Email Security<br />

appliance only uses this query when RSA Enterprise Manager is enabled for DLP. See the “LDAP<br />

Queries” chapter in the Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> for Email Advanced <strong>Configuration</strong> <strong>Guide</strong> for more<br />

information.<br />

When you create message actions on the Email Security appliance, the appliance sends the name of the<br />

action and some read-only metadata about the action to Enterprise Manager for DLP policies. You<br />

cannot use Enterprise Manager to modify the action or create new ones.<br />

Message actions can order the Email Security appliance to notify a user, such as a DLP compliance<br />

officer, if a DLP violation occurs. Enterprise Manager’s DLP policies can also send DLP violation<br />

notifications to users. Cisco recommends that you set up notifications using either Enterprise Manager<br />

or the Message Actions page in the Email Security appliance, but not both, to prevent duplicate<br />

notifications.<br />

See Chapter 11, “Message Actions” for more information.<br />

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

11-29

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

Saved successfully!

Ooh no, something went wrong!