Engineering

Cybersecurity

My reverse-engineering work focuses on studying single-player programs. I use it to learn about memory, instructions, and how observed behavior relates to code.

Following the evidence

The workbench records memory changes, decodes instructions, and keeps observations separate from hypotheses. A changing value gives me somewhere to investigate; it doesn't tell me what the value means.

I keep records tied to the session that produced them, so I can return to an investigation without treating an old address as a current finding.

Open questions

  • What was actually sampled, and what was missed between samples?
  • Which part of this note is an observation, and which part is a hypothesis?
  • Would the same number still mean anything after the process starts again?