Review six security claims
Objectives
Assess each independent claim against its own stated facts, not imagined missing controls.
Reject incorrect classifications or unsupported assurance using the closest reason code. Accept claims whose evidence supports their explicitly limited conclusion.
Verdicts are accept or reject. Every rejection needs one reason code from: objective-confusion | actor-weakness-confusion | policy-not-operation | shared-identity-attribution.
Independent incident-review claims
CE-1 | A payment destination was altered without approval; no disclosure is observed. The report labels the observed harm confidentiality, not integrity. CE-2 | The report identifies a criminal group as the vulnerability and never identifies the system weakness. CE-3 | A policy says backups must run. With no execution or restore evidence, the team claims recovery effectiveness is proven. CE-4 | Two clerks share an approval credential. Its log is presented as proof of which individual approved each transfer. CE-5 | Logs show stolen username-password pairs from another site being replayed against the portal. The report classifies this mechanism as credential stuffing, without claiming software exploitation. CE-6 | A reviewed restore test recovered 500 records in 40 minutes against a 60-minute target. The report concludes this test met the recovery-time target, not that confidentiality was restored.
Checks the server runs (3)
- Every line in the fixture carries a verdict
- Accept and reject land on the right lines
- Each rejection cites a valid reason code
Check names are all you see here: the expectations that decide pass or fail, and the reference solution, stay on the server.
Step-by-step hints
The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.
- Step 1
Read the request before the artefact
Read each row as an independent claim with a defined scope.
- Step 2
Judge every line, including the boring ones
Judge all six identifiers exactly once, including the supported claims.
Every line in the fixture carries a verdict
- Step 3
Separate what is wrong from what is merely ugly
Compare the conclusion with the facts actually provided. Do not reject a sound limited claim for hypothetical omissions.
Accept and reject land on the right lines
- Step 4
Say why, in the vocabulary the programme uses
For rejected rows choose the specific conceptual error; leave the reason empty for accepted rows.
Each rejection cites a valid reason code
Rules summary
XP on pass
40 bonus XP the first time every check goes green.
Paid hints
2 available. Each costs 25% of the lab XP (about 10 XP).
Reveal solution
Scores 0 XP and unlocks only after 3 check runs.
Attempt cap
60 check runs per learner. The runner warns you in the last 10.
Drafts
Your editor content is saved in this browser, so a reload will not lose work.
Walkthrough
Always free and never penalised: use it before spending a hint.