Menu

Write the Findings

Part of the Investigating a Breach section of Coddy's Cybersecurity journey. Lesson 18 of 20.

A useful incident report explains what the evidence supports. Name the affected computer, how the program started, what it tried to do and what you changed.

The practice evidence says demo-browser launched demo-helper. Its file names training-records.csv, and the logs confirm a transfer. Record a specific finding:

seclab answer cause demo-browser

You should see:

Recorded your answer to cause.

This is more useful than writing “someone hacked us.” It gives the next person a fact they can check.

Saved evidence belongs to the moment it was collected. A later record showing the process stopped does not contradict an earlier snapshot showing it running. Include that order in your explanation.

challenge icon

Challenge

Easy

Ticket from Sam, IT lead

Finish the studio incident findings using its saved evidence and logs. Record the affected computer as host, the parent that launched the helper as cause, and the helper’s file ID as file. Keep the completed cleanup and approved backup intact.

Try it yourself

Terminal

All lessons in Investigating a Breach