Research
Tooling
Nothing here was built to be a product. Each exists because a piece of research needed it and nothing suitable did, which is the only good reason to write a tool.
The work
What this actually involves
Not a checklist worked through in order. These are the parts of the job, and the target decides how much of each it needs.
-
Harnesses
The scaffolding that gets a target into a state where it can be hammered at speed, and keeps it there.
-
Minimisation and triage
Turning ten thousand crashes into the six worth an afternoon, and proving the rest are the same bug.
-
Instrumentation
Seeing what the software is doing, not inferring it from what it printed.
-
Reconnaissance
Working out what a target is made of (versions, components, lineage) before deciding where to push.
Next
How it runs, and how to commission it
Every piece of research follows the same four steps, and the same terms apply to what comes out.
Ask about tooling
Tell us what the target is and what you need to know about it.