INSIGHTS / APPLIED USE CASES
USE CASE · COMPLIANCE & RISK
Compliance Evidence Must Change the Risk State

Picture a routine compliance test: an auditor checks whether critical vulnerabilities are actually getting patched within the timeline your policy requires. Say the test comes back showing a handful of failures — vulnerabilities that blew past their deadline. That finding gets written up, filed, and closed out at the next audit cycle. Box checked.
Now here's the problem: remember that vulnerability your team accepted 90 days for, back a year ago? It's one of the ones that failed this test. But the compliance finding and the original risk acceptance live in two completely different systems, tracked by two different teams, reviewed on two different schedules. Nobody connects them. So the audit shows "control failure, remediated" once someone eventually patches something, and the actual open risk that's been sitting there for a year never gets touched by that finding at all.

Why This Keeps Happening
A compliance test answers one narrow question: was the control working the way it's supposed to, at the moment someone checked. It doesn't ask whether the risk that control exists to manage is still open somewhere on your books, still within the terms of an old acceptance, still costing you something real. Those two things — did the control pass, and is the underlying risk still live — get tracked completely separately, and somebody has to manually connect them for the finding to actually mean anything.
What a Finding Should Actually Do
When a compliance test finds something, it should immediately update four things at once: the actual state of that control, what the exposure is worth in dollars now that you know the control isn't working, whether that pushes you outside the risk appetite you set, and what's actually being done about it — fixed, transferred, or knowingly accepted with someone's name on it. Right now, most companies get the finding and stop there. It sits in an audit report. Nothing downstream of it moves.
Keeping the Reasoning, Not Just the Result
When a finding does eventually connect back to a real decision — say, leadership decides the risk acceptance still holds even with the failed control — that decision needs its own record: what was known at the time, who authorized continuing to carry it, and why. Without that, you can prove the test happened. You can't prove anyone actually decided anything because of it.
That's what's missing from most compliance programs: testing that actually changes what you know about your real risk the moment the facts change. Meridian ties compliance evidence directly to the exposure, the appetite, and the decision it should be informing — so a finding does something, instead of just getting filed.
APPLIED USE CASES