CONTROL VALIDATION
The control is declared. How does it respond to a test?
We test a declared control on an agreed isolated copy. We apply a supported change and observe whether the control detects it or blocks the process, according to its expected behavior.
A test for your tests, and for the controls that claim to protect you.
The current implementation mutates an isolated copy and observes whether the declared control reacts. It is not a general testing method, not externally validated, and not demonstrated on customer production systems.
How the check runs
- 01
The technical contact confirms the control to observe.
- 02
The agreed isolated copy is fixed, before the change.
- 03
A controlled change alters only that copy.
- 04
You observe whether the declared control reacts, and the limits are recorded.
Two implemented mutation operators.
M1 — Declared critical file
M2 — Policy changed without updating its digest
Example
In the demonstrated self-assessment profile, a mutation removes a required artifact or alters a policy digest in a controlled environment. Quvant observes whether the declared control detects the deviation. This is not a customer-production run.
Declared control
Change in the test copy
Behavior to observe
Limit of the result
What the customer receives
- The declared control
- The applied mutation
- The observed behaviour
- Test evidence
- Verification limits
- A suggested next step