DON’T FOLLOW THE NARRATIVE. FOLLOW THE EVIDENCE.
A badge doesn’t make you an investigator and a certification doesn’t automatically make you an expert. What matters is whether you can follow evidence, control your bias, and recognize when someone else’s narrative is influencing your conclusions.
I’ve spent decades teaching investigative thinking to law enforcement officers, digital forensic examiners, and even a few “secret squirrels.” I’ve written books and developed frameworks around one central idea: investigating isn’t about pushing buttons. It’s about knowing what questions to ask, how to evaluate evidence, and when to challenge your own conclusions.
But there’s something I’ve wanted to demonstrate for years and haven’t been able to: A real investigation unfolding in public, using actual records that anyone can examine.
Not a fictional training exercise. Not a closed case or CTF where we already know the ending. An investigation where evidence arrives over time, questions lead to more questions, and conclusions can change.
Register (free) here: https://www.suspectbehindthekeyboard.com/offers/Q5EZpEkq/checkout
There are good reasons why this is difficult.
Real casework involves NDAs, sealed court records, privacy laws, confidential information, and sometimes ongoing criminal or civil proceedings. Sharing evidence from an active case can compromise an investigation, violate legal obligations, expose people unnecessarily, or lead to some very painful cross-examinations.
You can’t just open a live case file and invite the public to follow along. I’ve helped investigate actual cases while training investigators behind closed doors, but that’s different. The evidence stays confidential, the work stays within the investigation, and the public never gets to see the process unfold.
That leaves much of the industry relying on sanitized case studies, 10-year-old closed files, or perfectly packaged fictional CTFs where the answer is already baked in.
Those are useful for learning tools, techniques, and procedures. But they don’t always teach you what to do when you don’t know how the story ends.
I’m done relying exclusively on the sanitized versions. I’ve found a way to demonstrate investigative thinking in real time, using actual government records as they’re released.
Public records.
Government agencies generate records documenting their activities. Emails, memoranda, reports, investigative files, communications, and decisions. Much of that material is legally accessible through public records laws, subject to exemptions, redactions, and other legal protections.
You don’t need a badge. You can request those records yourself and that’s exactly what I’ve done.
I recently learned of an event involving a public agency that immediately made me curious, so I started submitting public records requests.
The records are already coming in, with more expected installments in the coming months.
And instead of simply writing an opinion piece about what I think happened, I’m going to show you how to think, plan, ask questions, and evaluate evidence using the principles I teach in The DFIR Investigative Mindset.
This isn’t primarily a digital forensic investigation, although there are digital forensic issues involved.
And it isn’t an official criminal investigation. I don’t have the authority to compel testimony, seize evidence, or access every record the government possesses. What I do have are public records, the ability to ask questions, and decades of investigative experience.
That’s enough to demonstrate something I’ve wanted to show for years. How to investigate when nobody hands you the answers.
We’ll start with what’s publicly known about the incident, examine what the underlying records reveal, and follow the evidence wherever it leads. We may reach firm conclusions about some questions and find that others remain unanswered.
We’ll compare official statements against documented facts, build a timeline, identify contradictions, and separate what the evidence establishes from what remains unsupported.
When a document answers one question but raises three more, we’ll follow those questions. When something doesn’t make sense, we’ll examine why. When an explanation appears reasonable, we’ll test it. And when the evidence doesn’t support a conclusion, we won’t make one.
Finding something suspicious doesn’t automatically establish misconduct. An allegation isn’t proof. A contradiction doesn’t necessarily mean someone lied. And a missing record doesn’t automatically mean someone destroyed it.
Forming a theory early isn’t the problem. Refusing to test it is. When you spend the rest of an investigation collecting only evidence that supports your theory, you’ve stopped investigating and started confirming your own bias.
I’ll show you my reasoning, explain where I think the evidence leads, and identify where it stops.
You might disagree with my interpretations. Good. That’s the point.
I don’t want you to take my word for anything. I want you to examine the source documents, decide whether my reasoning holds up, and tell me where you think I’m wrong. Show me the evidence that supports a different interpretation. I’ll examine it just as critically as my own.
That’s lesson one: Challenge the hypothesis. Especially your own.
I already have records that I consider explosive. But explosive evidence can turn out to be nothing when confronted with other evidence. That’s how investigations work.
I have missing pieces, explanations I haven’t verified, and questions I can’t answer. I’m not starting from nothing. I already have evidence and a working hypothesis about where this might lead. But that’s only one of several possible outcomes, and I could be wrong. A hypothesis is something to test, not something to prove.
As new records arrive, my understanding may change, and if it does, I’ll explain exactly why.
I’ll distinguish documented facts from my observations, interpretations, and opinions. I’ll identify alternative explanations and show what additional evidence would be needed to support or eliminate them.
I’ll also explain why I ask for certain records, what I’m looking for, and what I plan to do with the information. Just like a real investigation, not every lead will go somewhere. Some questions may never be answered. Some records might contradict what I currently believe.
That’s part of the process. The purpose isn’t to prove an accusation. The purpose is to demonstrate how an investigative mindset works when the answers aren’t supplied in advance.
Follow this investigation as it unfolds.
Beginning this week, I’m publishing a short series examining this event, the records I’ve obtained, the questions they raise, and the investigative reasoning behind my conclusions. To be clear, the event is done. The internal investigation is over. But the public records have not all been produced, so we don’t know any of the conclusions or if they were fair or biased.
My goal isn’t to embarrass anyone. My goal is to examine a matter of public interest, follow the records, and see whether the documented facts support what the public has been told.
You don’t need any digital forensics experience to follow along.
The same investigative principles apply whether you’re examining a hard drive, conducting an incident response, investigating a crime, evaluating a witness statement, or filing your own public records request.
Apply what I discuss to your DFIR work, or any investigative work you do. You’re invited to challenge my reasoning because they will help yours.
Live discussions
I’m also planning free live discussions about the records, the investigative process, and the questions that come up along the way. This will be a free invite only, not a YouTube video.
No prepared lectures. Just online conversations where you can ask questions, challenge my interpretations, and see how I work through evidence that doesn’t always fit neatly together.
And perhaps most importantly, we’ll talk about the investigative friction involved when records are incomplete, explanations conflict, and answers aren’t readily available. I’ve already received hundreds of files. Many contain substantial redactions, leaving gaps in what I can establish from the records. That’s part of the challenge. You don’t get to invent what you can’t see.
The first installment begins this week.
Bring your curiosity. Bring your skepticism. Don’t take my word for it. Don’t take the government’s word for it. Read the evidence.
Social media won’t necessarily show you every installment. If you want the articles, supporting documents, and invitations to the live discussions delivered directly to your inbox, sign up below.
No paywall. No predetermined conclusions. Just the evidence and the process of following it.
Discover more from Brett's Ramblings
Subscribe to get the latest posts sent to your email.