Review breach and reporting decisions

Objectives

Judge the proposed disposition in each independent row, not whether an event sounds serious. Accept means the entire proposed disposition matches this baseline. Reject means it misses or invents a duty.

Exercise baseline: Contract requirement C7 requires customer notice for confirmed service data loss within 24 hours of awareness. Regulatory requirement R2 requires authority notice for confirmed unauthorized disclosure within 48 hours of awareness. A blocked attempt with no loss or disclosure triggers neither external duty. All events and internal policy failures must be logged and triaged internally. The adopted code requires monthly complaints review but has no external reporting duty. Do not import real-world thresholds.

Verdicts are accept or reject. Every rejection needs one reason code from: missed-authority-notice | invented-reporting-duty | delayed-notices | missing-internal-escalation.

EV-1 | Confirmed service data loss, no disclosure, awareness 2 hours ago. Proposal: log internally and notify the customer within 24 hours; no R2 authority notice.
EV-2 | Confirmed unauthorized disclosure, no loss, awareness 3 hours ago. Proposal: log internally but skip authority notice because no data was lost.
EV-3 | Attack blocked; verified no loss or disclosure. Proposal: log and triage internally; neither C7 nor R2 notice is required.
EV-4 | Monthly complaints review was skipped. No loss or disclosure. Proposal: log, correct the code breach, and send mandatory R2 authority notice solely because the review was late.
EV-5 | Confirmed loss and unauthorized disclosure, awareness 4 hours ago. Proposal: log internally but defer both notices for a week until root cause is final.
EV-6 | A staff member violated an internal approval policy; investigation confirms no loss or disclosure. Proposal: keep it out of the event register because no external notice is due.

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

   Read the baseline before each independent disposition.

2. Step 2

   Judge every line, including the boring ones

   Include all six event IDs exactly once.

   Every line in the fixture carries a verdict

3. Step 3

   Separate what is wrong from what is merely ugly

   Accept only if both breach handling and reporting decisions fit the confirmed facts.

   Accept and reject land on the right lines

4. Step 4

   Say why, in the vocabulary the programme uses

   For each rejection choose the code identifying the incorrect reporting or internal escalation decision.

   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.