Staying Operational: A BankTech Playbook for Uncertain Times

1 00:00:00,080 - > 00:00:02,479 SPEAKER_01: Imagine waking up tomorrow, you walk down to your 2 00:00:02,479 - > 00:00:06,400 local cafe, and you just try to buy a simple cup of coffee, you 3 00:00:06,400 - > 00:00:08,400 tap your phone, and the payment declines. 4 00:00:08,560 - > 00:00:08,720 Right. 5 00:00:08,880 - > 00:00:11,839 And it's not because, you know, your account is empty, or 6 00:00:11,839 - > 00:00:15,599 because your bank is insolvent, or facing some classic run where 7 00:00:15,599 - > 00:00:18,320 thousands of people are lined up around the block trying to 8 00:00:18,320 - > 00:00:19,280 withdraw physical cash. 9 00:00:19,679 - > 00:00:22,320 SPEAKER_00: No, there's no 1929 style panic in the streets. 10 00:00:22,640 - > 00:00:23,039 SPEAKER_01: Exactly. 11 00:00:23,280 - > 00:00:27,199 Your payment declines because a tiny, completely obscure 12 00:00:27,199 - > 00:00:29,280 software vendor halfway across the world. 13 00:00:29,760 - > 00:00:31,440 SPEAKER_00: Some company you've literally never heard of? 14 00:00:31,679 - > 00:00:31,760 SPEAKER_01: Right. 15 00:00:32,079 - > 00:00:35,759 A company that routes like a fraction of a data packet for a 16 00:00:35,759 - > 00:00:37,119 cloud server you've never heard of. 17 00:00:37,200 - > 00:00:39,840 Well, they just went offline due to a geopolitical conflict. 18 00:00:40,240 - > 00:00:40,560 Wow. 19 00:00:41,039 - > 00:00:44,079 The money is there, but the invisible pipes that move it are 20 00:00:44,079 - > 00:00:44,880 suddenly shattered. 21 00:00:44,960 - > 00:00:47,200 SPEAKER_00: Aaron Powell, which is an incredibly disorienting 22 00:00:47,200 - > 00:00:47,600 reality. 23 00:00:47,920 - > 00:00:50,799 I mean, we are culturally conditioned to think of banking 24 00:00:50,799 - > 00:00:52,240 crises in terms of liquidity, right? 25 00:00:52,320 - > 00:00:53,200 SPEAKER_01: Aaron Ross Powell Oh, totally. 26 00:00:53,520 - > 00:00:56,079 Crashing stock prices, plummeting assets. 27 00:00:56,560 - > 00:00:58,560 SPEAKER_00: Yeah, red numbers flashing on a trading floor. 28 00:00:59,039 - > 00:01:03,439 But the battlefield has um it's fundamentally shifted into the 29 00:01:03,439 - > 00:01:04,079 digital shadows. 30 00:01:04,239 - > 00:01:04,400 Trevor Burrus, Jr. 31 00:01:05,439 - > 00:01:05,920 Exactly. 32 00:01:06,239 - > 00:01:09,280 The real threat to the global financial system right now is 33 00:01:09,280 - > 00:01:10,159 entirely operational. 34 00:01:10,239 - > 00:01:12,239 SPEAKER_01: Aaron Powell And that operational threat is 35 00:01:12,239 - > 00:01:14,959 exactly what we are tearing into for today's deep dive. 36 00:01:15,040 - > 00:01:16,000 SPEAKER_00: Aaron Powell It's a big one today. 37 00:01:16,239 - > 00:01:16,879 SPEAKER_01: It really is. 38 00:01:17,200 - > 00:01:21,519 We are unpacking a highly detailed March 2026 report 39 00:01:21,519 - > 00:01:23,840 published by Cedar Management Consulting. 40 00:01:24,079 - > 00:01:28,480 It's titled Staying Operational, a Banking Technology Playbook 41 00:01:28,480 - > 00:01:29,519 for Uncertain Times. 42 00:01:29,599 - > 00:01:31,760 SPEAKER_00: Aaron Powell And this report, I mean, it drops a 43 00:01:31,760 - > 00:01:33,439 massive reality check on the industry. 44 00:01:33,519 - > 00:01:34,719 SPEAKER_01: Aaron Powell A huge one. 45 00:01:34,959 - > 00:01:37,519 It reveals how recent geopolitical developments, 46 00:01:37,680 - > 00:01:40,719 specifically the shock waves radiating out of the Middle East 47 00:01:40,719 - > 00:01:43,359 right now, are putting unprecedented strain on the 48 00:01:43,359 - > 00:01:44,560 world's financial plumbing. 49 00:01:44,640 - > 00:01:46,719 SPEAKER_00: Aaron Powell And the terrifying part is that this 50 00:01:46,719 - > 00:01:50,000 strain doesn't trigger the traditional warning lights on 51 00:01:50,000 - > 00:01:51,120 standard financial dashboards. 52 00:01:51,200 - > 00:01:52,560 SPEAKER_01: Trevor Burrus Because the standard dashboards 53 00:01:52,560 - > 00:01:53,840 are looking for the wrong kind of stress. 54 00:01:53,920 - > 00:01:54,560 SPEAKER_00: Aaron Ross Powell Exactly. 55 00:01:54,719 - > 00:01:57,359 They are measuring market volatility and capital reserves. 56 00:01:57,519 - > 00:01:57,599 Yeah. 57 00:01:57,920 - > 00:02:00,480 But the real friction is happening deep within the 58 00:02:00,480 - > 00:02:01,840 underlying digital infrastructure. 59 00:02:01,920 - > 00:02:04,400 SPEAKER_01: Trevor Burrus We are talking about that vast complex 60 00:02:04,400 - > 00:02:06,239 web of third-party dependencies. 61 00:02:06,319 - > 00:02:06,879 Trevor Burrus Right. 62 00:02:07,040 - > 00:02:08,319 SPEAKER_00: API integrations. 63 00:02:08,479 - > 00:02:12,080 And honestly, just the raw technological willpower required 64 00:02:12,080 - > 00:02:14,319 to keep cross-border financial flows moving. 65 00:02:14,400 - > 00:02:14,719 Trevor Burrus, Jr. 66 00:02:14,800 - > 00:02:17,439 SPEAKER_01: Especially when the geopolitical surface right above 67 00:02:17,439 - > 00:02:18,479 them is just fracturing. 68 00:02:19,199 - > 00:02:20,400 Okay, let's unpack this. 69 00:02:20,560 - > 00:02:23,599 Because to understand how the plumbing is breaking, we really 70 00:02:23,599 - > 00:02:26,879 have to look at how the banking sector historically designed its 71 00:02:26,879 - > 00:02:27,439 safety nets. 72 00:02:27,520 - > 00:02:29,039 SPEAKER_00: Aaron Powell Right, their whole backup plan. 73 00:02:29,280 - > 00:02:29,360 SPEAKER_01: Yeah. 74 00:02:29,680 - > 00:02:33,680 For decades, business continuity planning, or BCP, was built 75 00:02:33,680 - > 00:02:36,879 around the assumption of isolated sequential disasters. 76 00:02:36,960 - > 00:02:38,719 SPEAKER_00: Aaron Powell The traditional model was strictly 77 00:02:38,719 - > 00:02:39,039 linear. 78 00:02:39,280 - > 00:02:43,439 I mean, if a severe storm knocks out a data center in London, you 79 00:02:43,680 - > 00:02:46,080 fail over to a backup facility in Frankfurt. 80 00:02:46,479 - > 00:02:46,879 Exactly. 81 00:02:47,039 - > 00:02:50,319 Or if a specific vendor goes offline, you just switch to a 82 00:02:50,319 - > 00:02:51,360 precontracted alternate. 83 00:02:51,680 - > 00:02:52,719 SPEAKER_01: It's a one-for-one swap. 84 00:02:53,039 - > 00:02:53,199 SPEAKER_00: Right. 85 00:02:53,360 - > 00:02:56,000 The entire framework was designed under the assumption 86 00:02:56,000 - > 00:02:59,360 that the broader ecosystem remains totally stable while you 87 00:02:59,360 - > 00:03:01,280 fix one localized problem. 88 00:03:01,439 - > 00:03:04,879 You endure the event, you recover, and you return to a 89 00:03:04,879 - > 00:03:06,960 known baseline of normal operations. 90 00:03:07,280 - > 00:03:09,439 SPEAKER_01: It's like a it's like an old school municipal 91 00:03:09,439 - > 00:03:10,080 disaster plan. 92 00:03:10,400 - > 00:03:10,960 SPEAKER_00: Oh how so? 93 00:03:11,199 - > 00:03:13,520 SPEAKER_01: Well, it gives you a highly detailed checklist of 94 00:03:13,520 - > 00:03:15,680 exactly what to do if a building catches on fire. 95 00:03:16,000 - > 00:03:16,159 SPEAKER_00: Right. 96 00:03:16,240 - > 00:03:17,199 Step one, step two? 97 00:03:17,520 - > 00:03:18,159 SPEAKER_01: Exactly. 98 00:03:18,319 - > 00:03:22,159 But that manual completely falls apart if there's a fire and a 99 00:03:22,159 - > 00:03:25,599 massive flood and a coordinated cyber attack on the fire 100 00:03:25,599 - > 00:03:28,560 department's dispatch system all happening at the exact same 101 00:03:28,560 - > 00:03:28,719 time. 102 00:03:29,199 - > 00:03:29,520 SPEAKER_00: Wow. 103 00:03:29,680 - > 00:03:30,240 Yeah. 104 00:03:30,479 - > 00:03:32,879 The manual assumes you only have to fight one enemy. 105 00:03:33,199 - > 00:03:33,680 SPEAKER_01: Right. 106 00:03:34,000 - > 00:03:36,719 SPEAKER_00: What's fascinating here is that the CEDA report 107 00:03:36,719 - > 00:03:39,039 actually mathematically proves this shift. 108 00:03:39,360 - > 00:03:39,840 SPEAKER_01: Oh, really? 109 00:03:40,159 - > 00:03:40,479 SPEAKER_00: Yeah. 110 00:03:40,719 - > 00:03:44,560 The defining characteristic of the 2026 operational landscape 111 00:03:44,560 - > 00:03:48,879 isn't the introduction of new risks, it is the sheer speed and 112 00:03:48,879 - > 00:03:50,400 convergence of existing threats. 113 00:03:50,800 - > 00:03:51,360 SPEAKER_01: Convergence. 114 00:03:51,439 - > 00:03:52,479 They're all happening at once. 115 00:03:52,800 - > 00:03:53,280 SPEAKER_00: Exactly. 116 00:03:53,520 - > 00:03:56,560 Banks are currently facing elevated, highly coordinated 117 00:03:56,560 - > 00:03:59,039 cyber activity at the exact same moment. 118 00:03:59,199 - > 00:04:01,919 Their physical infrastructure is under threat from geopolitical 119 00:04:01,919 - > 00:04:02,080 tension. 120 00:04:02,159 - > 00:04:03,919 SPEAKER_01: Aaron Powell And then you add in global supply 121 00:04:03,919 - > 00:04:04,560 chain disruptions. 122 00:04:05,039 - > 00:04:06,400 SPEAKER_00: Right, which prevents the delivery of 123 00:04:06,400 - > 00:04:09,280 critical networking hardware, and you top it all off with 124 00:04:09,280 - > 00:04:11,039 rapidly evolving regulatory sanctions. 125 00:04:11,360 - > 00:04:13,360 SPEAKER_01: So the threats act as multipliers for each other. 126 00:04:13,680 - > 00:04:14,479 SPEAKER_00: You absolutely do. 127 00:04:14,800 - > 00:04:18,160 SPEAKER_01: Like a cyberattack on a logistics port delays the 128 00:04:18,160 - > 00:04:20,879 shipment of servers you desperately need to upgrade a 129 00:04:20,879 - > 00:04:21,360 data center. 130 00:04:21,439 - > 00:04:23,519 SPEAKER_00: Aaron Powell A data center that is currently 131 00:04:23,519 - > 00:04:26,720 buckling under a surge of panicked customer traffic. 132 00:04:27,040 - > 00:04:27,199 SPEAKER_01: Right. 133 00:04:27,519 - > 00:04:30,480 SPEAKER_00: Which means traditional BCP is effectively 134 00:04:30,480 - > 00:04:31,199 obsolete. 135 00:04:31,680 - > 00:04:34,319 The risk is no longer linear, it's exponential. 136 00:04:34,399 - > 00:04:36,560 SPEAKER_01: Aaron Powell So how do banks even handle that? 137 00:04:36,639 - > 00:04:38,160 SPEAKER_00: Aaron Ross Powell Well, the report says it 138 00:04:38,160 - > 00:04:40,639 requires a fundamental restructuring of how 139 00:04:40,639 - > 00:04:42,240 institutions govern themselves. 140 00:04:42,879 - > 00:04:46,959 They are adamant that the first step to survival is elevating 141 00:04:46,959 - > 00:04:49,920 technology risk out of the IT department and planting it 142 00:04:49,920 - > 00:04:50,879 directly into the boardroom. 143 00:04:51,199 - > 00:04:52,160 SPEAKER_01: Strategic governance. 144 00:04:52,480 - > 00:04:52,800 SPEAKER_00: Exactly. 145 00:04:53,040 - > 00:04:55,360 Strategic governance has to change before the conditions 146 00:04:55,360 - > 00:04:55,759 demand it. 147 00:04:56,000 - > 00:04:57,279 SPEAKER_01: But I want to push on that a bit. 148 00:04:57,439 - > 00:05:00,319 Strategic governance sounds great in a corporate memo, 149 00:05:00,399 - > 00:05:00,480 right? 150 00:05:00,720 - > 00:05:01,199 SPEAKER_00: Oh, sure. 151 00:05:01,439 - > 00:05:03,600 SPEAKER_01: But what does that actually look like in practice? 152 00:05:03,759 - > 00:05:07,279 I mean, if a board is largely made up of finance experts and 153 00:05:07,279 - > 00:05:10,720 former CEOs, how do they suddenly grasp the existential 154 00:05:10,720 - > 00:05:12,800 threat of interconnected digital plumbing? 155 00:05:12,959 - > 00:05:15,040 SPEAKER_00: Aaron Powell Well, it requires translating deeply 156 00:05:15,199 - > 00:05:17,839 technical exposures into immediate business consequences. 157 00:05:18,639 - > 00:05:24,800 So a board might not understand the intricacies of like a BGP 158 00:05:24,800 - > 00:05:25,680 routing vulnerability. 159 00:05:26,000 - > 00:05:26,639 SPEAKER_01: Most people don't. 160 00:05:26,959 - > 00:05:27,519 SPEAKER_00: Right. 161 00:05:27,839 - > 00:05:31,360 But they absolutely understand when you tell them if this 162 00:05:31,360 - > 00:05:35,279 specific digital corridor goes down, we lose the ability to 163 00:05:35,279 - > 00:05:38,319 process$80 million in cross-border trade tomorrow 164 00:05:38,319 - > 00:05:38,560 morning. 165 00:05:38,800 - > 00:05:39,279 SPEAKER_01: Oh yeah. 166 00:05:39,360 - > 00:05:40,160 That gets their attention. 167 00:05:40,480 - > 00:05:42,639 SPEAKER_00: And we will be legally liable for the failed 168 00:05:42,639 - > 00:05:42,959 settlements. 169 00:05:43,279 - > 00:05:44,480 SPEAKER_01: Yeah, that translates it perfectly. 170 00:05:44,800 - > 00:05:47,279 SPEAKER_00: The governance model has to match the reality of the 171 00:05:47,279 - > 00:05:47,759 threat. 172 00:05:47,920 - > 00:05:52,160 And that means leadership needs structured, scenario-based 173 00:05:52,160 - > 00:05:55,360 briefings that map these simultaneous stress tests before 174 00:05:55,360 - > 00:05:55,839 they happen. 175 00:05:55,920 - > 00:05:58,480 SPEAKER_01: Aaron Powell So if the board finally grasps that 176 00:05:58,480 - > 00:06:01,680 this interconnected web is fragile, where do they look 177 00:06:01,680 - > 00:06:01,920 first? 178 00:06:02,240 - > 00:06:04,879 What's the first piece of plumbing that actually bursts 179 00:06:04,879 - > 00:06:05,839 when the pressure builds? 180 00:06:05,920 - > 00:06:07,759 SPEAKER_00: Aaron Ross Powell The report points directly at 181 00:06:07,759 - > 00:06:09,600 the payments and transaction infrastructure. 182 00:06:09,680 - > 00:06:10,720 SPEAKER_01: Trevor Burrus The money moving. 183 00:06:11,120 - > 00:06:11,360 SPEAKER_00: Right. 184 00:06:11,519 - > 00:06:14,480 Specifically mapping out how international money movement is 185 00:06:14,480 - > 00:06:15,759 cracking under this pressure. 186 00:06:16,399 - > 00:06:19,759 Payments are the ultimate unforgiving litmus test of 187 00:06:19,759 - > 00:06:20,560 operational reality. 188 00:06:20,879 - > 00:06:22,319 SPEAKER_01: Unforgiving is a good word for it. 189 00:06:22,639 - > 00:06:24,639 SPEAKER_00: Especially in the Middle East right now, where 190 00:06:24,639 - > 00:06:28,480 cross-border flows and complex trade corridors are the absolute 191 00:06:28,480 - > 00:06:30,720 lifeblood of the regional economy. 192 00:06:31,040 - > 00:06:34,879 When the system is stressed, cross-border payment timelines 193 00:06:34,879 - > 00:06:35,759 begin to stretch. 194 00:06:36,079 - > 00:06:36,959 SPEAKER_01: They bottleneck. 195 00:06:37,360 - > 00:06:39,279 SPEAKER_00: Remittance corridors bottleneck, yeah. 196 00:06:39,680 - > 00:06:42,319 And for an exchange settlement, which is supposed to happen 197 00:06:42,319 - > 00:06:45,120 almost instantly in the background, well, it becomes 198 00:06:45,120 - > 00:06:46,319 incredibly complex. 199 00:06:46,720 - > 00:06:48,639 SPEAKER_01: And let's look at the mechanism driving that 200 00:06:48,639 - > 00:06:49,040 friction. 201 00:06:49,439 - > 00:06:52,160 The report highlights the strain on correspondent banking and 202 00:06:52,160 - > 00:06:53,279 Swift connectivity. 203 00:06:53,360 - > 00:06:54,800 SPEAKER_00: Aaron Powell Yeah, this is a huge point. 204 00:06:55,279 - > 00:06:56,800 SPEAKER_01: Now most people listening know that 205 00:06:56,800 - > 00:06:59,920 correspondent banking requires banks to essentially trust each 206 00:06:59,920 - > 00:07:03,199 other to hold accounts and process localized payments on 207 00:07:03,199 - > 00:07:03,600 their behalf. 208 00:07:03,680 - > 00:07:04,079 SPEAKER_00: Aaron Powell Right. 209 00:07:04,160 - > 00:07:04,879 It runs on trust. 210 00:07:05,279 - > 00:07:08,079 SPEAKER_01: But what the report explains is why this breaks down 211 00:07:08,079 - > 00:07:10,079 during a geopolitical crisis. 212 00:07:10,240 - > 00:07:12,720 It's not just that the wires physically get cut. 213 00:07:13,120 - > 00:07:15,279 SPEAKER_00: No, it's that the algorithmic trust evaporates. 214 00:07:15,680 - > 00:07:16,399 SPEAKER_01: Wait, explain that. 215 00:07:16,720 - > 00:07:19,360 SPEAKER_00: So the mechanism of failure here is driven by risk 216 00:07:19,360 - > 00:07:20,000 aversion. 217 00:07:20,160 - > 00:07:23,120 In stable times, a correspondent bank automatically routes 218 00:07:23,120 - > 00:07:25,920 millions of transactions based on established baselines of 219 00:07:25,920 - > 00:07:26,160 trust. 220 00:07:26,560 - > 00:07:28,879 SPEAKER_01: It's just algorithms talking to algorithms. 221 00:07:29,279 - > 00:07:29,680 SPEAKER_00: Exactly. 222 00:07:29,839 - > 00:07:33,680 But the second a geopolitical conflict erupts, that baseline 223 00:07:33,680 - > 00:07:34,319 shifts. 224 00:07:34,560 - > 00:07:36,800 Intermediary banks suddenly get spooked. 225 00:07:37,120 - > 00:07:38,240 SPEAKER_01: Their systems freak out. 226 00:07:38,560 - > 00:07:41,839 SPEAKER_00: Their systems stop automatically routing money and 227 00:07:41,839 - > 00:07:46,160 start flagging massive volumes of transactions for manual 228 00:07:46,160 - > 00:07:47,040 compliance reviews. 229 00:07:47,360 - > 00:07:50,079 SPEAKER_01: Manual reviews for millions of transactions. 230 00:07:50,399 - > 00:07:50,560 SPEAKER_00: Yeah. 231 00:07:50,720 - > 00:07:53,199 And they demand immediate prefunding for accounts that 232 00:07:53,199 - > 00:07:54,560 previously operated on credit. 233 00:07:54,800 - > 00:07:55,040 SPEAKER_01: Wow. 234 00:07:55,279 - > 00:07:57,439 So the friction isn't always a broken pipe. 235 00:07:57,759 - > 00:07:58,000 SPEAKER_00: No. 236 00:07:58,319 - > 00:08:00,800 SPEAKER_01: Sometimes the friction is the system actively 237 00:08:00,800 - > 00:08:03,040 deciding to freeze the water just to be safe. 238 00:08:03,439 - > 00:08:04,720 SPEAKER_00: That is exactly what happens. 239 00:08:04,959 - > 00:08:08,480 Interbank routing requires pre-tested contingency protocols 240 00:08:08,639 - > 00:08:11,680 because you can no longer assume your correspondent partner will 241 00:08:11,680 - > 00:08:13,680 actually accept your digital handshake tomorrow. 242 00:08:14,079 - > 00:08:17,519 SPEAKER_01: And this demand for absolute real-time visibility 243 00:08:17,519 - > 00:08:19,759 falls squarely on the shoulders of treasury desks. 244 00:08:19,839 - > 00:08:21,199 SPEAKER_00: Aaron Powell And capital markets, yeah. 245 00:08:21,519 - > 00:08:23,759 They have to manage trade finance platforms under 246 00:08:23,759 - > 00:08:26,879 concurrent demand, knowing that the pathways they rely on could 247 00:08:26,879 - > 00:08:28,399 close at literally any second. 248 00:08:28,480 - > 00:08:29,759 SPEAKER_01: Aaron Powell Here's where it gets really 249 00:08:29,759 - > 00:08:30,319 interesting. 250 00:08:30,560 - > 00:08:33,840 I want to bring up the data and cloud section of the CEDAR 251 00:08:33,840 - > 00:08:37,600 report because it completely shatters a massive tech industry 252 00:08:37,600 - > 00:08:37,840 narrative. 253 00:08:38,240 - > 00:08:38,720 SPEAKER_00: It really does. 254 00:08:39,039 - > 00:08:40,960 SPEAKER_01: The report explicitly states that the 255 00:08:40,960 - > 00:08:44,240 assumption that cloud hosting provides inherent insulation 256 00:08:44,240 - > 00:08:47,440 from disruption has been tested and found incomplete. 257 00:08:47,840 - > 00:08:49,279 SPEAKER_00: Tested and found incomplete, yes. 258 00:08:49,600 - > 00:08:52,480 SPEAKER_01: But wait a minute, isn't the entire multi-billion 259 00:08:52,480 - > 00:08:56,720 dollar sales pitch of the cloud that it is a decentralized, 260 00:08:56,799 - > 00:08:57,840 bulletproof backup? 261 00:08:58,080 - > 00:08:59,039 SPEAKER_00: That's the marketing, sure. 262 00:08:59,279 - > 00:09:02,639 SPEAKER_01: Like if an entire server farm in one country goes 263 00:09:02,639 - > 00:09:06,159 dark, another one seamlessly takes over without dropping a 264 00:09:06,159 - > 00:09:06,799 single packet. 265 00:09:07,120 - > 00:09:09,519 SPEAKER_00: Well, if we connect this to the bigger picture, we 266 00:09:09,519 - > 00:09:11,360 see the flaw in that promise. 267 00:09:11,600 - > 00:09:14,720 The cloud itself, like the massive data centers owned by 268 00:09:14,720 - > 00:09:17,759 the tech giants, might be incredibly resilient. 269 00:09:18,000 - > 00:09:18,320 Right. 270 00:09:18,559 - > 00:09:21,600 But your bank's operational continuity is only as strong as 271 00:09:21,600 - > 00:09:23,440 its unmapped vendor dependencies. 272 00:09:23,759 - > 00:09:25,919 SPEAKER_01: Break down unmapped vendor dependencies. 273 00:09:26,080 - > 00:09:27,120 How hidden are we talking? 274 00:09:27,360 - > 00:09:29,600 SPEAKER_00: Like of it as a nesting doll of vulnerabilities. 275 00:09:29,840 - > 00:09:33,519 Your bank might use a highly secure top-tier cloud provider, 276 00:09:33,759 - > 00:09:38,399 but to run your specific banking application on that cloud, you 277 00:09:38,720 - > 00:09:43,279 utilize a specialized third-party vendor for, say, a 278 00:09:43,279 - > 00:09:44,480 data analytics function. 279 00:09:44,720 - > 00:09:44,879 SPEAKER_01: Right. 280 00:09:45,120 - > 00:09:47,759 SPEAKER_00: That third-party vendor, unbeknownst to you, 281 00:09:48,000 - > 00:09:52,080 relies on a fourth-party supplier for a critical API that 282 00:09:52,080 - > 00:09:53,679 handles identity verification. 283 00:09:53,919 - > 00:09:54,559 SPEAKER_01: Oh no. 284 00:09:54,879 - > 00:09:56,799 SPEAKER_00: And that fourth party supplier has their 285 00:09:56,799 - > 00:09:59,840 physical infrastructure located in a region that just 286 00:09:59,840 - > 00:10:02,399 experienced a severe geopolitical disruption. 287 00:10:02,799 - > 00:10:04,559 SPEAKER_01: Because the top-tier cloud provider is perfectly 288 00:10:04,559 - > 00:10:04,720 fine. 289 00:10:05,039 - > 00:10:06,320 SPEAKER_00: Running at 100% capacity. 290 00:10:06,639 - > 00:10:09,360 SPEAKER_01: But the tiny crucial gears running inside it just 291 00:10:09,360 - > 00:10:09,919 seized up. 292 00:10:10,240 - > 00:10:10,559 SPEAKER_00: Exactly. 293 00:10:10,720 - > 00:10:13,759 Single points of failure almost always sit well beyond your 294 00:10:13,759 - > 00:10:14,559 formal vendor list. 295 00:10:14,879 - > 00:10:15,679 SPEAKER_01: The unmapped ones. 296 00:10:16,000 - > 00:10:16,159 SPEAKER_00: Right. 297 00:10:16,399 - > 00:10:18,639 The report stresses that dependencies that were never 298 00:10:18,639 - > 00:10:21,919 formally mapped out or audited are suddenly carrying direct 299 00:10:21,919 - > 00:10:22,960 operational consequences. 300 00:10:23,759 - > 00:10:26,960 When that fourth party API times out, your mobile banking app 301 00:10:26,960 - > 00:10:27,519 crashes. 302 00:10:27,679 - > 00:10:29,759 Even though your primary servers are totally fine. 303 00:10:30,080 - > 00:10:31,600 SPEAKER_01: It's like installing a state-of-the-art 304 00:10:31,840 - > 00:10:34,960 military-grade security system on your house, complete with 305 00:10:34,960 - > 00:10:36,799 backup batteries and encrypted feeds. 306 00:10:36,960 - > 00:10:40,559 But you didn't realize that the system's central processor 307 00:10:40,559 - > 00:10:44,559 relies on a continuous Wi-Fi signal from your neighbor's 308 00:10:44,559 - > 00:10:46,879 incredibly cheap faulty router. 309 00:10:47,200 - > 00:10:47,440 SPEAKER_00: Yes. 310 00:10:47,679 - > 00:10:50,240 SPEAKER_01: When their router reboots, your entire fortress 311 00:10:50,240 - > 00:10:50,559 shuts down. 312 00:10:50,879 - > 00:10:52,000 SPEAKER_00: That is a perfect analogy. 313 00:10:52,320 - > 00:10:54,960 And the current geopolitical environment is mercilessly 314 00:10:54,960 - > 00:10:56,480 exposing all of those hidden routers. 315 00:10:56,879 - > 00:11:00,559 SPEAKER_01: So we have this invisible back-end plumbing, the 316 00:11:00,559 - > 00:11:04,399 cross-border routing delays, the evaporating correspondent trust, 317 00:11:04,480 - > 00:11:06,399 the unmapped fourth-party cloud dependencies. 318 00:11:09,600 - > 00:11:09,759 Right. 319 00:11:10,000 - > 00:11:13,039 But let's shift to the visible front-end reality. 320 00:11:13,279 - > 00:11:17,600 How do these systemic abstract technology risks directly impact 321 00:11:17,600 - > 00:11:18,159 human behavior? 322 00:11:18,480 - > 00:11:18,960 SPEAKER_00: Oh, deeply. 323 00:11:19,279 - > 00:11:21,519 SPEAKER_01: Because the CETA report dives deep into the 324 00:11:21,519 - > 00:11:24,159 intense pressure placed on digital channels and customer 325 00:11:24,159 - > 00:11:25,840 service during these geopolitical shocks. 326 00:11:26,320 - > 00:11:28,559 SPEAKER_00: The translation from back-end latency to frontline 327 00:11:28,720 - > 00:11:30,080 panic happens almost instantly. 328 00:11:30,320 - > 00:11:30,879 I'm sure it does. 329 00:11:31,200 - > 00:11:34,399 In times of profound uncertainty, whether it's rumors 330 00:11:34,399 - > 00:11:37,679 of a conflict escalating or sudden economic sanctions being 331 00:11:37,679 - > 00:11:40,159 announced, customers crave reassurance. 332 00:11:40,320 - > 00:11:43,039 Their immediate reflex is to check their balances. 333 00:11:43,200 - > 00:11:46,559 So they flood their bank's mobile app and online portals. 334 00:11:46,879 - > 00:11:48,960 SPEAKER_01: And if that app is down because of a hidden 335 00:11:48,960 - > 00:11:52,320 fourth-party API failure, the customer doesn't know about the 336 00:11:52,320 - > 00:11:52,799 API. 337 00:11:53,039 - > 00:11:54,159 SPEAKER_00: They don't care about the API. 338 00:11:54,480 - > 00:11:55,039 SPEAKER_01: Exactly. 339 00:11:55,279 - > 00:11:58,240 They just see a loading screen that eventually times out. 340 00:11:58,399 - > 00:12:02,559 And in a crisis, a timed-out app is the modern-day equivalent of 341 00:12:02,559 - > 00:12:05,840 walking up to your local bank branch and finding the heavy 342 00:12:05,840 - > 00:12:08,960 steel doors padlocked shut with no explanation. 343 00:12:09,360 - > 00:12:10,000 SPEAKER_00: It really is. 344 00:12:10,159 - > 00:12:12,159 And the report is definitive on this. 345 00:12:12,320 - > 00:12:15,519 In the modern era, platform availability is institutional 346 00:12:15,519 - > 00:12:16,000 credibility. 347 00:12:16,320 - > 00:12:19,120 SPEAKER_01: If the app is down, the psychological jump for the 348 00:12:19,120 - > 00:12:20,000 customer is immediate. 349 00:12:20,320 - > 00:12:20,480 SPEAKER_00: Right. 350 00:12:20,559 - > 00:12:21,919 They don't assume a routing glitch. 351 00:12:22,000 - > 00:12:23,039 They assume the bank is insolvent. 352 00:12:23,440 - > 00:12:26,320 SPEAKER_01: Which forces banks to actively review platform 353 00:12:26,320 - > 00:12:29,759 stability and vastly expand service desk capacity. 354 00:12:30,080 - > 00:12:32,559 SPEAKER_00: And engineer proactive customer communication 355 00:12:32,559 - > 00:12:35,360 strategies that get ahead of outages before the rumor mill 356 00:12:35,519 - > 00:12:35,759 starts. 357 00:12:36,080 - > 00:12:38,320 SPEAKER_01: But while millions of anxious customers are 358 00:12:38,320 - > 00:12:41,279 legitimately trying to log in and check their savings, the 359 00:12:41,279 - > 00:12:44,000 ecosystem is being flooded by something else entirely. 360 00:12:44,240 - > 00:12:44,879 SPEAKER_00: Bad actors. 361 00:12:45,120 - > 00:12:46,080 SPEAKER_01: Bad actors. 362 00:12:46,320 - > 00:12:50,720 The report tracks a severe, measurable spike in fraud and 363 00:12:50,720 - > 00:12:53,679 social engineering OBMs during these exact periods of 364 00:12:53,679 - > 00:12:54,320 volatility. 365 00:12:54,639 - > 00:12:56,879 SPEAKER_00: This raises an important question about how our 366 00:12:56,879 - > 00:12:58,639 defensive systems are built. 367 00:12:58,960 - > 00:13:02,799 Organized threat actors know that during a crisis, attention 368 00:13:02,799 - > 00:13:03,440 is fractured. 369 00:13:03,679 - > 00:13:04,000 SPEAKER_01: Right. 370 00:13:04,159 - > 00:13:05,200 Everyone's distracted. 371 00:13:05,440 - > 00:13:08,159 SPEAKER_00: Bank staff are overwhelmed trying to maintain 372 00:13:08,159 - > 00:13:11,759 basic operations, and customers are highly susceptible to 373 00:13:11,759 - > 00:13:14,080 deception because they are operating out of fear. 374 00:13:14,320 - > 00:13:15,840 SPEAKER_01: Panic makes people vulnerable. 375 00:13:16,080 - > 00:13:18,799 SPEAKER_00: A panicked customer is far more likely to fall for a 376 00:13:18,799 - > 00:13:22,159 phishing email claiming their funds are about to be frozen and 377 00:13:22,159 - > 00:13:24,000 need to be transferred to a safe account. 378 00:13:24,320 - > 00:13:26,960 SPEAKER_01: Which creates an absolute nightmare scenario for 379 00:13:26,960 - > 00:13:28,879 the bank's automated fraud detection system. 380 00:13:29,200 - > 00:13:30,080 Oh, the total nightmare. 381 00:13:30,320 - > 00:13:33,360 Think about the mechanism of how fraud algorithms work. 382 00:13:33,600 - > 00:13:35,759 They are trained to look for anomalies, right? 383 00:13:36,000 - > 00:13:38,480 Deviations from a baseline of normal behavior. 384 00:13:38,720 - > 00:13:42,159 It's like a highly sensitive car alarm that's calibrated to go 385 00:13:42,159 - > 00:13:44,159 off if someone breaks a window. 386 00:13:44,399 - > 00:13:47,279 But suddenly a geopolitical hurricane hits. 387 00:13:47,519 - > 00:13:51,440 The wind is rattling every single window, so the alarm is 388 00:13:51,440 - > 00:13:54,720 just screaming nonstop, and you have absolutely no idea if it's 389 00:13:54,720 - > 00:13:57,200 the storm or an actual burglar breaking in. 390 00:13:57,600 - > 00:13:58,799 SPEAKER_00: That is exactly what happens. 391 00:13:58,960 - > 00:14:02,559 The baseline for normal is completely obliterated. 392 00:14:02,720 - > 00:14:06,159 During a crisis, legitimate customers start acting 393 00:14:06,159 - > 00:14:06,559 erratically. 394 00:14:06,799 - > 00:14:08,240 SPEAKER_01: They move large sums of money around. 395 00:14:08,559 - > 00:14:08,720 SPEAKER_00: Right. 396 00:14:08,879 - > 00:14:12,240 They log in from unusual IP addresses if they are fleeing a 397 00:14:12,240 - > 00:14:12,559 region. 398 00:14:12,720 - > 00:14:16,080 They wire funds to relatives across borders at three in the 399 00:14:16,080 - > 00:14:16,159 morning. 400 00:14:16,480 - > 00:14:18,399 SPEAKER_01: And to the algorithm, this looks exactly 401 00:14:18,399 - > 00:14:18,879 like fraud. 402 00:14:19,279 - > 00:14:20,879 SPEAKER_00: To the algorithm, they are all burglars. 403 00:14:21,200 - > 00:14:23,519 SPEAKER_01: So the bank is trapped in a mathematical 404 00:14:23,519 - > 00:14:23,759 dilemma. 405 00:14:24,159 - > 00:14:24,879 SPEAKER_00: A severe one. 406 00:14:25,039 - > 00:14:27,759 If they don't recalibrate their fraud detection rules on the 407 00:14:27,759 - > 00:14:29,440 fly, one of two things happens. 408 00:14:29,759 - > 00:14:29,919 SPEAKER_01: Okay. 409 00:14:30,080 - > 00:14:30,799 What are the options? 410 00:14:31,039 - > 00:14:32,799 SPEAKER_00: Either they loosen the rules and hemorrhage 411 00:14:33,039 - > 00:14:35,600 millions of dollars to opportunistic cybercriminals. 412 00:14:35,759 - > 00:14:36,399 SPEAKER_01: Yikes. 413 00:14:36,720 - > 00:14:39,200 SPEAKER_00: Or they keep the rules tight and trigger massive 414 00:14:39,200 - > 00:14:39,759 false positives. 415 00:14:40,080 - > 00:14:42,720 SPEAKER_01: And a false positive means freezing an innocent 416 00:14:42,720 - > 00:14:43,360 person's account. 417 00:14:43,679 - > 00:14:44,480 SPEAKER_00: Exactly. 418 00:14:44,799 - > 00:14:48,639 A false positive means the algorithm freezes the account of 419 00:14:48,639 - > 00:14:52,159 a panicked mother trying to legitimately wire money to her 420 00:14:52,159 - > 00:14:52,799 stranded child. 421 00:14:53,120 - > 00:14:54,080 SPEAKER_01: Oh, wow. 422 00:14:54,480 - > 00:14:57,759 That creates a catastrophic public relations crisis on top 423 00:14:57,759 - > 00:14:58,639 of the operational one. 424 00:14:59,039 - > 00:14:59,360 SPEAKER_00: Exactly. 425 00:14:59,519 - > 00:15:02,320 And while the tech teams are frantically trying to tune the 426 00:15:02,320 - > 00:15:05,600 fraud dials, the compliance teams are dealing with the 427 00:15:05,600 - > 00:15:08,159 absolute whiplash of international sanctions. 428 00:15:08,480 - > 00:15:08,720 SPEAKER_01: Right. 429 00:15:08,799 - > 00:15:11,840 Because during geopolitical conflicts, global regulators do 430 00:15:11,840 - > 00:15:12,399 not pause. 431 00:15:12,799 - > 00:15:14,240 SPEAKER_00: No, they accelerate. 432 00:15:14,399 - > 00:15:17,120 The velocity of regulatory change during these periods is 433 00:15:17,120 - > 00:15:17,519 staggering. 434 00:15:17,840 - > 00:15:19,360 SPEAKER_01: Sanctions lists update constantly. 435 00:15:19,679 - > 00:15:20,080 SPEAKER_00: Constantly. 436 00:15:20,240 - > 00:15:24,080 A bank's compliance technology must be incredibly agile to 437 00:15:24,080 - > 00:15:27,279 ingest and apply rapid updates to international sanctions 438 00:15:27,279 - > 00:15:27,759 databases. 439 00:15:28,080 - > 00:15:30,320 SPEAKER_01: Without causing massive bottlenecks in payment 440 00:15:30,320 - > 00:15:30,639 processing. 441 00:15:30,879 - > 00:15:31,039 SPEAKER_00: Right. 442 00:15:31,279 - > 00:15:32,720 SPEAKER_01: The mechanism here is brutal. 443 00:15:32,879 - > 00:15:36,799 If your compliance API takes, say, 24 hours to sync with the 444 00:15:36,799 - > 00:15:39,840 newly published sanctions list, and you accidentally process a 445 00:15:39,840 - > 00:15:42,960 multimillion dollar trade for an entity that was sanctioned 15 446 00:15:42,960 - > 00:15:43,360 minutes ago. 447 00:15:43,679 - > 00:15:44,879 SPEAKER_00: Your bank is legally liable. 448 00:15:45,120 - > 00:15:48,399 SPEAKER_01: But if you pause all transactions to manually check 449 00:15:48,399 - > 00:15:52,320 the new lists, you bring regional commerce to a grinding 450 00:15:52,320 - > 00:15:52,559 halt. 451 00:15:52,960 - > 00:15:56,000 SPEAKER_00: The margin for error drops to zero at the exact 452 00:15:56,000 - > 00:15:57,919 moment the complexity reaches its peak. 453 00:15:58,240 - > 00:15:59,679 SPEAKER_01: So what does this all mean? 454 00:15:59,840 - > 00:16:02,879 We've painted a picture of a battlefield where the backups 455 00:16:02,879 - > 00:16:05,919 are outdated, the international payment routes are heavily 456 00:16:05,919 - > 00:16:09,840 restricted by fear, the cloud is vulnerable to hidden failures. 457 00:16:10,159 - > 00:16:12,639 SPEAKER_00: The customers are panicking, algorithms are 458 00:16:12,639 - > 00:16:14,159 freezing legitimate accounts. 459 00:16:14,480 - > 00:16:16,399 SPEAKER_01: And regulators are updating the rules by the 460 00:16:16,399 - > 00:16:16,720 minute. 461 00:16:16,879 - > 00:16:20,559 How do the banks that actually survive this pressure operate? 462 00:16:20,960 - > 00:16:23,679 SPEAKER_00: Well, the CEDA report provides a 10-point 463 00:16:23,679 - > 00:16:27,120 technology leadership playbook for moving from reactive panic 464 00:16:27,120 - > 00:16:28,960 to what they call a structural advantage. 465 00:16:29,279 - > 00:16:31,360 SPEAKER_01: Let's look at the critical steps in this playbook. 466 00:16:31,600 - > 00:16:34,720 They emphasize mapping every single vendor dependency, right? 467 00:16:35,279 - > 00:16:37,919 SPEAKER_00: Going three or four levels deep to find those hidden 468 00:16:37,919 - > 00:16:38,480 points of failure. 469 00:16:38,799 - > 00:16:40,080 SPEAKER_01: The fourth party routers. 470 00:16:40,399 - > 00:16:40,799 SPEAKER_00: Exactly. 471 00:16:40,960 - > 00:16:44,960 They also mandate stress testing for simultaneous overlapping 472 00:16:44,960 - > 00:16:45,360 disasters. 473 00:16:45,679 - > 00:16:46,639 SPEAKER_01: Not sequential ones. 474 00:16:46,960 - > 00:16:47,200 SPEAKER_00: Right. 475 00:16:47,360 - > 00:16:50,080 And they require securing payment rails and tightening 476 00:16:50,080 - > 00:16:53,679 compliance tech to absorb sanctions changes in real time. 477 00:16:53,759 - > 00:16:56,000 SPEAKER_01: Aaron Powell Okay, but I really want to zero in on 478 00:16:56,000 - > 00:16:58,320 point number eight in their playbook because it seems 479 00:16:58,320 - > 00:16:59,519 entirely counterintuitive. 480 00:16:59,919 - > 00:17:01,360 SPEAKER_00: Oh, I know which one you're talking about. 481 00:17:01,519 - > 00:17:02,879 Accelerate key projects. 482 00:17:03,200 - > 00:17:03,440 SPEAKER_01: Yes. 483 00:17:03,679 - > 00:17:04,960 And I have to push back hard on this. 484 00:17:05,279 - > 00:17:05,519 SPEAKER_00: Go ahead. 485 00:17:05,759 - > 00:17:08,000 SPEAKER_01: Wait, you're telling me that while my cross-border 486 00:17:08,000 - > 00:17:11,039 supply chains are breaking, my correspondent trust is 487 00:17:11,039 - > 00:17:14,000 evaporating, and my cloud providers are facing 488 00:17:14,000 - > 00:17:15,359 fourth-party outages? 489 00:17:15,599 - > 00:17:15,839 Right. 490 00:17:16,079 - > 00:17:20,000 My board should be approving a multi-million dollar AI 491 00:17:20,000 - > 00:17:21,039 infrastructure upgrade. 492 00:17:21,359 - > 00:17:22,319 SPEAKER_00: That is what they recommend. 493 00:17:22,640 - > 00:17:24,960 SPEAKER_01: How does any CEO stand in front of nervous 494 00:17:25,119 - > 00:17:28,480 shareholders and justify accelerating massive tech 495 00:17:28,480 - > 00:17:30,160 spending during a crisis? 496 00:17:30,400 - > 00:17:34,240 Shouldn't they batten down the hatches, freeze all nonessential 497 00:17:34,319 - > 00:17:36,559 budgets, and just focus on survival? 498 00:17:36,960 - > 00:17:39,519 SPEAKER_00: That instinct to pause, to freeze budgets and 499 00:17:39,519 - > 00:17:42,720 wait for the dust to settle is exactly what destroys long-term 500 00:17:42,720 - > 00:17:42,880 value. 501 00:17:43,200 - > 00:17:43,599 SPEAKER_01: Wait, really? 502 00:17:43,839 - > 00:17:44,319 SPEAKER_00: Yes. 503 00:17:44,559 - > 00:17:48,400 The CEDAR report highlights this as the most crucial conceptual 504 00:17:48,400 - > 00:17:50,319 shift for executive leadership. 505 00:17:50,640 - > 00:17:53,920 Deep uncertainty is not a reason to pause. 506 00:17:54,240 - > 00:17:56,720 It is a mandate to move aggressively on 507 00:17:56,720 - > 00:17:58,079 resilience-building projects. 508 00:17:58,480 - > 00:18:00,480 SPEAKER_01: What is the mechanism behind that logic? 509 00:18:00,640 - > 00:18:02,640 Why spend when everything is burning? 510 00:18:03,119 - > 00:18:05,680 SPEAKER_00: Because the underlying assumption of waiting 511 00:18:05,680 - > 00:18:07,920 for the dust to settle is flawed. 512 00:18:08,160 - > 00:18:10,559 The dust might not settle for a decade. 513 00:18:10,799 - > 00:18:11,359 SPEAKER_01: Wow. 514 00:18:11,599 - > 00:18:13,440 SPEAKER_00: The baseline operating environment has 515 00:18:13,440 - > 00:18:14,480 permanently changed. 516 00:18:14,640 - > 00:18:17,039 Geopolitical volatility is the new normal. 517 00:18:17,359 - > 00:18:18,720 SPEAKER_01: So if you freeze your upgrades. 518 00:18:19,119 - > 00:18:21,279 SPEAKER_00: If you delay migrating away from legacy 519 00:18:21,279 - > 00:18:23,759 on-premise servers, or if you hold off on implementing 520 00:18:23,759 - > 00:18:26,480 advanced machine learning for your fraud detection, you are 521 00:18:26,480 - > 00:18:29,440 choosing to fight tomorrow's simultaneous threats with 522 00:18:29,440 - > 00:18:31,200 yesterday's sequential tools. 523 00:18:31,519 - > 00:18:33,200 SPEAKER_01: Ah, I see where this leads. 524 00:18:33,359 - > 00:18:36,480 If you use the pressure of the crisis to force through vital 525 00:18:36,480 - > 00:18:38,559 system upgrades, you are building capacity. 526 00:18:38,880 - > 00:18:39,279 SPEAKER_00: Exactly. 527 00:18:39,440 - > 00:18:42,400 Meanwhile, your competitor gives in to fear, freezes their 528 00:18:42,400 - > 00:18:44,319 budget, and just tries to keep their head above water. 529 00:18:44,559 - > 00:18:46,720 SPEAKER_01: So when the market finally establishes a new 530 00:18:46,880 - > 00:18:50,240 turbulent equilibrium, you aren't just surviving, you are 531 00:18:50,240 - > 00:18:52,640 operating with unprecedented efficiency. 532 00:18:52,960 - > 00:18:55,519 SPEAKER_00: You have engineered a structural advantage. 533 00:18:55,759 - > 00:18:57,279 A structural advantage. 534 00:18:57,519 - > 00:18:57,759 SPEAKER_01: Yes. 535 00:18:57,920 - > 00:19:00,160 SPEAKER_00: Your systems can automatically route around 536 00:19:00,160 - > 00:19:01,519 localized outages. 537 00:19:01,680 - > 00:19:06,079 Your fraud algorithms can parse false positives in milliseconds. 538 00:19:06,400 - > 00:19:09,200 SPEAKER_01: Your compliance tech ingests sanctions instantly. 539 00:19:09,519 - > 00:19:09,839 SPEAKER_00: Right. 540 00:19:10,000 - > 00:19:14,000 And your competitor will take years and billions of dollars to 541 00:19:14,000 - > 00:19:15,759 close that operational gap. 542 00:19:16,000 - > 00:19:19,680 The technology decisions a board makes under maximum pressure 543 00:19:19,680 - > 00:19:22,319 will define their market dominance well beyond the 544 00:19:22,319 - > 00:19:23,599 current geopolitical cycle. 545 00:19:23,920 - > 00:19:25,920 SPEAKER_01: Which brings us to the ultimate takeaway here. 546 00:19:26,160 - > 00:19:27,680 SPEAKER_00: Yeah, bringing it back to the big picture. 547 00:19:28,000 - > 00:19:30,400 SPEAKER_01: Even if you, listening to this deep dive 548 00:19:30,400 - > 00:19:32,640 right now, have absolutely nothing to do with Middle 549 00:19:32,640 - > 00:19:33,359 Eastern banking. 550 00:19:33,599 - > 00:19:33,920 Right. 551 00:19:34,160 - > 00:19:37,119 Even if you work in global logistics or healthcare 552 00:19:37,119 - > 00:19:40,559 administration or international e-commerce, this report is an 553 00:19:40,559 - > 00:19:43,440 absolute masterclass in modern operational survival. 554 00:19:43,680 - > 00:19:46,160 SPEAKER_00: It really redefines what it means to be prepared. 555 00:19:46,400 - > 00:19:49,279 SPEAKER_01: It proves that in a hyper-interconnected digital 556 00:19:49,279 - > 00:19:52,480 economy, your resilience is only as strong as your weakest, 557 00:19:52,640 - > 00:19:54,240 unmapped third-party vendor. 558 00:19:54,480 - > 00:19:56,160 SPEAKER_00: That fourth party Wi-Fi router. 559 00:19:56,559 - > 00:19:56,960 SPEAKER_01: Exactly. 560 00:19:57,119 - > 00:19:59,839 And it proves that true continuity doesn't mean having a 561 00:19:59,839 - > 00:20:01,200 plan for a disaster. 562 00:20:01,440 - > 00:20:06,000 It means having a mechanism to absorb simultaneous, overlapping 563 00:20:06,000 - > 00:20:09,440 disasters without losing the trust of your user base. 564 00:20:09,839 - > 00:20:12,480 SPEAKER_00: The principles of resilience are universal across 565 00:20:12,480 - > 00:20:13,279 all sectors. 566 00:20:13,519 - > 00:20:17,599 It all comes down to speed, coordination, and the verifiable 567 00:20:17,599 - > 00:20:21,039 ability to maintain digital integrity when the physical 568 00:20:21,039 - > 00:20:23,359 environment around you is completely unpredictable. 569 00:20:23,680 - > 00:20:24,079 SPEAKER_01: Very true. 570 00:20:24,400 - > 00:20:26,240 SPEAKER_00: Which actually leaves us with a fascinating, 571 00:20:26,400 - > 00:20:27,680 broader concept to consider. 572 00:20:28,000 - > 00:20:29,119 SPEAKER_01: Oh lay it on us. 573 00:20:29,440 - > 00:20:31,119 SPEAKER_00: For the last century, we have valued 574 00:20:31,119 - > 00:20:34,319 companies based on very specific traditional metrics. 575 00:20:34,480 - > 00:20:37,200 We look at profit margins, quarter over quarter growth 576 00:20:37,200 - > 00:20:37,519 projections. 577 00:20:37,839 - > 00:20:39,599 SPEAKER_01: User acquisition costs, market share. 578 00:20:39,920 - > 00:20:40,319 SPEAKER_00: Exactly. 579 00:20:40,720 - > 00:20:43,519 But is overlapping global disruptions, whether they're 580 00:20:43,519 - > 00:20:46,559 geopolitical conflicts, massive technological shifts, or 581 00:20:46,559 - > 00:20:49,359 environmental crises become the absolute norm rather than the 582 00:20:49,359 - > 00:20:49,759 exception. 583 00:20:49,920 - > 00:20:50,079 Yeah. 584 00:20:50,400 - > 00:20:52,960 We might need an entirely new metric for valuation. 585 00:20:53,279 - > 00:20:54,000 SPEAKER_01: What kind of metric? 586 00:20:54,319 - > 00:20:56,640 SPEAKER_00: What if the ultimate measure of an organization's 587 00:20:56,640 - > 00:20:58,960 future worth becomes its chaos tolerance? 588 00:20:59,359 - > 00:21:00,079 SPEAKER_01: Chaos tolerance. 589 00:21:00,400 - > 00:21:00,880 SPEAKER_00: Yes. 590 00:21:01,039 - > 00:21:05,039 It's mathematically proven, battle-tested ability to 591 00:21:05,039 - > 00:21:08,559 maintain digital trust and uninterrupted operational 592 00:21:08,559 - > 00:21:11,920 continuity when the physical world around it is unraveling. 593 00:21:12,319 - > 00:21:14,559 SPEAKER_01: So the companies that can audit, prove, and 594 00:21:14,559 - > 00:21:18,160 expand their chaos tolerance will be the ones that command 595 00:21:18,160 - > 00:21:20,000 the most value in the markets of tomorrow. 596 00:21:20,319 - > 00:21:20,799 SPEAKER_00: That's the idea. 597 00:21:21,039 - > 00:21:23,359 SPEAKER_01: That is a completely new lens for evaluating 598 00:21:23,359 - > 00:21:24,160 corporate strength. 599 00:21:24,319 - > 00:21:26,480 And it brings us right back to the image we started with. 600 00:21:26,799 - > 00:21:27,519 SPEAKER_00: The cup of coffee. 601 00:21:27,839 - > 00:21:28,480 SPEAKER_01: Exactly. 602 00:21:28,720 - > 00:21:32,000 When you picture an institution in crisis, you no longer need to 603 00:21:32,000 - > 00:21:35,359 look for a plummeting stock ticker or a physical run on a 604 00:21:35,359 - > 00:21:35,920 local branch. 605 00:21:36,240 - > 00:21:37,599 SPEAKER_00: The signs are much subtler now. 606 00:21:37,920 - > 00:21:40,400 SPEAKER_01: The real test of an organization's survival is 607 00:21:40,400 - > 00:21:43,359 happening right now, silently, in the hidden digital 608 00:21:43,359 - > 00:21:45,519 architecture that keeps our world moving. 609 00:21:45,759 - > 00:21:49,039 The true crisis and the true victory are completely 610 00:21:49,039 - > 00:21:49,599 invisible.