Proof of Control
Proof of Control is evidence that a control fired, such as a log entry showing it triggered. It shows the control acted, not that the outcome was achieved. It is the baseline tier beneath Proof of Efficacy.
What it means
Proof of Control is a deliberately low, permissive bar: evidence that a control did something when it was supposed to. A log entry, alert or event record showing the control triggered is enough.
It answers the question: did the control act?
Where it sits
Proof of Control sits above Verification of Control (the control is in place) and beneath Proof of Efficacy (the required outcome was produced). It is the baseline tier: necessary, easy to meet, and not sufficient.
See the full ladder: Verification vs. Validation vs. Proof.
What it does not show
A control can fire and still fail. It can alert on the first stage of an attack and miss the second, block one request and pass the next, or log a detection after the damage is done. Proof of Control records the action, not the result.
Example
An endpoint product logs that it blocked a malicious process. That log entry is Proof of Control. Proof of Efficacy asks the next question: did the attack fail, under realistic conditions, to the standard the buyer needs?