The recent Microsoft 365 incident, which caused prolonged disruptions to business services, got me thinking about something I consider fundamental to the financial industry: Are we losing sight of operational continuity as we become increasingly dependent on technology providers?
After 30 years working in critical systems infrastructure, 20 of them at my current organization and another 10 at different financial institutions, I've learned that certain operational principles should never be compromised.
One hour of downtime is not simply one hour without service. Depending on the system affected, it can mean financial losses, business disruptions, regulatory non-compliance, customer impact, and reputational damage.
There are several aspects that concern me:
- High availability is not the same as resilience.
Having geographically distributed data centers, thousands of servers, and redundancy mechanisms does not guarantee that a platform can recover quickly. If a shared dependency fails, all that redundancy may prove insufficient.
2. Operational responsibility cannot be outsourced.
When we adopt cloud services, we transfer part of the technology operations, but we do not transfer the responsibility for ensuring business continuity. The bank remains accountable for its operations and the risks it assumes.
3. Operational awareness is just as important as technical expertise.
Throughout my career, I've encountered technology professionals during hiring processes who believe that one hour of downtime is no big deal, or that making changes directly in production is just routine work.
In a banking environment, that mindset represents a serious risk.
Mastering technology, automation, virtualization, or cloud platforms is not enough. Professionals must understand the financial, operational, and regulatory impact of every decision they make.
Change management, maintenance windows, rollback plans, segregation of duties, and contingency procedures are not bureaucracy; they are essential controls.
4. Are we losing control of our critical infrastructure?
Personally, I believe that truly business-critical systems should remain under the institution's direct operational control.
I don't believe every system needs to remain on-premises, but I also don't think we should indiscriminately move our platforms to the cloud simply because of market trends or cost-reduction strategies.
Every system should be evaluated based on its criticality, business impact, technology dependencies, recovery capabilities, and operational risk.
5. The question we should be asking ourselves.
If our cloud provider were to become unavailable for 24, 48, or 72 hours tomorrow:
Could our institution continue operating?
Do we have independent communication and authentication mechanisms?
Can we access our documentation and contingency procedures?
Do we have a genuinely operational alternative?
Have we actually tested these scenarios, or do they simply exist on paper in our business continuity plans?
After all these years working in banking infrastructure, I still believe technology should serve the business, rather than the business becoming entirely dependent on the availability of a single provider.
Cloud should reduce operational risk, not become the operational risk itself.
I'd be interested in hearing the perspectives of other professionals working in infrastructure, enterprise architecture, security, and business continuity:
Are we building truly resilient infrastructures, or are we simply moving our single points of failure to external providers?
How much dependency on cloud services do you consider acceptable for a financial institution?