Test the Restart
Part of the Investigating a Breach section of Coddy's Cybersecurity journey. Lesson 9 of 20.
A cleanup can look finished until the computer restarts. Test that the unwanted program stays stopped and the approved programs return.
Suppose the practice helper has already been stopped, quarantined and removed from startup. Restart its computer:
seclab host practice-laptop restartYou should see:
practice-laptop: restart.Check the helper:
seclab inspect processes demo-helperLook for these lines:
demo-helper:
Running: noIt stays stopped. To watch another interval without making a new change, use wait:
seclab waitYou should see:
Watching the next interval.Then read the connection records:
seclab inspect connections demo-uploadLook for these lines:
demo-upload:
Allowed: no
Reason: process_stoppedThe route is blocked because the source process is stopped. A restart is useful evidence that cleanup lasted, but also check that the computer’s approved work still runs.
Challenge
EasyTicket from Sam, IT lead
Test the cleaned support-laptop after a restart. Its unwanted program must remain stopped when the next connection attempt happens. Keep its file quarantined and its startup entry disabled. Confirm the approved backup still works and that no new customer data leaves through the old connection.
Try it yourself
All lessons in Investigating a Breach
1Follow the Evidence
Running ProgramsParent ProcessesFile FingerprintsSave the EvidenceAnother Report2Make the Cleanup Last
Stop the ProgramQuarantine the FileStartup EntriesTest the RestartThe Returning Program