McAfee Data Loss Prevention 9.2.2 Product Guide

More documents

Recommendations

Info

13Managing McAfee DLP systemsAdding servers to McAfee DLP systems11 Open a web browser and enter the address of the McAfee DLP appliance in the address bar.12 Return the Windows clock setting to the correct time zone.Reset time manuallyReset time manually by stopping and restarting NTP services.Stop and restart the NTP daemon to manually reset the time.Task1 Log on as root to the McAfee DLP appliance.2 Stop the NTP daemon.# service ntpd stop# chkconfig ‐‐level 2345 ntpd off3 Restart the NTP daemon.# service ntpd start# chkconfig ‐‐level 2345 ntpd onThe service command will control the service while the system is running; the chkconfigcommands will control what happens at boot time.Syslog server message structureSyslog servers are automatically recognized if they reside on the same network as DLP devices; nospecial connection is needed. If a syslog server is installed on the network, DLP automatically sendsmessages about significant events in the following format.The health of the DLP appliances, as well as the rule hits, are automatically transferred to the syslogserver.Table 13-3 Syslog server message definitionsMessage fieldDateHost nameComponentFormatDevice vendorDevice productDevice versionRuleSeverity #PolicyPolicy labelMatch countMatch count labelSource IPDestination IPSource PortDefinitionDate the event was loggedName or IP address of the machine that logged the eventComponent or process that generated an alertFormat version of the syslog outputVendor nameManager, Monitor, Discover, Prevent or EndpointProduct versionSearch ruleCritical, High , Medium, Low, InformationalPolicy nameType of objectMatches foundType of objectSource IP addressDestination IP addressSource port260 McAfee Data Loss Prevention 9.2.2 Product Guide
Managing McAfee DLP systemsAdding servers to McAfee DLP systems 13Table 13-3 Syslog server message definitions (continued)Message fieldDestination portSource user nameDestination nameEmail subjectFile nameDefinitionDestination portSource user nameDestination user nameEmail subjectFile nameUsing DLP on directory serversThe ability to monitor user traffic on Active Directory servers now has been extended to directoryservers, making global user management a reality.The ability of McAfee Data Loss Prevention to connect to multiple domain controllers makes it possibleto capture data on local networks and up to two LDAP servers.When users can be recognized by name, group, department, city or country, a DLP administrator canextract a great deal of significant information by using a few seminal facts to gradually gather moredetails about potential violations.OpenLDAP and Active Directory server differencesMcAfee Data Loss Prevention supports OpenLDAP as well as Active Directory servers.OpenLDAP and Active Directory produce different user schemas. Active Directory has a constrained setof parameters, but OpenLDAP is completely customizable, so user implementations might vary widely.OpenLDAP and Active Directory servers identify users by using different means of user identification.Active Directory uses sAMAccountName, and OpenLDAP uses UID. LDAP queries forsAMAMccountName are handled by using the UID property on OpenLDAP systems.OpenLDAP and Active Directory servers also identify user classes by using different user attributes.Instead of the User object class, OpenLDAP uses inetOrgPerson, which does not support country or"memberOf" attributes.How directory server accounts are accessedHistorically, McAfee DLP Manager has been linked to sAMAccountName as the main user identificationelement. But if that attribute is applied to users in the same domain who have similar or matchinguser names, they cannot be identified conclusively.McAfee DLP keys on the unique alphanumeric SID (Security Identifier) that is assigned to each useraccount by the Windows domain controller.Because McAfee Logon Collector allows McAfee DLP to key on SIDs (Security Identifiers), the identitiesof individual users can be resolved and their traffic can be monitored. By leveraging multiple userattributes, it is now possible to identify end users precisely, regardless of what email or IP addressesthey are using.When a SID is retrieved from the Active Directory server, all of its associated attributes, such asdomain name, location, department and user group, come with it. That collection of information canthen be used in rules, templates, action rules, and notifications to find and stop security violations byspecific users.For example, the user name jsmith might belong to John Smith or Jack Smith, so more informationwould be needed to distinguish between those two users. They might even be using the same IPaddress, which would amplify the problem of discovering the identity of the actual user.McAfee Data Loss Prevention 9.2.2 Product Guide 261
Page 1:
Product GuideRevision AMcAfee Data
Page 6 and 7:
ContentsFind host names in data at
Page 8 and 9:
ContentsDelete views . . . . . . .
Page 10 and 11:
ContentsTypical scenarios . . . . .
Page 12 and 13:
Contents12 McAfee Data Loss Prevent
Page 14 and 15:
PrefaceFind product documentationTi
Page 16 and 17:
1McAfee DLP ManagerMcAfee DLP data
Page 18 and 19:
2Using McAfee DLP MonitorHow data i
Page 20 and 21:
2Using McAfee DLP MonitorTypical sc
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
2Using McAfee DLP MonitorSearch bas
Page 28 and 29:
2Using McAfee DLP MonitorUsing logi
Page 30 and 31:
2Using McAfee DLP MonitorSupported
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
2Using McAfee DLP MonitorRules used
Page 40 and 41:
2Using McAfee DLP MonitorFinding in
Page 42 and 43:
2Using McAfee DLP MonitorFinding in
Page 44 and 45:
2Using McAfee DLP MonitorUse concep
Page 46 and 47:
2Using McAfee DLP MonitorFind data
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
2Using McAfee DLP MonitorSearching
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
2Using McAfee DLP MonitorFinding do
Page 66 and 67:
3Managing McAfee DLP PreventHow McA
Page 68 and 69:
3Managing McAfee DLP PreventConfigu
Page 70 and 71:
3Managing McAfee DLP PreventConfigu
Page 72 and 73:
4Using McAfee DLP DiscoverTypical s
Page 74 and 75:
4Using McAfee DLP DiscoverTypical s
Page 76 and 77:
4Using McAfee DLP DiscoverRegisteri
Page 78 and 79:
4Using McAfee DLP DiscoverRegisteri
Page 80 and 81:
4Using McAfee DLP DiscoverCrawling
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
4Using McAfee DLP DiscoverOptimizin
Page 88 and 89:
4Using McAfee DLP DiscoverOptimizin
Page 90 and 91:
4Using McAfee DLP DiscoverManaging
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
4Using McAfee DLP DiscoverScan stat
Page 106 and 107:
Page 108 and 109:
4Using McAfee DLP DiscoverSearch di
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
4Using McAfee DLP DiscoverRemediati
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
4Using McAfee DLP DiscoverGetting s
Page 124 and 125:
4Using McAfee DLP DiscoverGetting s
Page 126 and 127:
4Using McAfee DLP DiscoverConfiguri
Page 128 and 129:
4Using McAfee DLP DiscoverConfiguri
Page 130 and 131:
5Integrating McAfee DLP EndpointTyp
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
5Integrating McAfee DLP EndpointVie
Page 140 and 141:
5Integrating McAfee DLP EndpointCon
Page 142 and 143:
5Integrating McAfee DLP EndpointUni
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
5Integrating McAfee DLP EndpointTag
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
6Managing the Home pageHow the Home
Page 174 and 175:
7Using the Incidents dashboardTypic
Page 176 and 177:
7Using the Incidents dashboardSort
Page 178 and 179:
7Using the Incidents dashboardGetti
Page 180 and 181:
7Using the Incidents dashboardGetti
Page 182 and 183:
7Using the Incidents dashboardSet u
Page 184 and 185:
7Using the Incidents dashboardGener
Page 186 and 187:
7Using the Incidents dashboardCusto
Page 188 and 189:
7Using the Incidents dashboardContr
Page 190 and 191:
8Working with casesManage case perm
Page 192 and 193:
8Working with casesAdd, delete, or
Page 194 and 195:
8Working with casesModify casesYou
Page 196 and 197:
8Working with casesCustomize cases3
Page 198 and 199:
8Working with casesCustomize cases4
Page 200 and 201:
9Managing policies and rulesHow pol
Page 202 and 203:
9Managing policies and rulesTypical
Page 204 and 205:
9Managing policies and rulesTypical
Page 206 and 207:
9Managing policies and rulesManagin
Page 208 and 209:
9Managing policies and rulesAdd, mo
Page 210 and 211: 9Managing policies and rulesAdd, mo
Page 212 and 213: 9Managing policies and rulesManage
Page 218 and 219: 9Managing policies and rulesIdentif
Page 220 and 221: 9Managing policies and rulesIdentif
Page 222 and 223: 10Managing action rulesHow McAfee D
Page 224 and 225: 10Managing action rulesAdd, modify,
Page 232 and 233: 11Managing conceptsTypical scenario
Page 234 and 235: 11Managing conceptsAdd, apply, rest
Page 240 and 241: 12Using templatesTypical scenariosT
Page 242 and 243: 12Using templatesAdd, modify, and d
Page 244 and 245: 12Using templatesAdd, modify, and d
Page 246 and 247: 13Managing McAfee DLP systemsConfig
Page 248 and 249: 13Managing McAfee DLP systemsConfig
Page 250 and 251: 13Managing McAfee DLP systemsUsing
Page 258 and 259: 13Managing McAfee DLP systemsAdding
Page 274 and 275: 13Managing McAfee DLP systemsManagi
Page 280 and 281: 13Managing McAfee DLP systemsTechni
Page 282 and 283: 13Managing McAfee DLP systemsTechni
Page 284 and 285: 14Disaster recovery backup and rest
Page 290 and 291: 15Technical supportCreate a technic
Page 292 and 293: Indexdevice class (continued)status
Page 294 and 295: Indexuser groupscreating 275deletin
show all

McAfee Data Loss Prevention 9.2.2 Product Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?