Recognises a control unable to satisfy its requirement
The control as described cannot meet the requirement as worded.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 89% | Not shown |
| gemini-3.5-flash-lite | Low cost | 9% | Not shown |
| gpt-6-luna | Low cost | 10% | Not shown |
| claude-haiku-5-5 | Low cost | 90% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The control, the requirement and the gap
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: CT-003 "CVV purged nightly" for RQ-003 "SAD not retained after authorisation" Acceptable: CVV never written to storage
Also known as: Control unable to satisfy its requirement
Related knobits
Builds on
All 17 knobits of Register regulatory security requirements.
Source: Review checklist 01-regulatory-requirements, row 9 (PCI 3.3.1)