A security scan flagged the deploy account's private SSH key as readable beyond its owner on the shared deploy host.
Stage 1 of 4 in Breach Response.
The nightly permissions scan flagged /home/deploy/.ssh on the shared deploy host after yesterday's home directory sync, and security has opened a containment ticket.
The deploy account still needs this key for the 10:00 release, so deleting it or disabling the account is off the table.
Rotation will happen separately, out of band, once local access is contained.
The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.
The alert fires and the clock starts. Read the page and the briefing.
Work in a simulated shell with realistic output: logs, configs, services.
Change the system the way you would in production. Hints are there if you get stuck.
Automated checks verify the recovery, then the debrief explains what happened.
Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.