Insights

Cyber risk without the theater

Practical questions that reduce real exposure for small and mid-sized operators — without drowning the team in dashboards, tools, and maturity theater.

A board member, an owner, or a capture lead asks a reasonable question: are we actually at risk? The room answers with a product tour. A new dashboard. Another endpoint agent. A maturity model with a color. Six months later the stack is busier, the invoices are real, and nobody can say what exposure changed. The questions that would have reduced harm never got asked.

We see that as a framing problem, not a staffing failure. Small and mid-sized operators — federal contractors, nonprofits, real estate investors — rarely fail cyber because they skipped the enterprise catalog. They fail because activity was mistaken for judgment: more tools, more reports, still no named owner, no picture of what would actually hurt, and no recovery path anyone has tested.

Theater is activity. Risk is a few questions you can answer.

We treat cybersecurity as operating risk, not as a shopping list. Theater is anything that consumes attention and budget while leaving the same people able to get in, the same systems unowned, and the same restore untested. A crowded stack can still be theater. A one-page picture of crown jewels, access, and recovery can be the opposite.

Three tests decide whether the work is reducing exposure or performing security:

Named. Someone owns cyber as an operating problem — not “IT,” not a vendor portal, not a shared inbox. If the first call after an incident is “who is supposed to handle this?”, you do not have a program. You have a hope.

Proportionate. Controls match what would actually stop the mission, move money, or break trust. A 200-row register no one ranks is not proportionate. Neither is buying a platform because a peer mentioned it, a funder used a buzzword, or a proposal draft needed a discriminator.

Recoverable. You can restore the work that matters, with people who know the steps, in a time you could live with. Backup jobs that have never been restored are a comfort object. They are not a control.

We look for those tests before we talk tools. Identity before another monitoring product. Ownership before a framework name. A tested restore before a “zero trust” slide. We do not invent clients, incidents, or certifications, and we do not promise CMMC, insurance outcomes, or that a checklist will keep you from being breached. The useful question is narrower: if something went wrong this week, would we know what hurt, who decides, and whether we can come back?

This is not legal, procurement, or compliance advice. Contract clauses, funder conditions, and board policies you have already committed to still govern. The questions below help you see exposure clearly enough to act without drowning the team.

Practical moves

These are checks we use when an operator wants less theater and more reduction of real exposure. They are not a universal control set, and they are not a substitute for counsel, an assessor, or your insurer.

1. Ask what would actually hurt — then stop the list.
Write one page, not a register. What would stop operations this month? What would move money you cannot easily claw back? What data, if leaked or locked, would break trust with customers, donors, tenants, or a government customer? Name the systems behind those answers: email, finance, CRM or property systems, proposal shares, identity. If it is not on that page, it can wait. Theater starts when every asset is “critical.”

2. Ask who can get in — including people who already left.
Most of the exposure we see is identity, not a missing appliance. Who has admin on email, finance, cloud, and the primary line-of-business system? Is MFA on those paths, or only on the ones that were easy? How fast does access die when someone leaves, a contractor ends, or a volunteer stops showing up? Same-day offboarding and least privilege are boring. They close more real doors than a new dashboard that nobody triages. If you cannot answer who still has keys, buying another lock is theater.

3. Ask what is internet-facing and who owns the vendor.
Map the handful of things a stranger could actually reach: websites, remote access, file shares, SaaS consoles, public logins. For each, name an owner and whether the vendor holds data you would hate to lose. Small teams often discover that “our IT” is three products, a former staffer’s tenant, and a property or program tool nobody renewed on purpose. You do not need a CMDB. You need a list someone would still recognize next quarter. Vendor risk here is a contract-and-access question, not a questionnaire you will never score.

4. Ask whether you can restore, not whether a backup job is green.
Pick one crown-jewel system and restore it on a calendar, with the people who would do it for real. Note how long it took, what was missing (credentials, a runbook, an offline copy), and what you would tell staff, a board, or a customer while it was down. A green backup tile is not evidence. A restore you have watched is. Until that exists, ransomware slides are mostly narrative.

5. Ask who decides when it breaks — and what you will not buy this year.
Write a one-page incident card: who is called, who speaks, who can pull a system offline, which counsel or insurer number is current. Then write a short “not this year” list: platforms you will not add until identity, restore, and ownership are true. A decision log keeps the next vendor demo from becoming the strategy. If a board or a pursuit wants a maturity story, tell the true one: what you constrain, what you monitor, what you still accept.

None of this replaces a formal assessment when a contract or a board requires one. It does give that work a spine so the output is a sequence, not a tool catalog.

Who this is for

This is for operators who need cybersecurity that protects the work without burying a small team in theater — federal contractors under clause pressure, nonprofit leaders holding donor and program data, investors whose deals and properties run on a thin set of systems. It is not a guarantee about incidents, ratings, or certifications. Nonprofit boards who want the stewardship version of the same moves can start with Cybersecurity for Non-Security Leaders.

If you are in that bind — busy stack, no owners, no tested restore, and a room asking if you are “secure” — tell us the operating pressure and what you already know is fragile. We will say whether a collaboration is a fit.

Contact us.