INSIGHTS / THE MERIDIAN SERIES

13 / 16

Risk Appetite Requires a Current View of the Enterprise

Say your company sets a rule: no critical vulnerability stays open more than 90 days without a signed risk acceptance from someone senior enough to own it. That's risk appetite — the line you've drawn for how much risk you're willing to carry, and under what conditions.

A rule like that only means something if you actually know, right now, whether you're inside it or outside it. And that's where most companies get stuck. You've got a vulnerability scanner that knows what's open, a ticketing system that knows what's assigned, and a spreadsheet somewhere that tracks the handful of risk acceptances anyone remembers to log. Each one is accurate on its own. None of them, on its own, can tell you whether the rule you set is actually being followed right now.

A single point positioned against a boundary line, illustrating a risk measured against an appetite threshold.

Data Has to Tell You Something About the Business

A scan result by itself is just a fact: a server has a vulnerability. It doesn't become useful until it's connected to what that fact means for you — is this covered by an existing acceptance, is that acceptance still valid, is it past the 90-day line or inside it. Without that connection, you've got a list of facts and a rule sitting in a different document, and somebody has to manually match them up every time someone asks.

Where you can put a dollar figure on the exposure, that gets even more useful — now you can weigh whether the acceptance you granted is still worth what it's costing you to carry, the same way you'd weigh any other spend.

A Live View, Not a Snapshot

You don't need to connect every system in the company on day one. You can start with one area — vulnerability management, say, or vendor risk — and build a real, current view there: what's actually open right now, what's been accepted, what's past its own deadline. Add more areas over time, and the picture gets bigger without you having to start over.

Inside whatever scope you've built, you can actually compare the risk you said you'd carry against the risk you're carrying. That comparison is risk appetite doing its job — not a policy sitting in a binder, but a line you can check yourself against, today.

Two Different Levels of Appetite

There's a version of this that looks fine and still isn't. Take that same 90-day rule. Now imagine fifty vulnerabilities across the company, each with its own acceptance, each one signed by someone who followed the rule, each one sitting inside its own 90-day window. Individually, every single one of them is defensible. Nobody did anything wrong.

But add them up, and that's fifty separate risk items the company is carrying at the same time. Is that total still inside what the company as a whole is willing to carry? Nobody can answer that by looking at any one acceptance. You need both: is this specific risk staying inside the rule its owner agreed to, and is the sum of everything currently accepted staying inside what the business can actually absorb.

Most companies can answer the first question, one acceptance at a time, if someone goes looking. Almost none of them can answer the second one at all, because nothing connects the individual acceptances into a total. That's the harder problem, and it's the one that actually matters at the board level — not whether any single risk owner made a defensible call, but whether the company, in aggregate, is still inside its own appetite.

Individual limits versus company appetiteLeft panel, each risk against its own limit: about fifty thin bars of varied small heights, all below a dashed line labeled each owner's limit. Right panel, all of them together against company appetite: the same fifty segments stacked into one tall column that rises above a dashed line labeled what the company will carry.Each risk, against its own limitRisk carriedEach owner's limitAll of them together, against companyappetiteRisk carriedWhat the companywill carry
Every acceptance can be defensible and the total can still be over the line.Illustrative

The Rule Only Works If You Know Where You Stand

The rule itself doesn't change once you can measure against it. What you gain is the ability to hold your current state up against it, right now, with evidence instead of a guess — at the level of one risk, and at the level of everything the company is carrying together.

A boundary is only as useful as your ability to see where you actually stand against it. Meridian is built to keep that current view connected — so "no criticals past 90 days" isn't a rule you hope is true. It's one you can check, one risk at a time and in total.