McAfee DTP-165C-DPVG Installation Guide - Page 70

Checking the connection, Configuring McAfee DLP Endpoint on McAfee DLP Manager, Add New Device

Get McAfee DTP-165C-DPVG - Network DLP Prevent 1650 Appliance PDF manuals and user guides View all McAfee DTP-165C-DPVG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

7 Integrating McAfee DLP Endpoint into a unified policy system Configuring McAfee DLP Endpoint on McAfee DLP Manager Task 1 In ePolicy Orchestrator, select Menu | Data Loss Prevention | DLP Sys Config | System Administration | Devices. 2 On your Linux-based appliance, select System | System Administration | Devices. 3 From the Actions menu, select Add New Device. 4 Select the ePO device checkbox. 5 Select Actions | New Device. 6 Enter the information gathered from the ePolicy Orchestrator Registered Server Builder | 2 Details page. 7 Click Add. 8 Click OK to confirm or Cancel the registration. 9 Wait for the Status icon in the device list to turn green. If the icon turns red, the netdlp.zip extension is probably not installed on ePolicy Orchestrator. The CPU usage display indicates that the registration tasks being performed. McAfee DLP Manager does not display any CPU activity, because it serves only as a collection point for the data. Other machines are capturing and indexing data and the processor indicates the CPU utilization. It should not go over 70-80%. If registration seems to be taking a long time, try refreshing the page. Checking the connection If your connection through McAfee DLP Manager is successful, the ePolicy Orchestrator will display a green Status icon on the System page. The status icon does not apply to the evidence server, which is normally a folder on the ePolicy Orchestrator server. If it is listed, it has been successfully added to McAfee DLP Manager. If the ePolicy Orchestrator server loses connection to the database, you cannot use https:// servername:port/core/config to reconnect to the database. Refer to KB66320 in the McAfee Knowledgebase for more information. Configuring McAfee DLP Endpoint on McAfee DLP Manager After McAfee DLP Endpoint and its components are installed on ePolicy Orchestrator, you must configure the system to start detecting endpoint events through McAfee DLP Manager. After McAfee DLP Endpoint is integrated McAfee DLP Manager, the following tasks must be completed before McAfee DLP Endpoint can work with the network product suite. • Enable unified policy management by generating a policy, setting a posting period, and selecting a backward compatibility mode. • Add an agent override password to encrypt and decrypt evidence and override default reactions. • Add a list of printer models that cannot be controlled by McAfee DLP software. • Create tags, then set up optional manual tagging 70 McAfee Data Loss Prevention 9.2.0 Installation Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
Task
1
In ePolicy Orchestrator, select
Menu
|
Data Loss Prevention
|
DLP Sys Config
|
System Administration
|
Devices
.
2
On your Linux-based appliance, select
System
|
System Administration
|
Devices
.
3
From the
Actions
menu, select
Add New Device
.
4
Select the
ePO device
checkbox.
5
Select
Actions
|
New Device
.
6
Enter the information gathered from the ePolicy Orchestrator
Registered Server Builder
|
2 Details
page.
7
Click
Add
.
8
Click
OK
to confirm or
Cancel
the registration.
9
Wait for the
Status
icon in the device list to turn green.
If the icon turns red, the netdlp.zip extension is probably not installed on ePolicy Orchestrator.
The CPU usage display indicates that the registration tasks being performed. McAfee DLP Manager
does not display any CPU activity, because it serves only as a collection point for the data. Other
machines are capturing and indexing data and the processor indicates the CPU utilization. It should
not go over 70—80%.
If registration seems to be taking a long time, try refreshing the page.
Checking the connection
If your connection through McAfee DLP Manager is successful, the ePolicy Orchestrator will display a
green
Status
icon on the
System
page.
The status icon does not apply to the evidence server, which is normally a folder on the ePolicy
Orchestrator server. If it is listed, it has been successfully added to McAfee DLP Manager.
If the ePolicy Orchestrator server loses connection to the database, you cannot use
https://
servername:port/core/config
to reconnect to the database. Refer to KB66320 in the McAfee
Knowledgebase for more information.
Configuring McAfee DLP Endpoint on McAfee DLP Manager
After McAfee DLP Endpoint and its components are installed on ePolicy Orchestrator, you must
configure the system to start detecting endpoint events through McAfee DLP Manager.
After McAfee DLP Endpoint is integrated McAfee DLP Manager, the following tasks must be completed
before McAfee DLP Endpoint can work with the network product suite.
•
Enable unified policy management by generating a policy, setting a posting period, and selecting a
backward compatibility mode.
•
Add an agent override password to encrypt and decrypt evidence and override default reactions.
•
Add a list of printer models that cannot be controlled by McAfee DLP software.
•
Create tags, then set up optional manual tagging
7
Integrating McAfee DLP Endpoint into a unified policy system
Configuring McAfee DLP Endpoint on McAfee DLP Manager
70
McAfee Data Loss Prevention 9.2.0
Installation Guide