Strengthening Third-Party Resilience in an Increasingly Cloud-Dependent Environment
- Improving visibility of hidden dependencies: Identify sole-source suppliers, subcontractors, and cloud dependencies through assessments and mapping exercises.
- Assessing resilience through evidence: Go beyond certifications by reviewing testing, incident, recovery, and performance data.
- Managing cloud concentration risk: Strengthen operational resilience and access to critical data during outages.
- Expanding risk frameworks for AI: Treat cloud-hosted AI and related services as dependencies subject to existing controls.
- Focusing on practical resilience: Prioritise defence-in-depth, dependency management, contingency planning, and operational resilience over adding more cloud providers.
Ahead of CeFPro’s Vendor
& Third Party Risk: The Cross-Industry Conference in Fort Worth, USA on
October 14-15, we sat down with Mark Carroll, Founder – Graduate ERM Program,
Boston University, to explore the evolving landscape of third-party and cloud
dependency risk, operational resilience, hidden fourth-party dependencies, and
how organisations can better prepare for disruption in an increasingly
interconnected technology environment.
1. Many organisations have visibility over
their direct vendors but limited insight into underlying cloud providers. What
approaches have you found most effective for uncovering and mapping hidden
cloud dependencies and fourth-party risks across a vendor portfolio?
Use of Service Level Agreements (SLAs)
as well as the identification of single and sole source vendors being used by a
direct vendor. Results of exercises
conducted by vendors that engage data dependencies.
2. Beyond standard certifications and audit reports, what evidence should organisations be requesting from suppliers to gain real confidence in their resilience, failover capabilities, and incident response preparedness?
Access to testing results from recovery
tabletops, full scale assessments and actual crisis events as well as vendor
performance data (on time delivery, percentage complete, etc.). Also inventory and production management
practices (i.e., inventory on hand, etc.).
3. For organisations heavily reliant on a
small number of cloud providers, what are the most practical mitigation
measures you've seen implemented when diversification is not commercially or
technically feasible?
Protect yourself with good solid data
management. For example, generate
regular reports that depict inventory balances, production status, financial
conditions, etc. only to be used in the event that the firm is running blind
due to a cloud vendor outage.
4. As more third-party solutions become
dependent on cloud-hosted AI services, how do you see operational risk
frameworks evolving to address these increasingly interconnected technology
ecosystems?
Operational Risk frameworks will not
change but the scope of these frameworks will evolve. Single and sole source vendor dependency
management is not new but for reasons of complexity has allowed Cloud hosted
services (AI et al) to be excluded from that fundamental management. Going forward Cloud service outage will be or
needs to be addressed in the same manner as a sole or single source vendor that
cannot deliver.
5. Looking ahead five years, do you expect
organisations to continue managing cloud concentration risk through governance
and resilience measures, or will market, regulatory, or technological
developments drive a more distributed sourcing model?
Firms will need to protect themselves
better as they become more cloud-dependent.
A distributed sourcing model will be too complex for most firms, at
least operationally. Failover will not
be easily accomplished from Cloud house to Cloud house. Firms are relying on defence-in-depth between
Cloud vendor sites, not realizing that it is a single vendor regardless of the
number of installations.
Founder - Graduate ERM Program, Boston University
Mark Carroll is a risk, crisis, and recovery professional with over 30 years of experience in the field of vendor risk management, business continuity, crisis management, and disaster recovery. Mark launched the very first business continuity and disaster recovery programs for BIOGEN; built out the global Gillette crisis and continuity program to 150 locations worldwide, built out the vendor risk program for Fidelity Employer Services Company, led Business Continuity globally for Fidelity Enterprise Operations and introduced risk, emergency management and recovery management at Income Research and Management. An Information Technology (IT) professional by education and training, Mark built out the IT Audit program at Gillette, integrating IT control assessment into operational audit activities. Prior to these roles Mark was the head of IT for Rexam Graphics and JPS Elastomerics. Mark is currently employed at Boston University and is a frequent speaker at Continuity Insights, ISACA, MIT, DHS, and Disaster Recovery Journal conferences. Mark is Founder of the graduate degree in Enterprise Risk Management (ERM) at Boston University and functions as adjunct faculty at the University, having taught risk management to over 3000 graduate students worldwide. A member of Infragard, he previously served on the Board of Boston Chapter of the Association of Continuity Professionals (ACP). Education: MBA – Babson College (Finance); BA – Boston College (Economics and Political Science) Certifications: CPIM, CIRM, MBCP, FBCI, CISSP, CISA, PMP, CGEIT, RIMS-CRMP, GRCP, GRCA
LinkedIn profile