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

Connecting McAfee DLP Manager and the ePolicy Orchestrator server

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 68 highlights

7 Integrating McAfee DLP Endpoint into a unified policy system Connecting McAfee DLP Manager and the ePolicy Orchestrator server • Hostname - \\ • IP Address - • Username -

  • 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
•
Hostname
— \\<server name>
•
IP Address
— <IP address>
•
Username
— <domain name\user name
•
Password
— ********
5
Click
Add
.
Connecting McAfee DLP Manager and the ePolicy Orchestrator
server
McAfee DLP Manager and the ePolicy Orchestrator server must be authenticated to each other to
initiate the unified policy installation.
Each product requires information from the other before they can be connected. The database name is
needed from ePolicy Orchestrator, and an
epouser
account is needed from the McAfee DLP Manager.
Gather ePolicy Orchestrator registration information
You must log on to the ePolicy Orchestrator server
(https://servername:port/core/config)
and
SQL Server Configuration Manager
to get the information needed to register McAfee DLP Manager on McAfee
ePO.
Table 7-1
Sources for ePolicy Orchestrator data
Field or menu item
Where to find data
ePO database IP address or
hostname
Menu
|
Configuration
|
Registered Servers
(local McAfee ePO server)
ePO database password
The SQL password created in
Microsoft SQL Server Management Studio
ePO database port
SQL Server Configuration Manager
|
TCP/IP Properties
|
IP Addresses
|
TCP Ports
ePO database user
The logon name created in
Microsoft SQL Server Management Studio
Unified policy / Incident copy
If incident copy only is selected, no policy updates will be routed to
endpoints through ePolicy Orchestrator
ePO database
Menu
|
Configuration
|
Registered Servers
|
Actions
|
Edit
|
Next
|
Database instance
ePO database instance
Menu
|
Configuration
|
Registered Servers
|
Actions
|
Edit
|
Next
|
SQL Server
instance
|
instance name
ePO GUI IP address
Address bar of McAfee ePO server
ePO GUI user
User account name used to log on to McAfee ePO server
ePO GUI password
User account password used to log on to McAfee ePO server
ePO GUI port
Address bar of McAfee ePO server
Add a McAfee ePO database user for McAfee DLP Manager
Create ePolicy Orchestrator database users to authenticate connections from McAfee DLP Manager to
ePolicy Orchestrator servers. ePolicy Orchestrator servers are Windows-based, but a McAfee DLP
Manager is a Linux server that does not support Windows-based authentication of users. Database
user accounts are used to make the connection.
Creating an ePolicy Orchestrator database user is only one aspect of establishing a connection to the
ePolicy Orchestrator server, which is required to support McAfee DLP Endpoint features.
7
Integrating McAfee DLP Endpoint into a unified policy system
Connecting McAfee DLP Manager and the ePolicy Orchestrator server
68
McAfee Data Loss Prevention 9.2.0
Installation Guide