
The two Host Intrusion Prevention policies without a My Default policy, IPS Rules and Trusted
Applications, are called multiple-instance policies because you can assign multiple policy instances
under a single policy. The policy instances are automatically combined into one effective policy.
Figure 1: IPS Rules policy with three policy instances
How policies are applied
Policies are applied to any System Tree group or system by inheritance or assignment.
Inheritance
determines whether the policy settings for any system are taken from its parent.
By default, inheritance is enabled throughout the System Tree. You can break inheritance by
direct policy
assignment
. Host Intrusion Prevention, as managed by ePolicy Orchestrator, enables
you to create policies and assign them without regard to inheritance. When you break this
inheritance by assigning a new policy, all groups and systems below inherit the new policy.
Policy ownership
Each policy is required to have an assigned owner. Ownership ensures that no one can modify
the policy other than the global administrator, the creator of the policy, or the person associated
as the policy owner. Any administrator can use any policy that exists in the catalog, but only
the creator, owner, or global administrator can modify it.
If you assign a policy that you do not own to System Tree groups that you administer, and the
owner of the policy modifies it, all systems to which this policy is assigned receive these
modifications.
TIP: To use and control a policy owned by a different administrator, duplicate the policy, then
assign the duplicate policy.
Policy tracking and tuning
The deployment and management of Host Intrusion Prevention clients are handled from ePolicy
Orchestrator. In the ePO System Tree you can group systems hierarchically by attributes. For
example, you might group a first level by geographic location and a second level by operating
system platform or IP address. McAfee recommends grouping systems by Host Intrusion
Prevention configuration criteria, including system type (server or desktop), use of major
applications (web, database, or mail server), and strategic locations (DMZ or intranet). You can
place systems that fit a common usage profile into a common group on the System Tree. In
fact, you might name a group after its usage profile, for example,
Web Servers
.
With computers grouped in the System Tree according to type, function, or geographic location,
you can easily divide administrative functions along the same lines. With Host Intrusion
Introducing Host Intrusion Prevention 7.0
Policy tracking and tuning
McAfee Host Intrusion Prevention 7.0 Product Guide for use with ePolicy Orchestrator 4.010
Comentarios a estos manuales