Daniel Oz

I got my first computer at six and wrecked it almost immediately. My dad called a technician. I sat there watching him and all I could think about was wanting to know what he knows. Take these machines apart myself.

Same with everything else. Every toy I got, I'd crack open. I wanted to see the parts, figure out what makes them tick.

Most of what I know I picked up on my own. Got into computers early, got into breaking things, and eventually turned it into a career. I've managed a cybersecurity department, taught offensive security, and today I lead the offensive cyber division at one of Israel's largest healthcare organizations.

Vulnerability research, exploit development, reverse engineering, system internals. Whatever I happen to be digging into. Most posts here started as something I was already investigating for work or on my own time. When I find something interesting enough, I write it up.

I look at systems and see where they fail. Trust relationships nobody checked, design decisions nobody revisited, assumptions that went untested. That's just how my brain works. Has been since I was a kid breaking toys.

The exploit itself is usually the least interesting part of the process. Building the mental model of why something should break, figuring out the logic, mapping the assumptions. That takes the most time and thinking. The exploit at the end is just confirmation that the model was right.