EY refers to the global organization, and may refer to one or more, of the member firms of Ernst & Young Global Limited, each of which is a separate legal entity. Ernst & Young Global Limited, a UK company limited by guarantee, does not provide services to clients.
How EY can help
-
Discover how EY's Third Party Risk Management team can enable your business to make better decisions about the third parties they choose to work with.
Read more
When it comes to organizational risk, AI presents a double-edged dilemma. Every leap forward brings powerful capabilities to better assess and address risk across an expanding enterprise, but it also introduces new and fast-changing exposure through the vendors, suppliers and other third-party organizations and technology that use it. As those third-party networks grow and AI is embedded into more processes and workflows, many organizations can’t identify, assess or manage the related risk fast enough. It’s a far worse problem when models, data sources, functionality and downstream dependencies can all be impacted after onboarding the third party. When this happens, risk profiles that once passed due diligence can suddenly look very different.
AI, of course, offers capabilities to manage those increasing risks, but adding it to an unchanged business model won’t solve the problem. Instead, risk leaders should consider the opportunity to redesign third-party risk management (TPRM) for the AI era, including how to incorporate TPRM managed services as a continuous, decision-oriented capability to both govern AI risk and strengthen oversight. Here is a four-step strategy for risk leaders to follow:
1. Identify AI exposure beyond traditional vendors
It’s important to broaden the view of AI risk factors beyond providers labeled as AI companies. Start with identifying all AI-embedded models, cloud platforms, open-source components, subcontractors and AI-enabled services that have a direct and crucial influence on business processes. Link each dependency to its business owner, data access, operational purpose and downstream relationships so the organization can pinpoint exact exposures and create a risk mitigation approach.
From there, create a plan to keep track of changes within these vendors. If a provider’s model, training data, functionality or subprocessor network shifts after onboarding, things like privacy, cyber, compliance and operational processes can all pose a risk.