Process and question
The OSINT research process
OSINT (intelligence gathered and verified from publicly available sources) runs in five steps: plan, collect, process, analyse, report.
Why it matters
The order is what keeps the work from drifting. If I start collecting before writing the question, I end up with a pile of screenshots and no context.
Method
- Plan: write the question, the limits, and which sources are allowed.
- Collect: take the raw data together with its source address and a UTC timestamp.
- Process: name and order the files, and leave the raw copy alone.
- Analyse: separate Fact, Inference, and Assumption.
- Report: attach a source and a confidence level to every finding.
Example
For one domain I first wrote: "When was this registered and who might be running it?" Only then did I look at the registration record. Without the question I would have jumped straight to a subdomain list, and that list did not answer the question.
Common mistake
Starting with a tool. Typing something into a search box feels like starting work, but it does not set the scope.
OPSEC and ethics note
In the planning step I also write down the legal and OPSEC limits (operational security, meaning protecting myself and the work). Remembering them later does not work.
Question before tool, limits before question.
Sources I used
- My own weekly binder reports and practical index
- Berkeley Protocol on Digital Open Source Investigations
- GIAC Open Source Intelligence (GOSI) certification page

