Review the readiness claims

Objectives

Two weeks before the Type II window closes, your programme lead circulates six controls marked "fully automated, evidence continuous".

Accept the claims that would survive an auditor walkthrough. Reject the ones that still contain a human step, produce evidence nobody can rely on, or cover only part of the period.

Verdicts are accept or reject. Every rejection needs one reason code from: manual-step | evidence-mutable | partial-period.

S-1  Leaver removal: daily job diffs HRIS terminations against Okta; failures ticketed; run log immutable, whole period.
S-2  Change approval: pipeline blocks unapproved merges; evidence is a CSV the release manager assembles each month by hand.
S-3  Backup restore: automated monthly restore with recorded outcome; log write-once; whole period.
S-4  Vulnerability SLAs: scanner runs nightly; evidence exported to a shared drive anyone in engineering can edit.
S-5  Access review: automated collection started in month 10 of a 12-month window.
S-6  Encryption: config check on every deploy; results appended to an immutable store; whole period.

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.

1. Step 1

   Read the request before the artefact

   A readiness claim has three parts: the control runs without a person, the evidence is tamper-evident, and both hold for the whole period. Grade each part separately.

2. Step 2

   Judge every line, including the boring ones

   All six claims get a verdict. Three are genuinely ready; identifying them is what tells the programme lead where the remaining two weeks should go.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Trace each claim from trigger to stored artefact and mark the first point a human could change the outcome or the record.

   Then check coverage against the window. A control that started collecting late has evidence for part of the period and nothing for the rest.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   A hand-assembled export, an editable evidence store and a late start are three different remediations: one is a pipeline change, one is a storage change, one cannot be fixed at all before the window closes.

   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.