McAfee EPOCDE-AA-BA Product Guide - Page 167

About user-based policy assignments, Scenario: Using multi-slot policies to control Internet access

Page 167 highlights

Using policies to manage products and systems How policy assignment rules work 15 How multi-slot policies work with policy assignment rule priority Priority of rules is not considered for multi-slot policies. When a single rule containing multi-slot policies of the same product category is applied, all settings of the multi-slot policies are combined. Similarly, if multiple rules containing multi-slot policy settings are applied, all settings from each multi-slot policy are combined. As a result, the applied policy is a combination of the settings of each individual rule. When multi-slot policies are aggregated, they are aggregated only with multi-slot policies of the same type; user-based or system-based. However, multi-slot policies assigned using policy assignment rules are not aggregated with multi-slot policies assigned in the System Tree. Multi-slot policies assigned using policy assignment rules override policies assigned in the System Tree. Furthermore, user-based policies take priority over system-based policies. Consider the following scenario where: Policy type Assignment type Generic policy Policy assigned in the System Tree System-based Policy assignment rule User-based Policy assignment rule Policy name A B C Policy settings Prevents internet access from all systems to which the policy is assigned. Allows internet access from systems with the tag "IsLaptop." Allows unrestricted internet access to all users in the Admin user group from all systems. Scenario: Using multi-slot policies to control Internet access In your System Tree, there is a group named "Engineering" which consists of systems tagged with either "IsServer" or "IsLaptop." In the System Tree, policy A is assigned to all systems in this group. Assigning policy B to any location in the System Tree above the Engineering group using a policy assignment rule overrides the settings of policy A, and allows systems tagged with "IsLaptop" to access the internet. Assigning policy C to any group in the System Tree above the Engineering group allows users in the Admin user group to access the internet from all systems, including those in the Engineering group tagged with "IsServer." Excluding Active Directory objects from aggregated policies. Because rules that consist of multi-slot policies are applied to assigned systems without regard to priority, you might need to prevent policy setting aggregation in some instances. You can prevent aggregation of user-based multi-slot policy settings across multiple policy assignment rules by excluding a user (or other Active Directory objects such as a group or organizational unit) when creating the rule. For more information on the multi-slot policies that can be used in policy assignment rules, refer to the product documentation for the managed product you are using. About user-based policy assignments User-based policy assignment rules give you the ability to create user specific policy assignments. These assignments are enforced at the target system when a user logs on. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 167

  • 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

How multi-slot policies work with policy assignment rule priority
Priority of rules is not considered for multi-slot policies. When a single rule containing multi-slot
policies of the same product category is applied, all settings of the multi-slot policies are combined.
Similarly, if multiple rules containing multi-slot policy settings are applied, all settings from each
multi-slot policy are combined. As a result, the applied policy is a combination of the settings of each
individual rule.
When multi-slot policies are aggregated, they are aggregated only with multi-slot policies of the same
type; user-based or system-based. However, multi-slot policies assigned using policy assignment rules
are not aggregated with multi-slot policies assigned in the System Tree. Multi-slot policies assigned
using policy assignment rules override policies assigned in the System Tree. Furthermore, user-based
policies take priority over system-based policies. Consider the following scenario where:
Policy type
Assignment type
Policy
name
Policy settings
Generic policy
Policy assigned in the
System Tree
A
Prevents internet access from all systems to
which the policy is assigned.
System-based
Policy assignment rule
B
Allows internet access from systems with the
tag "IsLaptop."
User-based
Policy assignment rule
C
Allows unrestricted internet access to all
users in the Admin user group from all
systems.
Scenario: Using multi-slot policies to control Internet access
In your System Tree, there is a group named "Engineering" which consists of systems tagged with
either "IsServer" or "IsLaptop." In the System Tree, policy A is assigned to all systems in this group.
Assigning policy B to any location in the System Tree above the Engineering group using a policy
assignment rule overrides the settings of policy A, and allows systems tagged with "IsLaptop" to
access the internet. Assigning policy C to any group in the System Tree above the Engineering group
allows users in the Admin user group to access the internet from all systems, including those in the
Engineering group tagged with "IsServer."
Excluding Active Directory objects from aggregated policies.
Because rules that consist of multi-slot policies are applied to assigned systems without regard to
priority, you might need to prevent policy setting aggregation in some instances. You can prevent
aggregation of user-based multi-slot policy settings across multiple policy assignment rules by
excluding a user (or other Active Directory objects such as a group or organizational unit) when
creating the rule. For more information on the multi-slot policies that can be used in policy assignment
rules, refer to the product documentation for the managed product you are using.
About user-based policy assignments
User-based policy assignment rules give you the ability to create user specific policy assignments.
These assignments are enforced at the target system when a user logs on.
Using policies to manage products and systems
How policy assignment rules work
15
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
167