Table of Contents
Advertisement
Managing Audit Waivers
Types of waivers
Exception waivers
Exception waivers potentially affect the audit scores of selected systems by forcing the audit
result of a benchmark rule to have a status of pass. The primary use of an exception waiver is
to force audit rules to pass.
Exception waivers have these characteristics:
They apply to selected systems and groups in the System Tree.
They require you to select an audit benchmark and a rule contained in the benchmark.
They evaluate every rule during an audit, but force the selected rule(s) to have a status of
pass.
They can be backdated. Scores for results collected during the backdate timeframe are
recalculated.
For example, McAfee Policy Auditor audits a system with a benchmark that contains five rules.
Four rules pass and one fails, resulting in a score of 80%. If the rule that failed is granted an
exception waiver, all five rules are considered to have passed and the score is 100%.
Exemption waivers
Exemption waivers prevent selected systems from being audited.
Exemption waivers have these characteristics:
They apply to selected systems and groups in the System Tree.
They do not require you to select a benchmark and a rule.
They cannot be backdated.
They do not audit the selected systems when the waiver is in effect.
They do not include selected systems in the audit results.
For example, McAfee Policy Auditor audits a system with a benchmark that contains five rules.
Four rules pass and one fails, resulting in a score of 80%. If the system is granted an exemption
waiver, it is not audited and does not appear in the audit results.
Suppression waivers
Suppression waivers potentially alter the audit scores of selected systems by excluding the
audit result of a benchmark rule. The primary use of a suppression waiver is to hide the audit
results.
Suppression waivers have these characteristics:
They apply to selected systems and groups in the System Tree
They require you to select an audit benchmark and a rule contained in the benchmark.
They evaluate every rule during an audit, but do not include the rule result when calculating
the score.
They can be backdated. Scores for results collected during the backdate timeframe are
recalculated.
For example, McAfee Policy Auditor audits a system with a benchmark that contains five rules.
Four rules pass and one fails, resulting in a score of 80%. If the rule that failed is granted a
suppression waiver, the rule results are excluded and the score is 100%.
McAfee Policy Auditor 6.0 software Product Guide for ePolicy Orchestrator 4.6
53
Advertisement
Table of Contents
