Typical telemetry
- Process creation and parent-child relationships.
- Command lines.
- File creation or modification.
- User and session context.
- Network connections.
- Security-relevant changes and detections.
Understand endpoint detection and response telemetry and how analysts use it during investigations.
EDR focuses on endpoint activity such as processes, files, users and network connections. Its value comes from detailed host context and investigation pivots.
Use this page after the daily quiz: learn the concept first, then follow the investigation workflow and examples.
Which EDR evidence is especially useful for understanding how a suspicious process started: its parent-child process relationship or only its filename?
Quiz flow: introduce this topic briefly on social media, ask the question, reveal the answer, then send learners here for the detailed investigation.
Endpoint detection and response is useful when events retain relationships: process ancestry, user, file changes, persistence, network activity, and sensor health. An alert is one analytic result; the underlying timeline is what lets an investigator test the explanation.
Follow one process from parent to child and compare its behavior with the host’s role. Missing telemetry can reflect sensor coverage or policy as well as attacker evasion, so validate collection health before concluding that an event did not occur.
Continue practicing: open a fictional mission and test your reasoning against the simulated evidence.