INSIGHTS / THE MERIDIAN SERIES
01 / 16
The Governance Gap
The Exception That Outlived Its Reason
Eighteen months ago, you approved a firewall exception. A subcontractor three tiers down your supply chain needed an old system-to-system connection to keep parts flowing, the proper fix wasn't ready yet, and ninety days felt like a reasonable bridge — long enough to finish moving that connection onto the newer, more secure network, short enough that nobody worried about it becoming permanent.
Then the migration moved on without it. Three other subcontractors got migrated on schedule. This one didn't — the engineer assigned to it got pulled onto a higher-priority project, and the ticket sat. Nobody closed the loop, because nobody was watching for it to reopen.

How One Decision Becomes Five Records
That approval didn't stay in one place. Security logged the exception. Procurement holds the subcontractor's data-handling terms. The program office tracks the migration as a line item in a spreadsheet nobody's opened since spring. Compliance has a control marked "in progress." Five records, five owners, and not one of them is the reason you approved the exception in the first place.
That reason — the judgment call that made ninety days defensible instead of reckless — never had a home of its own. It lived in a meeting, an email thread, maybe a comment on a ticket that's since been closed and archived. The records describe what happened. None of them explain why it was still okay.
What an Audit Finds
Your new security director finds the exception during a routine review ahead of a contract renewal — the kind of check every government supplier has to pass to keep the work coming. It's live. It's still open. And the honest answer to "why is this still here" is: nobody knows. The subcontractor is still using it. The engineer who owned the fix doesn't work this account anymore. The compliance record still says "in progress," which is technically true and completely useless.
Here's the question that actually matters, and it isn't whether the exception is documented. It's whether the reasoning that made it defensible eighteen months ago still holds up today. Does the subcontractor's access still match what was approved? Is the fix still funded, still staffed, still real? If the answer to any of that is no, you're not carrying the risk you accepted — you're carrying a different one, and nobody decided to accept it.

Naming the Gap
I call this the Governance Gap: the distance between the reasoning that made a decision defensible and the governance work — the tickets, the approvals, the compliance records — that's supposed to carry that reasoning forward. The work can be done perfectly. The paperwork can be immaculate. And the gap still opens anyway — not because nobody wrote the decision down, but because what gets written down doesn't move with reality. The record holds the decision. It doesn't hold whether the condition that justified it still holds, or what it's now costing you if it doesn't.
Every open exception in your environment right now is carrying one. The only question is whether you can still answer for it, or whether you're about to find out you can't.