01 / Research

I don't trust a scan result until I've checked it myself.

A finding is only useful if I can reproduce it, explain it and show why it matters. That's what I try to focus on when testing web applications.

02 / Process

How I approach a finding

01

Check the scope

Before touching a target, I check the rules and confirm what I'm allowed to test.

02

Reproduce the issue

If something looks off, I repeat the request and compare it with a normal response. One unusual result isn't enough.

03

Understand what happened

I try to work out the cause and impact instead of just copying whatever a scanner reported.

04

Document it clearly

I keep the minimum evidence needed to explain the behavior, remove anything sensitive and follow the disclosure rules.

03 / Write-ups

No public write-ups here yet.

I haven't published a disclosure on this site yet. I'd rather leave the section empty than put together a fake case study or dress up a scanner result. If I publish something, it'll include enough detail to understand and verify it without exposing anyone's data.

04 / Related

I've built some tools for reconnaissance, cache testing and other web security tasks. The tools catalog shows which projects have public source, a public website, or a private research summary.

Browse my tools