12.07.2015 Views

McAfee Data Loss Prevention 9.2.2 Product Guide

McAfee Data Loss Prevention 9.2.2 Product Guide

McAfee Data Loss Prevention 9.2.2 Product Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Integrating <strong>McAfee</strong> DLP EndpointMaintaining compatibility with installed agents 5Such operations require users to provide two types of authentication — an ID Code and a ReleaseCode.• The ID Code is generated by <strong>McAfee</strong> DLP Agent, which uses the Agent Override Password with analgorithm to calculate a code. That number automatically populates a field in a pop‐up that islaunched whenever authentication is required.• The Release Code must be provided by an ePolicy Orchestrator administrator, and this code mustbe provided verbally during an offline call.When both codes are entered into the fields in the pop‐up, the Agent goes into bypass mode, and theoperation is allowed.If <strong>McAfee</strong> Endpoint Encryption for PC is installed, a pop‐up might prompt the user for a key that isgenerated by that product.However, if a Request Justification pop‐up is launched when a file is opened, a password is not required.The user simply types in an justification, and the administrator monitors the text entries periodically.Task1 Select one of these options:• In ePolicy Orchestrator, select Menu | <strong>Data</strong> <strong>Loss</strong> <strong>Prevention</strong> | DLP Sys Config | Endpoint Configuration |Miscellaneous and click Agent Override Password.• On your <strong>McAfee</strong> DLP appliance, select System | Endpoint Configuration | Miscellaneous and click AgentOverride Password.2 Enter a password in the Password field and confirm it.This sets up a password that is used by <strong>McAfee</strong> DLP Agent to generate an ID Code.3 Click Submit.Maintaining compatibility with installed agents<strong>McAfee</strong> DLP Manager might have to support many different versions of the <strong>McAfee</strong> DLP agent thatwere installed at different times on many different endpoints.Because interoperability must be supported in such cases, the default configuration is set to DLP Agent9.0 and above.But if earlier versions do not have to be supported, you can select No compatibility with earlier agents,and the full functionality of <strong>McAfee</strong> DLP 9.2 will be available, and new features like Document Scan Scopeand Password Protected Files can be used.The compatibility selection is not activated until you generate a policy on the Manage Endpoints page. Thenetworked product suite cannot monitor endpoints until a policy is assigned, and events cannot begenerated until the <strong>McAfee</strong> DLP client has been updated through ePolicy Orchestrator and <strong>McAfee</strong> DLPManager.Manage endpointsWhen you generate a policy for <strong>McAfee</strong> DLP Endpoint, you must also set a posting interval thatregulates the distribution of events.If <strong>McAfee</strong> Host DLP is installed on ePolicy Orchestrator, using the networked <strong>McAfee</strong> DLP Endpointversion will overwrite the events on the evidence server. Because of this potential problem, you mustgenerate a policy to support installation of the updated product.<strong>McAfee</strong> <strong>Data</strong> <strong>Loss</strong> <strong>Prevention</strong> <strong>9.2.2</strong> <strong>Product</strong> <strong>Guide</strong> 141

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

Saved successfully!

Ooh no, something went wrong!