Enum ControlOutcome
- Namespace
- Excalibur.Compliance
- Assembly
- Excalibur.Compliance.Abstractions.dll
What a control validation established about a control.
public enum ControlOutcome
Fields
Deficient = 0The control was examined and found not to be operating: a violation was detected, or the mechanism it depends on is absent.
Effective = 2The control was examined and found to be operating.
NotVerified = 1The control was NOT examined, so nothing is established either way. This is a statement about the validation, not about the control: it is neither a pass nor a finding, and an auditor reading it should expect to obtain assurance by some other means rather than to investigate a defect.
Remarks
Three states, because there are three facts. A boolean verdict can say that a control is operating and that it is not; it has nowhere to put "nobody looked". A validator that could not examine a control — the mechanism is not observable from inside this framework, the check threw, or nothing was in scope — is then forced to pick one of the two, and both choices are false statements to an external auditor. Reporting it as effective claims an assurance nobody established. Reporting it as deficient claims a finding nobody made, and sends an auditor looking for a defect that does not exist.
The ordering is the contract. Deficient is worse than NotVerified and both are worse than Effective: a proven deficiency is knowledge, and an open question must never read as better than a clean examination nor worse than a confirmed break. Anything ranking, aggregating or thresholding these values relies on that order.
An unverified control is not a passing control. A criterion containing one cannot be reported as met, because nothing established that it is. That rule is applied to the worst control in a criterion rather than to their mean — an average lets an effective control pay for an unexamined one, which is precisely how an unverified control comes to sit inside a passing report.