DataAI & Technology

Proof Not Promises: Why Vendor Trust is Critical For Enterprises to Navigate Data Residency and Geopolitical Complexity

By Joe Logan, CIO, iManage

With data residency rules multiplying, geopolitical tensions shifting, and new security threatsย emergingย faster than ever, enterprises face a growing list of compliance obligations andย significant downside risk they need to successfully manage.ย Increasingly, this will require partneringย with cloud vendorsย who can not only navigateย multi-jurisdictional compliance complexityย but canย also objectivelyย validateย theirย securityย and governance capabilitiesย โ€“ย making โ€œtrustโ€ย aย primary competitive differentiator forย vendorย selection.ย 

To get it right, shift leftย 

Maintainingย data residency compliance was always a challenging undertaking, but technologies like AI raise the level of complexity significantly.ย ย 

AI needs to be grounded in curated data thatย residesย in a specific location. However, if AI performsย aย task on that data โ€“ aย quickย analysis, perhaps, orย aย summarisationย โ€“ is that output, which is a derivative of the original data, subject to the same data residency requirements? How should data that has beenย abstracted or changed in some way through an AI functionย be treated when it comes to data residency?ย 

Getting those nuances right requiresย a full understandingย of the regulatory componentsย andย theย financial and legalย risks associated withย breachingย those regulatoryย requirements.ย The โ€œwork fast and break thingsโ€ย approachย isย not the way to goย here.ย ย 

Vendors whoย โ€œshift leftโ€ and incorporateย regulatory, legal, privacy,ย andย security concernsย veryย early in the development process โ€“ย rather than retroactively having to add functionalityย in โ€“ย help ensureย thatย the right level of information can be shared across regions and leveraged by technologies like AI withoutย residency requirementsย beingย breached.ย ย 

For their part, enterprises will likewise benefit from โ€œshifting leftโ€ and making sure that people who fully understand these compliance nuances are involvedย early in theย vendor evaluation and selection processย rather than being brought on at the last minute, right as a deal is about to be inked.ย 

Solvingย the โ€œsay-doโ€ problemย 

Even with stronger processes upstream, enterprises face a deeper challenge:ย determiningย whether vendorsโ€™ assurances reflect reality or simply sound good on paper.ย Enterprises want toย knowย that anyย cloudย vendors theyโ€™re contracting with are compliant with a veritable alphabet soup of security and compliance frameworks:ย from ISO and CSA STAR; FedRAMP, IRAP,ย and Cyber Essentials Plus; EU-US Data Privacy Framework; through to NIST AI Risk Management andย theย EU AI Act.ย 

This means that vendors need to be able toย crediblyย attest to complianceย โ€“ย or,ย better yet,ย be evaluated by independent third partiesย that attest to their compliance. This helps address the โ€œsay-doโ€ problem: A vendor mightย sayย they tick the box inย X,Y, or Z area, but an independent validation verifies what theyย actuallyย do.ย 

Part of this effort involvesย vendorsย being able to provideย highlyย detailed documentation aroundย all relevant aspects of their platform, which couldย compriseย anything fromย data governanceย and data residencyย toย access management,ย AI, andย encryption services.ย ย 

Broad, high-levelย overviews no longerย cut itย in these areas.ย Vendors should be prepared to provide deep, โ€œnext levelโ€ detailsย โ€“ for instance, not justย indicatingย that encryption is used for certainย functions, butย specifyingย what type ofย cryptographic modulesย are used. Alternately, they should be able toย indicateย what steps the company takes around achieving separation of networks, or evenย provideย in-depthย details around token managementย โ€“ not just how they issue the digital tokens that applications use for authentication andย authorisation, but how they store, protect, monitor, refresh, and revoke them.ย ย ย 

To make sure nothing getsย โ€œlost in translationโ€ย around what isย requiredย fromย either a customer or regulatoryย standpoint versus what functionality and safeguards the productย actually provides,ย itโ€™sย important toย incorporate cross-functional teamsย at all stages of theย product development and documentationย process.ย Legal, privacy, security, development,ย andย operationsย should all be involvedย and working hand in gloveย to make sure that there’s alignment betweenย โ€œsayโ€ and โ€œdo.โ€ย 

Eye to the futureย 

If vendors want to build trust in the eyes of enterprises,ย itโ€™sย not enough toย show thatย theyโ€™reย able toย tackle todayโ€™s challenges โ€“ they also need to show thatย theyโ€™reย keeping an eye on the horizonย and tomorrowโ€™s threats.ย 

For instance, while it might not be aย riskย right now, what are vendors doing to prepare themselves against the potential combination of AI malwareย andย quantum computingย capabilities โ€“ย a supercharged threat thatย could break through cryptographic standards inย a fraction of theย timeย requiredย today?ย 

Thoseย customerย questions are coming, which means that vendors need to be moving towards having a credible answerย that can reassure customers thatย theyโ€™reย already putting thought intoย how to future-proof against emergent threats.ย 

In the end, the vendors preparing for tomorrowโ€™s threat landscape are the same ones proving they can be trusted today โ€“ and that distinction is becoming impossible to ignore. Vendors who canย proveย โ€“ not just claim โ€“ that they meet the highest bar across privacy, security, and residency will earn a seat at the enterprise table. Everyone else will discover that in todayโ€™s challenging security and data governance landscape, the absence of credible attestations is a dealbreaker. When trust is solid, decisions are faster, alignment is stronger, and results scale.ย ย 

Author

Related Articles

Back to top button