Building Resilience Through Third-Party Risk Management

Cyber

November 17, 2026

Beyond Compliance: Building Resilience Through Third-Party Risk Management

Most banks can list their critical suppliers. Far fewer can say what happens to their critical business services when one of those suppliers is breached, becomes inaccessible or simply stops working.

That gap was the subject of a session I presented with my colleague Gaurav Sheth at the FS-ISAC Americas Fall Summit. It reflects where financial institutions’ third-party risk management (TPRM) programs are heading, and the role cyber teams need to play.

 

The Question is Changing

Traditional TPRM asks whether a supplier is compliant and whether processes have been followed. That approach produces necessary evidence: completed assessments, assigned risk tiers and annual reviews. But it answers a narrow question.

Resilience-driven TPRM asks different ones: what fails, and what do we do next? Which services stop if a critical supplier fails? Where are our third-party concentrations? What workarounds are viable? Can we stay within impact tolerance?

Why the Question is Changing

Four pressures are driving the shift, and they reinforce one another:

1. Regulatory Focus.
Attention is moving from outsourcing compliance to service outcomes, resilience, incident reporting and material third-party arrangements.

2. Supply Chain Complexity.
Critical services increasingly depend on interconnected vendors, cloud platforms, software and data.

3. Cyber Incident Pressure.
Attackers exploit supply chains, connected services and trusted access, increasingly powered by AI.

4. Board Accountability.
Executives need evidence and assurance that critical services can remain within tolerance during a severe but plausible disruption.

The data underscores the cyber risk. Kroll’s Data Breach Outlook 2026 analyzes cases Kroll handled from June 2025 to June 2026, finance was the most-breached industry accounting for 20% of breaches. Among impacted individuals, 69% were affected by a third-party breach. Technology-sector incidents accounted for 60% of impacted individuals, despite representing only 6% of breaches. These figures reflect Kroll’s caseload rather than the broader market, but the pattern is clear: one vendor compromise can create obligations for many downstream organizations that never touched the vulnerable system.

The report also shows how attackers get in. Valid accounts were the most common initial access method in Kroll’s incident response engagements (31%), ahead of phishing links (20%) and external remote services (16%). Attackers can log in rather than break in, and a stolen vendor credential can look like legitimate activity.

Three Lessons from the Frontline

1. Compliance Does Not Equal Resilience

TPRM programs commonly track due diligence, annual reviews, contractual clauses, risk tiering and issue-aging metrics. Resilience requires more, including service-level impact analysis, substitutability and workarounds, concentration and subcontractor visibility, tested recovery, and clear escalation based on risk appetite.

A compliant supplier ecosystem can still leave critical services vulnerable.

 

2. Suppliers Are Not Services

The key visibility gap is understanding how supplier dependencies map to the business services they support. The blind spots are consistent:

  • Critical supplier lists that don’t show which services depend on them 
  • Material subcontractors that aren’t consistently mapped 
  • Platform that support multiple services 
  • Exit plans that aren’t service specific 
  • Cyber incidents tracked at the supplier level, with no view of downstream service impact 

Kroll’s recent Data Breach Outlook suggests this visibility gap may also be a communication gap. Fifty-four percent of IT and technology leaders rank vendor and third-party breaches as their single greatest compliance risk, compared with 39.7% of C-suite respondents and 30.4% of dedicated risk and compliance leaders.

Those closest to vendor risk may see the domino effect most clearly, but that understanding may not be reaching the executives who set risk appetite.

 

3. Service Criticality Should Organize Supplier Oversight

When service criticality becomes the organizing principle, it shapes supplier oversight, data, metrics, testing, monitoring and escalation. It also connects internal assets and third-party suppliers to the services they support, rather than assessing each in isolation.

What Good Looks Like: The Six Building Blocks

Institutions strengthening their programs should focus on six practices:

Critical Service Mapping

Connect suppliers to critical services and impact tolerances.

Dependency Mapping

Identify first-party and nth-party dependencies, including material subcontractors.

Concentration Analysis

Assess common provider, geography, technology, subcontractor and market concentration.

Continuous Monitoring

Align monitoring with supplier criticality and potential service impact.

Scenario Testing

Test severe but plausible failures, including cyber, and validate recovery assumptions.

Exit and Recovery Readiness

Document viable alternatives, workarounds, exit feasibility and governance triggers.

Whether the disruption is a cloud outage, ransomware attack, supplier breach or software compromise, resilience depends on the same things: understanding service dependencies, concentration and tested recovery options.

Concentration is also reshaping how the insurance market views the risk. As Katherine Keefe, Kroll’s Global Cyber Insurance Industry Lead, wrote in the Data Breach Outlook, insurers and policyholders are moving from asking, “could this vendor be breached?” to asking “how many other relationships does one breach take down with it?”

Banks should be asking the same question about their own supplier base.

Cyber’s Role: Turn Risk Signals into Decisions

Resilience-driven cyber TPRM broadens its focus to consider whether a business service can continue when a supplier is compromised or unavailable. In practice, that means multiple things, including:

  • Map Cyber Exposure
    Privileged access, data hosting, SaaS and cloud, SBOMs, APIs and digital supply-chain dependencies.
  • Control Third-Party Identities and Access
    Treat vendor identities as part of the attack surface. Apply least-privilege and time-bound access, strong authentication, privileged access controls, and regular access certification to third-party users and service accounts. Automatically revoke access when contracts, projects or support relationships end, and continuously monitor for dormant accounts, excessive privileges and anomalous access.
  • Monitor Continuously
    Use threat intelligence, passive scanning and dark web surveillance and other supply-chain risk signals, rather than periodic snapshots.
  • Test Failure Scenarios
    Ransomware, SaaS outage, data compromise, privileged access abuse and delayed supplier recovery, while integrating third parties into incident and crisis response.
  • Connect Third-Party Incidents to Enterprise Risk
    Coordinate decisions across cyber, resilience, TPRM, legal, privacy and business owners.

The Goal Is Simple: convert cyber signals into service-impact decisions and clear escalation when needed.

Start Narrow, Prove Value, Then Scale

None of this requires mapping every supplier before you begin. Start with the suppliers and dependencies that support your most critical services. Prove the approach there, then scale.

Time Frame
Action
Immediate
Define scope, critical services, ownership and data gaps
Short-term
Update policy, taxonomy, appetite, control objectives and KRI design
Medium-term
Map concentration, material subcontractors and residual risk, and build dashboards that pull in all relevant KRIs and data points
Longer-term
Establish scenario testing, response and recovery, monitoring, independent verification and effectiveness reviews.

Three Key Takeaways

1. A critical supplier list is not a resilience strategy.

2. Understanding service dependencies matters more than adding questionnaires.

3. Continuous monitoring and scenario testing reveal weaknesses that one-off assessments miss.

Find out more about the key considerations for building resilience and how Kroll can help.

Stay Ahead with Kroll

Cyber and Data Resilience

Kroll merges elite security and data risk expertise with frontline intelligence from thousands of incident responses and regulatory compliance, financial crime and due diligence engagements to make our clients more cyber- resilient.

Optimized Third-Party Cyber Risk Management Programs

Manage risk, not spreadsheets. Identify and remediate cybersecurity risks inherent in third-party relationships, helping achieve compliance with regulations such as NYDFS, FARS, GDPR, etc.