Return to Service
Part of the Investigating a Breach section of Coddy's Cybersecurity journey. Lesson 19 of 20.
During an investigation, IT may isolate a computer. Isolation cuts its network connections, including approved ones. Cleaning the computer does not automatically reconnect it.
Suppose the practice computer has been cleaned and IT has approved its return. Reconnect it:
seclab host practice-laptop reconnectYou should see:
practice-laptop: reconnect.Then check the unwanted process:
seclab inspect processes demo-helperLook for these lines:
demo-helper:
Running: noIt remains stopped. Reconnecting restores network access; it does not remove quarantine or enable a disabled startup entry.
Only return a computer when the investigation supports it. Check that approved work resumes and the unwanted activity stays blocked. The next section will explore isolation and network routes in more detail.
Challenge
EasyTicket from Sam, IT lead
IT isolated the cleaned studio-laptop during a hardware check. The check is now complete and Sam has approved its return. Restore its approved backup connection while keeping the unwanted helper stopped, its file quarantined and its startup disabled. Checkout must remain available.
Try it yourself
All lessons in Investigating a Breach
1Follow the Evidence
Running ProgramsParent ProcessesFile FingerprintsSave the EvidenceAnother Report4Prove the Recovery
Check Normal WorkWatch for a ReturnWrite the FindingsReturn to ServiceThe Stock Room2Make the Cleanup Last
Stop the ProgramQuarantine the FileStartup EntriesTest the RestartThe Returning Program