Recover in Stages
Part of the Stopping the Spread section of Coddy's Cybersecurity journey. Lesson 17 of 20.
Containment gives you time to clean up. Keep a computer isolated while you preserve evidence and remove the unwanted process, file and startup entry.
Once cleanup is complete, return that computer to service and verify its approved work. Then repeat for the next affected computer. This makes it easier to spot which recovery step caused a problem.
For example, a cleaned practice computer can return to the network:
seclab host practice-laptop reconnectYou should see:
practice-laptop: reconnect.Its old unwanted route should remain blocked:
seclab probe demo-uploadYou should see:
practice-laptop -> parcel-cache:443
Blocked: process_stoppedHere the source process is stopped. The block now comes from cleanup, rather than isolation. That distinction matters when deciding whether recovery is complete.
Challenge
EasyTicket from Sam, IT lead
Sam has approved recovery of returns-pc and stock-relay. Preserve evidence from both while their unwanted processes still run. Clean each process, its file and its startup, then reconnect both computers. Restore the returns backup, keep both outside routes blocked and leave checkout working.
Try it yourself
All lessons in Stopping the Spread
1Trace the Connection
Follow a ConnectionTest a RouteFollow the Whole OrderInside the CompanyOrders Without Payment4Recover and Verify
Prove the BlockRecover in StagesReport the ImpactReview the BoundaryLumen Stays Open2Close the Unwanted Route
Destination RulesRule OrderOutbound RulesAllow the Needed WorkTwo Unwanted Routes3Contain More Than One Computer
Isolate a ComputerThe Exposed PasswordFollow the SpreadKeep Customers WorkingTwo Active Computers