Filters

Purpose

Filters serve as a mechanism for ensuring that the prerequisites for one or more Control Points have been met prior to executing the Control Points on that host.

Example

Assume that you have a group of ten Control Points designed to ensure that Apache is configured properly. What do you do if Apache isn't installed? Running these Control Points against a host which does not have Apache installed is both pointless and misleading. How would you count these ten Control Points? Are they Ok, Not Ok, or something else?

Usage

Filters can stand on their own as a prerequisite and are not tied to a set of Control Points until they are added to a Policy. This means that you create the Filters separately from the Control Points and inside of the Policy, you add the Control Points to the Filters. To build a Filter:

  1. Set a name for your Filter that is descriptive of its function.
  2. Build the Rule(s) which identify the prerequisites for running the Control Points you will run if this Filter evaluates to a boolean "True".
  3. If you have only one Rule in your Filter:
    • Add a "FilterMembers" RuleKey to that Rule
  4. If you have more than one Rule in your Filter:
    • Find the List Rule and add a "FilterMembers" RuleKey to that Rule

Hints

Hint 1: Generally speaking, each Filter should consist of one of the following:

  • A single Rule -- or --
  • A Rule with the RuleType of either RollupList or RuleExpression which references all of the other Rules in the Filter.

Hint 2: Rules not referenced by another Rule in the Filter will not be executed.

Hint 3: You must designate a "top-level" Rule in the Filter by adding an empty RuleKey named FilterMembers. If you forget, the Filter will not execute, and neither will any Control Points you add to it in a Policy.

© 2011-2019 Moon River Software Inc. All rights reserved.
@AuditShark stay in touch