grceng.academy
Review lab 40 bonus XP

Review the exercise findings

Start labRead the room

Objectives

The facilitator has drafted six findings tickets from this quarter's tabletop and wants them filed 'as-is, so we can close out the exercise admin'.

Filed as-is, half of them will be next year's findings. Accept the tickets that can actually ship; reject the ones that encode a future repetition.

Verdicts are accept or reject. Every rejection needs one reason code from: no-owner | no-due-date | no-ship-target | vague-finding.

draft findings tickets

F-1  "Pager did not fire for SEV2" | owner: ir-team | due: 2026-10-15 | ships: alert rule fix
F-2  "Runbook rollback step wrong" | owner: platform-eng | due: 2026-10-01 | ships: runbook edit + control update
F-3  "The organisation should consider improving escalation" | owner: (none) | due: (none) | ships: discussion
F-4  "Vendor notice arrived in unread inbox" | owner: grc-eng | due: (none) | ships: monitored channel
F-5  "Document lessons learned from the exercise" | owner: facilitator | due: 2026-10-01 | ships: a document
F-6  "Improve security posture" | owner: security-team | due: 2026-12-31 | ships: "improvement"

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.

  1. Step 1

    Read the request before the artefact

    The facilitator's goal is administrative closure. Yours is that every finding which leaves the room can become a change. Those are different definitions of done.

  2. Step 2

    Judge every line, including the boring ones

    Six tickets, six verdicts. Anything you accept enters the tracker and represents the exercise's entire value.

    Every line in the fixture carries a verdict

  3. Step 3

    Separate what is wrong from what is merely ugly

    Check the three fields in order: is there a named owner, is there a due date, does 'done' mean a control, an alert or a runbook changed?

    Then read the finding itself: could a stranger act on it without asking what it means?

    Accept and reject land on the right lines

  4. Step 4

    Say why, in the vocabulary the programme uses

    Cite the failing field. The fix for no-owner is assignment; the fix for no-ship-target is defining done; they are not interchangeable.

    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.