Operation Broken Seal

A trusted build has become a delivery mechanism. Follow its trail, protect the fleet and earn the next release.

3LEVELS

5MISSIONS

125 MINEST. DURATION

Explore the operation

YOUR NEXT INSIGNIA

THE OPERATION

Every decision moves the story.

0 / 5 required missions passed

The build is green. The signature is valid. The update is already outside. Follow a supply-chain incident from a moved tag to the release you can defend.

What you’ll practise and what’s included

Five substantial software supply-chain investigations across three progressive levels, about 125 minutes in total. Join Kestrel Dispatch's release incident desk: trace a moved dependency tag, contain a reused build runner, challenge a signed bundle, scope a customer recall and earn a conditional return to service. Investigate realistic but inert logs, manifests, policy records and service receipts; choose between operationally defensible routes and test their consequences. A provenance variant changes which release check fails, so replay requires fresh evidence. Each mission has its own badge, animated briefing and saved decision debrief; the final dossier includes a reusable supply-chain incident worksheet. Level 2 unlocks after both Level 1 missions pass; Level 3 requires both Level 2 missions. Basic familiarity with builds and access control helps; terminology and required policy are supplied. All work happens in the HTML5 player: no coding, live malware, external accounts or terminal required. Included in the existing €20/month Missions subscription and eligible Teams access. This is guided decision practice, not a hands-on exploit lab or certification. Each chapter supplies a consistent checkpoint rather than dynamically importing earlier branch outcomes. Estimates are not timers.

LEVEL 1

Trace the intrusion

BS-0122 MIN

The Tag That Moved

08:25 UTC. Kestrel's warehouse-dispatch agent was updated this morning. A maintainer reports that gate-task's familiar v3 tag changed without authorisation. Release lead Leena asks which of your jobs actually ran the suspect revision. You may preserve scoped records and freeze the pre-approved build intake; do not replay suspect code, delete logs or accuse a maintainer. The release feed is separately held by the commander while you investigate. Each chapter uses a supplied incident checkpoint; your earlier choices are retained in their own debriefs, not imported as simulated facts. All records are synthetic. There is no enforced countdown.

22 min · Practice & assessmentBegin case

BS-0225 MIN

The Runner That Remembered

08:40 UTC. You lead the build-platform response at Kestrel. The supplied checkpoint confirms R901 executed GT-suspect on persistent runner K-17 and published B42 before the feed hold. The intake is now frozen. Platform owner Arun needs a credential and rebuild plan that does not trust the same host twice. You may isolate K-17, preserve scoped state, invoke approved identity controls and request safe denial probes; no new production build or broad employee investigation is authorised. Each chapter uses a supplied incident checkpoint; your earlier choices are retained in their own debriefs, not imported as simulated facts. All records are synthetic. There is no enforced countdown.

25 min · Practice & assessmentBegin case

LEVEL 2

Protect the people downstream

BS-03LOCKED

The Signature Was Not Enough

09:15 UTC. Kestrel's release desk has B42, a cryptographically valid attestation envelope and a worried product owner. The supplied checkpoint holds the customer feed, retires K-17 and keeps the historical signing review open. You are the artifact-assurance lead. Establish whether the attestation actually authorises these bytes, then recommend a bundle decision. You may inspect preserved metadata and request supplied isolated analyses; you cannot publish, run suspect code on a live host or change the organisation's trust policy to make a check pass. Each chapter uses a supplied incident checkpoint; your earlier choices are retained in their own debriefs, not imported as simulated facts. All records are synthetic. There is no enforced countdown.

27 min · Practice & assessment

Complete the previous level to unlock.

BS-04LOCKED

The Update Already Shipped

09:40 UTC. Kestrel's held B42 update has already reached customers. You are the downstream-response coordinator. The supplied checkpoint keeps B42 quarantined, the build runner retired and a new candidate unapproved. Customer operations lead Noor needs a scoped recall that protects dispatch continuity. You may invoke either pre-approved containment profile, prepare the approved technical notice and request site receipts. No untested bulk rollback, customer-wide compromise claim or legal notification decision is authorised. Each chapter uses a supplied incident checkpoint; your earlier choices are retained in their own debriefs, not imported as simulated facts. All records are synthetic. There is no enforced countdown.

24 min · Practice & assessment

Complete the previous level to unlock.

LEVEL 3

Earn the next release

BS-05LOCKED

The Release We Can Defend

10:30 UTC. Kestrel has a new candidate, B43, and a release board that wants dispatch service back. The supplied checkpoint keeps B42 held, K-17 retired, and historical credential/customer reviews open. A fresh K-18 environment has been accepted for isolated testing only. You are the release-assurance chair. Challenge the candidate, test rollback compatibility and recommend a constrained return or continued hold. You cannot authorise production publication from this player, waive privacy review or pretend earlier branch choices are simulated here. Each chapter uses a supplied incident checkpoint; your earlier choices are retained in their own debriefs, not imported as simulated facts. All records are synthetic. There is no enforced countdown.

27 min · Practice & assessment

Complete the previous level to unlock.

Paid campaign · €20/month including VAT with Solo, or included with eligible TIL Teams. Compare memberships →Sign in before starting to save your advancement.