Control statuses
How an individual control is qualified, and how that rolls up to a test's level.
This page is the condensed technical reference for the control statuses defined by RS-RVP-01. For a narrative explanation of why this distinction matters, see Result statuses.
Control statuses
| Status | Meaning |
|---|---|
PASS |
The expected condition is demonstrated. |
FAIL |
The control ran correctly and demonstrates that the expected condition is not satisfied. |
ERROR |
The control could not correctly determine the expected state (timeout, test infrastructure failure, unavailable dependency, execution exception, inconsistent environment...). |
NOT_APPLICABLE |
The control does not apply, and this status is explicitly allowed by the protocol. |
Roll-up to a level's status
required = PASS
→ contributes positively to the level
required = FAIL
→ level = FAIL
required = ERROR
→ level = INDETERMINATE
required = NOT_APPLICABLE
→ allowed only if the protocol explicitly provides for it
A level is only positively obtained if 100% of its mandatory controls are PASS, subject to
explicitly allowed NOT_APPLICABLE exceptions. A level's status belongs to the set PASS,
FAIL, INDETERMINATE, NOT_EVALUATED — never an average or an approximation of the
controls that make it up.
Example
L1 PASS
L2 PASS
L3 PASS
L4 INDETERMINATE
L5 NOT_EVALUATED
Highest demonstrated level: L3
This page is a quick reference. The full vocabulary, its implications, and the principle that an ERROR is never treated as equivalent to a success are detailed in Result statuses.