Interviews produce the diagnosis. Your own data tests it.

Security teams today are more capable and better funded than ever. The challenge is that most programs are measured by the tools they deploy and the frameworks they follow, not by whether the system as a whole is actually reducing exposure.

Each thing a person tells us about how security works becomes a belief we can check. The gap between what the organization believes and what its data shows is the finding.

Everything we check is written down with the evidence, an owner, and a date to look again, so the results stay useful long after the engagement. See a sample report.

This is not a checklist and not a tool. It is a way of seeing, applied the same way whether the company has 40 people or a board.

Five questions that reveal structural risk

Every engagement begins here. The questions are the same for a 40-person firm and a regulated enterprise; the depth of the evidence changes.

Every system, whether technical or human, is designed to optimize for something. Often, that original optimization no longer matches current needs. A security program measured by its audit results may be optimizing for evidence rather than for exposure reduction, without anyone having chosen that. Understanding what a system is truly optimizing for reveals whether it can deliver what you now need from it.

Systems that depend on people always doing the right thing will eventually fail. Humans forget. They cut corners under pressure. They misunderstand instructions. When we identify where a system assumes perfect human behavior, we find the places where failure is not a matter of if, but when.

Every system is built on assumptions about the environment, the users, the threats, and the resources available. Over time, these assumptions drift from reality. The cloud architecture designed for a 50-person company may not hold at 500. Identifying expired assumptions is often the fastest path to understanding why something no longer works.

Catastrophic failures rarely arrive suddenly. They accumulate. Small compromises compound. Warning signs get normalized. By the time failure becomes visible, the conditions that caused it have often been present for months or years.

Organizations often respond to uncertainty with more controls, more process, more oversight. But control without clarity creates friction without safety. Sometimes the most effective intervention is helping people understand what they are actually trying to protect, and why.

Free Diagnostic

See which question your program points to

Five minutes, thirteen questions, no login. You see the result on screen.

Take the 5-minute check

The Lens applies wherever systems meet assumptions

Cybersecurity

Examining security programs, architectures, and strategies for the structural risks that compliance frameworks miss.

Technology & Cloud

Evaluating architecture decisions and technology investments for hidden assumptions and future constraints.

Leadership

Helping executives see organizational dynamics, communication breakdowns, and strategic blind spots.

The perspective

Cybersecurist™

The intellectual property: the framework and lens that shapes how we see systems, risk, and failure, shared through writing, speaking, and public discourse.

See which question your program points to

Five minutes for the free check, or fifteen for a conversation about what it means.