Resilience Beyond Compliance Is Becoming the New Third-Party Risk Benchmark
- Explores the gap between regulatory compliance and operational
resilience.
- Examines common weaknesses in third-party risk documentation and
governance.
- Discusses how organizations can improve transparency without increasing
administrative burden.
- Highlights growing regulatory focus on resilience testing and real-world
outcomes.
- Looks at how third-party risk management will evolve over the next five years.
display-middle-ads-here
1. Many organisations invest significant time
and resources in meeting regulatory requirements, yet third-party failures
continue to cause major disruptions. In your experience, where is the biggest
gap between regulatory readiness and true operational resilience?
Most frameworks are built to answer a
supervisor's question, not to survive a supplier's bad day. Those are different
tests. A supervisor asks whether you identified the risk, assessed it and
recorded the decision. An outage asks whether someone in your building can make
a call at eleven at night with half the information and no vendor on the phone.
I have watched very compliant institutions freeze on the second test. The paper
was fine. The room wasn't. Readiness is a property of documents. Resilience is
a property of people, contracts and infrastructure under load. We spend most of
our effort on the first because it is what gets inspected, and that is the gap.
2. Regulators increasingly expect
organisations to provide clear evidence of how third-party risks are
identified, assessed, and managed. What are the most common weaknesses you see
in the way firms document and demonstrate their risk management decisions?
Firms document activity and call it
decision-making. The register is complete, the questionnaire is returned, the
rating is assigned. What is usually missing is the sentence that says who
accepted this risk, on what basis, and what would make them change their mind.
I look for that sentence first in any file. It is rarely there. The second
weakness is that ratings age badly. A vendor rated medium at onboarding stays
medium for three years while its footprint in your operations doubles. Nothing
in the file is wrong. All of it is stale. Supervisors have noticed. They are
asking less about the assessment now and more about what you did with it.
3. Collecting and validating evidence across
multiple functions, suppliers, and jurisdictions can be resource intensive. How
can organisations improve transparency and auditability without creating
excessive administrative burden for risk, procurement, and business teams?
Stop collecting evidence you never use. Most
of the burden comes from asking every supplier the same two hundred questions
regardless of what they do for you. Tier properly and mean it. A stationery
supplier does not need the same file as your core banking provider, and if your
framework says otherwise, the framework is the problem. Then make evidence a
by-product of running the process rather than a separate exercise. If the
decision is taken in committee, the minute is the evidence. If monitoring runs
off system data, the log is the evidence. The moment you build a team whose job
is producing evidence, you have put a compliance function inside your risk function and both get
slower. We do not want to overkill it. Proportionate and live beats
comprehensive and dead.
4. As regulatory expectations continue to
evolve, do you believe supervisory focus will increasingly shift from policies
and documentation towards evidence of real-world outcomes and resilience
testing? What should organisations be doing now to prepare for that shift?
It already has. The UK has been asking for
impact tolerances and scenario results for years. DORA is written around
testing, not policies. FINMA's operational resilience circular is built on
critical functions, not documents. Anyone waiting for the shift has missed it.
What supervisors want now is the hardest thing to produce: proof that something
was tried and either held or didn't. That means running a stressed exit on a
real critical vendor rather than table topping it. It means putting the
supplier in the room for the scenario, because your recovery plan is only half
the plan. And it means being willing to take a failed test to your board. A
clean result on a critical dependency should open a question, not close one. If
everything passed, either the scenario was soft or nobody looked hard.
5. Looking ahead, what will a truly resilient
third-party risk programme look like in five years' time, and how can
organisations ensure they are building capabilities that go beyond compliance
to withstand genuine supplier disruption?
The good programmes will not look like
programmes. Third-party risk will be a design constraint on the business rather
than a review at the end of it. Concentration will be decided when the
architecture is drawn, not discovered when it fails. Contracts will be written
for the worst week of the relationship, not the first. Monitoring will run off
data the supplier is obliged to feed you, not questionnaires they complete once
a year. And the question in the boardroom will move from "are we compliant"
to "how much could we lose, for how long, and who decides".
Regulation tells you the minimum. Your suppliers will test you on the
maximum. I will make the fuller argument in London,
and I do not expect everyone in the room to agree with it.
Vice President, Risk Management, Habib Bank AG Zurich
I am a seasoned Financial Risk Management professional with 19+ years of experience in banking, treasury, fintech, and AI-driven risk solutions. I am passionate about challenging traditional approaches to risk and driving innovation in the industry. As Vice President of Risk Management and Head of Market & Liquidity Risk, I develop and implement cutting-edge risk frameworks, ensure regulatory compliance, and deliver strategic solutions for complex financial challenges. I am also an International Speaker, Author, and Advisory Board Member, contributing to global discussions on risk, AI, and finance.
LinkedIn profile