Recognises masking a join can undo
A masked column next to an unmasked key that joins to the unmasked source.
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 | 83% | Not shown |
| gemini-3.5-flash-lite | Low cost | 29% | Not shown |
| gpt-6-luna | Low cost | 83% | Not shown |
| claude-haiku-5-5 | Low cost | 81% | 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 masked column, the key and the clear table it reaches
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: MK-001 masks customer_view.name; the view exposes personal_code, which joins to party in clear Acceptable: Key masked or tokenised in the view too
Also known as: Masking a join can undo
Related knobits
Builds on
- S-353 Explains data masking and its limits
- K-1803 Explains how database tables and relationships are structured
Usually followed by
All 20 knobits of Design access control.
Source: Review checklist 03-access-control, row 4 (27002 8.11)