From Compliance to Resilience: Integrating Operational Risk, Service Mapping and Impact Tolerances
- Integrated frameworks require shared language, governance and reporting.
- Service mapping must connect risks, controls, dependencies and critical services.
- Testing should focus on severe, plausible disruption and cross-functional handoffs.
- Impact tolerances must reflect customer harm, market integrity and digital dependency.
- True resilience is proven through learning, adaptation and executive ownership.
What are the hallmarks of a truly integrated operational
risk and operational resilience framework, and where do organisations most
commonly struggle to align the two disciplines in practice?
A truly integrated framework features a shared risk taxonomy and a unified governance structure where Risk (2nd Line) and Resilience (1st Line) speak the exact same language. It replaces siloed reporting with a single, integrated view for the Executive Committee and Board.
Where firms struggle: The biggest friction point is the disconnect between likelihood and outcome. Traditional Operational Risk focuses heavily on loss event frequency, severity, and control assessments (asking "How likely is this?"). Resilience assumes the event has already occurred and focuses strictly on outcome-based continuity (asking "Can we absorb this disruption and protect the customer?"). Bridging these two distinct worldviews—and reconciling their underlying data models—is where most organizations get stuck.
What best practices help organisations connect governance, service mapping, risk data, and reporting into a single enterprise-wide resilience framework rather than a collection of separate activities?
Service mapping shouldn't just be an operational
exercise; it must link system dependencies and RCSA/Risk Assessment control
ratings directly to top-level Critical Business Services.
Unified Governance & Escalation: Establish a unified Risk & Resilience oversight body co-chaired by Risk and Operations. Eliminating parallel board reporting packs in favor of one narrative creates a single version of truth.
Shared Data Architecture: Instead of running duplicate records across different platforms, establish a common data repository where risk indicators, KRI breaches, and disruption metrics automatically feed into resilience dashboards
How can firms ensure that service mapping exercises translate into practical testing, scenario analysis, and war-gaming activities that genuinely improve resilience and preparedness?
Build a Connected Testing Architecture: Move away from isolated IT disaster recovery tests. Or – better yet – integrate it with a cross-functional end-to-end scenario exercises, culminating in executive-level decision making/war-gaming.
Stress the Handoffs, Not Just Systems: Disruption
rarely breaks technical systems alone; it breaks the handoffs between
Operations, Legal, Communications, Third Parties and Risk. Testing must also
include cross-functional decision-making under time pressure.
Treat Maps as Living Assets: If a service map isn't actively used to design severe-but-plausible test scenarios, it quickly becomes a historical document rather than an operational tool.
As business models become increasingly dependent on digital services, third parties, and AI, how should organisations evolve their impact tolerance frameworks to remain relevant and effective?
First - Most organizations historically built their continuity strategies around Recovery Time Objectives (RTOs)—measuring how fast technology teams can restore an internal application or server. But in an era of complex digital ecosystems, RTO is no longer sufficient.
Impact tolerance is an external, board-owned threshold that measures the point at which disruption causes intolerable harm to customers, market stability, or financial integrity. As digital reliance grows, frameworks must evolve from "When does the system come back?" to "How long can the customer go without this service before the damage is permanent?"
Looking ahead, what will distinguish organisations that are genuinely resilient from those that are simply compliant, particularly in terms of recovery planning, testing, and response capabilities?
Compliant organizations design tests they know they can pass
to satisfy an audit checklist.
Genuinely resilient organizations intentionally run scenarios that push them to the edge of—or past—their impact tolerances to discover actual failure points. Discomfort during an exercise is the primary indicator of its value to enhancing resilience
Active Executive Ownership: Compliant firms treat resilience as a lower-level operational task. Resilient firms feature active Board and C-suite participation in realistic war-games, ensuring leaders have true muscle memory when a real crisis strikes.
End-to-End Learning: The true differentiator isn't
avoiding incidents, but how seamlessly an organization coordinates,
communicates, and feeds post-incident lessons back into its risk register and
service maps.
Head of Operational Risk Management, Citi
Ron Eisenberg is a Senior Global Risk Executive with over 20 years of experience designing and maturing unified Second Line of Defense frameworks within Tier-1 financial institutions and tech-driven environments. Currently serving as the Head of Operational Risk Management (ORM) for Citibank Canada, he successfully led the Operational Risk challenge of the Operational Risk and Resiliency framework across all Canadian business lines to secure critical operations against systemic disruption. A proven "builder" and former GRC software startup founder , Ron specializes in translating rigorous regulatory expectations into scalable corporate controls, establishing cross-functional resilience governance, and driving enterprise-wide risk strategy safely.