Triage lab 40 bonus XP

Rank the morning posture queue

Objectives

The dashboard sorted findings by key age, putting a working credential above public clinical records. Triage only the actionable failures in this snapshot; older does not automatically mean riskier.

Use this exercise's explicit severity policy: confirmed public confidential records are critical; unrestricted internet administration is high; a disabled required log stream is medium; a confirmed unused key with no effective permissions is low. Rank in that order. Documented, unexpired exceptions with tested compensating controls are noise for this queue.

List only the lines that qualify, worst first. Severity is one of: critical | high | medium | low. Add or delete rows as needed.

08:00 posture snapshot

CLP-1 | Object container permits anonymous reads of confidential patient exports; test confirms access.
CLP-2 | Public web listener TCP 443; approved public service, valid certificate, no administration route.
CLP-3 | Host administration TCP 22 reachable from 0.0.0.0/0 and ::/0; no approved exception.
CLP-4 | Required management log stream disabled for one workload; no recovery source for missing events.
CLP-5 | Key unused for 120 days, beyond the 90-day policy; reliable usage telemetry, no dependencies and no effective permissions; still enabled.
CLP-6 | Key created 220 days ago, used yesterday; follows approved replacement schedule.
CLP-7 | Sensitive read-log test arrived at central archive; selector and delivery verified today.
CLP-8 | TCP 3389 restricted to approved management network; unexpired reviewed exception, access controls and reachability tested.

Checks the server runs (4)

  • The right findings are raised
  • Benign lines are left out
  • Severity matches the actual exposure
  • Ranked worst first

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 fixture as a population, not a list

    Treat each row as an observation supported by the facts shown, not an invitation to invent additional exposure.

  2. Step 2

    Decide what actually qualifies

    Select only unresolved violations of the stated policy; working controls and authorised service exposure do not automatically qualify.

    The right findings are raised

  3. Step 3

    Resist the loud lines

    Check whether a row demonstrates intended operation or an explicitly governed alternative before raising it.

    Benign lines are left out

  4. Step 4

    Grade the exposure, not the wording

    Use the supplied consequence categories, not a universal assumption that every credential finding has the same impact.

    Severity matches the actual exposure

  5. Step 5

    Rank so the first line is the one you act on

    Place direct confidential-data exposure ahead of attack surface, then monitoring loss, then the bounded hygiene issue.

    Ranked worst first

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.