Desk live·
ForensicPost
The desk

Evidence before narrative

ForensicPost exists because most reporting on intrusions is written from press releases and most technical writing about them is written to sell something. We do neither. Every file we publish states what we reviewed, how confident we are, and what we still cannot answer.

01 · Sourcing

We name the number of artefacts we reviewed and the number of independent sources behind each claim. Where a file rests on one source, the file says so, in the file, not in a footnote.

02 · Independence

No vendor sponsorship, no sponsored files, no embargoed marketing. Revenue is subscriptions and institutional licences for the Case Files database. Our licence holders get no editorial input, ever.

03 · Harm

We publish hashes and infrastructure. We do not publish victim data, file trees that identify individuals, or working exploit detail. We never name the analyst who took the call.

Masthead
Paul Bradford
Editor in chief. Sets grading policy and signs off every file.
D. Kennedy
Editor. Identity and access. Former DFIR consultant.
S. Rosler
Extortion groups, leak-site economics, sample verification.
M. Kallio
Lead examiner. Malware teardowns and driver abuse.
A. Sandoval
Data editor. Owns the Case Files schema and grading.
Corrections log · 2026
22 Jul26-0618We wrote that five rating agencies had stopped sharing data with NAIC. Four had, at the time of publication. Corrected within four hours; the file records the original wording.
09 Jun26-0508Our first version described the Instructure incident as affecting all Canvas tenants. It did not. Headline and standfirst rewritten.
14 Apr26-0312We reported a 700-terabyte figure without labelling it an actor claim. The label was added and our verification method published alongside it.
03 Feb26-0209An earlier version misstated the registry’s operator. Corrected; the ministry’s statement is quoted in full.
Ethics, in short

We do not pay sources, and we do not pay actors for data. We do not accept exclusives conditioned on framing. If an organisation asks us to delay for containment, we weigh the delay against reader harm and record the decision in the file.

Our examiners hold no equity in security vendors and disclose prior employment on every file where it touches the subject. Conference travel is paid by us. When we get something wrong, the correction runs at the top of the file, not the bottom.

© 2026 ForensicPost Media · newsletter archive · searchGlossary