McAfee EPOCDE-AA-BA Product Guide - Page 168

About system-based policy assignments, Using tags to assign system-based policies

Page 168 highlights

15 Using policies to manage products and systems How policy assignment rules work On a managed system, the agent keeps a record of the users who log on to the network. The policy assignments you create for each user are pushed down to the system they log on to, and are cached during each agent-server communication. The agent applies the policies that you have assigned to each user. When a user logs on to a managed system for the first time, there can be a slight delay while the agent contacts its assigned server for the policy assignments specific to this user. During this time, the user has access only to that functionality allowed by the default machine policy, which typically is your most secure policy. To use user-based policy assignments, you must first register and configure a registered LDAP server for use with your ePolicy Orchestrator server. About migrating legacy policy assignment rules Policy assignment rules created using a version 4.5 ePolicy Orchestrator server were user-based by default. For migrated legacy policy assignment rules with no user-based criteria specified, the rules will continue to be evaluated as user-based. However, when creating a new user-based policy assignment rule , you must specify at least one user-based criteria. Applying your migrated legacy user-based policy assignment rules causes your ePolicy Orchestrator server to perform a look up on the LDAP server for every managed system in your network at each agent-server communication interval. About system-based policy assignments System-based policies allow you to assign policies to systems using system based criteria. You can assign a system-based policy using two types of system-based criteria: • System Tree location - All policy assignment rules require that System Tree location is specified. • Tags - User defined tags can be used to assign policies to system based on the tags you have applied. Once you have defined and applied a tag to your systems, you can create a policy assignment rule to assign policies to any system with that tag. This functionality is useful in cases when you want all systems of a particular type to have the same security policy, regardless of their location in the System Tree. Using tags to assign system-based policies Using tags to assign system-based policies makes automating policy assignment easier than ever. System-based policies which specify tags as criteria work in a similar fashion to user-based policies. They are assigned based on selection criteria you define using the Policy Assignment Builder. Any system you can tag, you can apply a specific policy to, based on that tag. 168 McAfee® ePolicy Orchestrator® 4.6.0 Software Product 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
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

On a managed system, the agent keeps a record of the users who log on to the network. The policy
assignments you create for each user are pushed down to the system they log on to, and are cached
during each agent-server communication. The agent applies the policies that you have assigned to
each user.
When a user logs on to a managed system for the first time, there can
be a slight delay while the agent contacts its assigned server for the
policy assignments specific to this user. During this time, the user has
access only to that functionality allowed by the default machine policy,
which typically is your most secure policy.
To use user-based policy assignments, you must first register and
configure a registered LDAP server for use with your ePolicy Orchestrator
server.
About migrating legacy policy assignment rules
Policy assignment rules created using a version 4.5 ePolicy Orchestrator server were user-based by
default. For migrated legacy policy assignment rules with no user-based criteria specified, the rules
will continue to be evaluated as user-based. However, when creating a new user-based policy
assignment rule , you must specify at least one user-based criteria.
Applying your migrated legacy user-based policy assignment rules
causes your ePolicy Orchestrator server to perform a look up on the
LDAP server for every managed system in your network at each
agent-server communication interval.
About system-based policy assignments
System-based policies allow you to assign policies to systems using system based criteria.
You can assign a system-based policy using two types of system-based criteria:
System Tree location — All policy assignment rules require that System Tree location is specified.
Tags — User defined tags can be used to assign policies to system based on the tags you have applied.
Once you have defined and applied a tag to your systems, you can create a policy assignment rule to
assign policies to any system with that tag. This functionality is useful in cases when you want all
systems of a particular type to have the same security policy, regardless of their location in the
System Tree.
Using tags to assign system-based policies
Using tags to assign system-based policies makes automating policy assignment easier than ever.
System-based policies which specify tags as criteria work in a similar fashion to user-based policies.
They are assigned based on selection criteria you define using the Policy Assignment Builder. Any
system you can tag, you can apply a specific policy to, based on that tag.
15
Using policies to manage products and systems
How policy assignment rules work
168
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide