Table of Contents

Class ControlValidationResult

Namespace
Excalibur.Compliance
Assembly
Excalibur.Compliance.Abstractions.dll

Result of control validation.

public record ControlValidationResult : IEquatable<ControlValidationResult>
Inheritance
ControlValidationResult
Implements
Inherited Members

Properties

ConfigurationIssues

Configuration issues found.

public IReadOnlyList<string> ConfigurationIssues { get; init; }

Property Value

IReadOnlyList<string>

ControlId

Control identifier.

public required string ControlId { get; init; }

Property Value

string

EffectivenessScore

What this validation established about the control's effectiveness, as one of the reportable bands.

public required ControlEffectiveness EffectivenessScore { get; init; }

Property Value

ControlEffectiveness

Remarks

Finer-grained than Outcome, which it determines: the band separates a control whose mechanism is absent from one that was examined and found broken, which Deficient covers jointly. Only a declared band may be supplied — a value outside ControlEffectiveness is rejected at construction, because the ordering the report relies on is defined only over the declared members.

Exceptions

ArgumentOutOfRangeException

The supplied value is not a declared ControlEffectiveness member.

Evidence

Evidence collected during validation.

public IReadOnlyList<EvidenceItem> Evidence { get; init; }

Property Value

IReadOnlyList<EvidenceItem>

IsConfigured

Whether the control is properly configured.

public required bool IsConfigured { get; init; }

Property Value

bool

Outcome

What this validation established about the control.

public ControlOutcome Outcome { get; }

Property Value

ControlOutcome

Remarks

Derived from EffectivenessScore, never stated separately. A result whose verdict contradicts its own band is not rejected here — it cannot be written. The band is the finer fact and it already determines the verdict, so offering a second place to say so would only offer a second place to say something different.

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 is then forced to pick one of the two, and both choices are false statements to an external auditor. See ControlOutcome for why the distinction is load-bearing.

ValidatedAt

Validation timestamp.

public DateTimeOffset ValidatedAt { get; init; }

Property Value

DateTimeOffset