To access material, start machines and answer questions login.
Across three rooms, Module 4 has named nineteen controls, each closing a different way a compromise outlives the moment it happened: five for code that keeps running (ASI05), seven for memory that keeps being read (ASI06) and seven for messages that keep being trusted (ASI07). None of them were ever switched on. This room puts them side by side against the estate for the first time, and switches on the ones a live incident actually reaches.
The Scenario
This is the TryTrainMe estate you already know: eight agents, with you in the security engineer's seat, as in every room of this module. Nothing new happens here that hasn't already happened somewhere in the three rooms before this one, and you have been reading this estate's logs since the first of them.

The estate hasn't changed. This room puts a lock on every link.
Learning Objectives
- Name, for each of the three prior rooms' attacks, the specific control(s) that would have closed it.
- Distinguish a control that stays on throughout an estate's normal operation from one that only becomes relevant during remediation.
- Trace a composite incident that spans more than one attack surface, and identify every layer where it could have been stopped.
- Select the correct subset of controls for a given scenario, rather than reciting an entire catalogue.
- Classify any control by the moment it acts: write time, trust time, action time, structural or after the fact.
- Read a
guardrailevent in an agent log as the reason a step was blocked, and tell an enforced control from one markedNOT ENFORCED.
Prerequisites
This room assumes you've completed all three walkthroughs it integrates. These are hard prerequisites, not background reading: Tasks 2 to 4 reuse their exact controls without re-explaining the attacks behind them.
- ASI05: Unexpected Code Execution: its five named controls are reused directly in Task 2.
- ASI06: Memory & Context Poisoning: its seven named controls are reused directly in Task 3.
- ASI07: Insecure Inter-Agent Communication: its seven named controls are reused directly in Task 4.
It's time to switch on everything you've already named.
Ready to learn Cyber Security?
The Defending the Persistence Layer room is only available for Premium or Max subscribers. Signup now to access more than 500 free rooms and learn cyber security through a fun, interactive learning environment.
Already have an account? Log in
