INSIGHTS / THE MERIDIAN SERIES

02 / 16

Decision Value

What the Audit Doesn't Tell You

Say your security director's audit turns up that firewall exception — the one for the subcontractor's system connection that was supposed to close in ninety days and is still open eighteen months later. The audit gives you a severity rating. It does not tell you what to do about it.

That's the gap that actually matters day to day. A rating tells you how bad the exception looks on paper. It doesn't tell you what happens to the subcontractor's parts flow if you shut it down this afternoon, what it costs to fix it properly, how long you can hold the current risk while you decide, or who in your organization actually has the authority to say "we'll carry this a while longer."

Abstract visualization of a single marked point radiating into several faint, unresolved paths.

Three Paths, Three Different Costs

You have real options here, and they're not equivalent. Revoke the exception today, and the subcontractor's connection goes down with it — parts flow stops until they stand up the proper connection, which could be days, could be longer, and it's not entirely in your control. Leave it open while you fund and staff the original fix for real this time, and you're carrying the exposure for another few weeks, deliberately, with your eyes open. Or negotiate a narrower version — cut the subcontractor's access down to exactly what they need for the current order cycle, nothing more — which costs you engineering time now instead of exposure later.

Every one of those paths changes something specific: how fast the subcontractor can ship, how much of your team's time gets pulled into this instead of the next contract, and how much risk you're still holding while the fix gets built.

The Number Isn't the Decision

Here's where it gets harder than a spreadsheet. Say the "leave it open and fix it properly" path has the best numbers — lowest disruption, lowest cost. That still might not be the right call, and the reason has nothing to do with the math. If your contract renewal review is six weeks out, "a few more weeks of exposure" might land you back in the same audit with the same finding, except now nobody can say you didn't know. If the subcontractor's own security posture has changed since you approved the original exception, the number you're carrying isn't even the number you think it is.

The path with the best forecast is still just a forecast, until someone can act on it. And someone has to be able to say yes — not just to the analysis, but to the actual trade-off: this much exposure, for this much benefit, for this long, under these conditions.

Treatment options compared in dollarsThree options for an open firewall exception, each shown as a pair of bars: cost to treat and exposure reduced. Closing the exception now costs a lot and reduces a lot. Keeping it open and accepting the risk costs little and reduces little. Adding a compensating control costs moderately and reduces almost as much exposure as closing it, so it is marked as the strongest case, where exposure reduced most exceeds cost.Cost to treatExposure reducedClose the exception nowKeep it open and accept the riskStrongest caseAdd a compensating controlDollars →
Put every option in dollars and the choice can be defended, not just argued.Illustrative

The Choice You Can Defend

That's what I mean by Decision Value: not the severity score, not the loss estimate, but whether the information in front of you is enough to make a call you can stand behind. It has to tell you what's really on the table, what each option costs, how long you can carry the exposure, and who has the standing to approve it.

Get that right, and the decision holds up under a second look. Get it wrong, and you're back where the exception started — a choice that made sense in the moment, with no way to prove it still does.