Enum AuditChainBreak
- Namespace
- Excalibur.AuditLogging
- Assembly
- Excalibur.AuditLogging.Abstractions.dll
What kind of break a chain verification found, when it found one.
public enum AuditChainBreak
Fields
ContentAltered = 2The record's MAC does not match its live contents, while its stored claim still names the record that actually precedes it — so the record's contents were rewritten in place.
None = 0No break; the chain verified.
PredecessorMismatch = 3The record's MAC does not match, and its stored claim names a predecessor that is not the record now preceding it — so a record has been removed, inserted, or reordered.
StoredLinkageAltered = 4The record's MAC verifies, but its stored claim about its predecessor disagrees with the record that actually precedes it — so the stored linkage value alone was altered.
SuccessorLinkBroken = 5Every record in range verified, but the record following the range does not chain to the range's last record. Its principal cause is removal of records from the end of the range: the survivors still chain to one another and to the anchor, so nothing inside the range mentions the removed suffix, and only the record beyond it still carries the tag that named what was there. It also reports the successor itself having been altered, which is likewise a break the reader must act on.
UntaggedRecord = 1The record carries no integrity tag at all, so nothing about it can be established.
Remarks
The distinction is not cosmetic. A rewritten record, a removed one, and an altered linkage value call for different responses from whoever reads the report, and a bare "verification failed" leaves them unable to tell which happened.