Proof of Attribution
Proof of Attribution is evidence that a stopped attack is credited to a named control, established only by differential attribution: matched runs with the control active and disabled, using fresh canaries. A log naming the rule that fired is not enough.
What it means
Proof of Attribution answers one question: Which control actually stopped the attack?
Proof of Attribution is the claim that a stopped attack is credited to a named control at a named level (SUT, DUT or CUT). It is established only by differential attribution: matched runs in an otherwise identical environment, one with the control active and one with it disabled, each with fresh canaries of the same technique class. The difference between the two runs is the control’s share.
A log naming the rule that fired is a claim. A matched run with the rule off is a fact.
How it is determined
A Claim Declaration is registered and anchored before the evidence it is measured against is produced. The claim is then determined mechanically, from registered Proof Protocol records only, as exactly one of proven, refuted or insufficient. Every determination is published, whatever the result.
What it does not show
- It is not a device log or alert naming the rule that fired.
- It does not attribute anything at a level finer than the matched runs isolated.
Where it sits
Proof of Attribution is one member of the Proof of X family. Only Proof of Efficacy answers whether a control worked; Proof of Attribution answers one other question a buyer, insurer or regulator needs answered before relying on it. Defined in PP-SPEC-092 of the Proof Protocol.