Did Data Leave?
Part of the Investigating a Breach section of Coddy's Cybersecurity journey. Lesson 12 of 20.
An attacker trying to send a file is different from a file actually leaving. Your report needs to distinguish those two outcomes.
Read the practice computer’s transfer record:
seclab logsLook for these lines:
2026-11-01 08:58:00 practice-laptop DATA_TRANSFERRED demo-upload: training-records.csvDATA_TRANSFERRED confirms that training-records.csv left through demo-upload. A CONNECTION_BLOCKED record would tell you that a connection attempt was stopped instead.
A successful cleanup cannot undo a transfer that already happened. You still need to record the confirmed loss so the team can decide what to do next.
Record only the filename supported by the transfer record:
seclab answer transferred training-records.csvYou should see:
Recorded your answer to transferred.Challenge
EasyTicket from Sam, IT lead
Sam has added two older audit records from the roastery incident. Determine which file is confirmed as transferred and which file was blocked. Record the filenames as transferred and blocked. Keep the cleaned program stopped and the approved backup working.
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 Program3Work Out What Happened
Build a TimelineDid Data Leave?Find Another CopyRestore a Safe ProgramThe Contractor’s Report