[{"data":1,"prerenderedAt":255},["ShallowReactive",2],{"focus:third-party-and-vendor-risk":3},{"id":4,"title":5,"body":6,"decision":243,"description":244,"extension":245,"eyebrow":246,"focusArea":12,"lead":247,"meta":248,"navigation":249,"order":250,"path":251,"seo":252,"stem":253,"__hash__":254},"content\u002Fenterprises\u002Ffocus-areas\u002Fthird-party-and-vendor-risk.md","Everyone else who touches your data: third-party and vendor risk",{"type":7,"value":8,"toc":232},"minimark",[9,13,18,22,31,35,42,48,54,60,64,67,157,160,164,168,171,174,178,194,198,212],[10,11],"self-assessment-scorecard",{"slug":12},"third-party-and-vendor-risk",[14,15,17],"h2",{"id":16},"what-this-covers","What this covers",[19,20,21],"p",{},"Any vendor that processes personal data for you must be bound by a valid contract. That is a legal duty. Around it sits the practice of oversight: knowing what actually moves to which vendor, making sure partners stop when consent dies, and keeping evidence that the ecosystem behaves.",[19,23,24,25,30],{},"This is the data-sharing dimension of vendor relationships, not general procurement reform. The ",[26,27,29],"a",{"href":28},"\u002Fenterprises\u002Fthird-party-data-exchange","third-party data exchange page"," covers the day-to-day discipline of sharing data safely, including why casual channels like WhatsApp do not belong in the flow. This page is about governing the relationships themselves.",[14,32,34],{"id":33},"the-framework-four-moves","The framework: four moves",[19,36,37,41],{},[38,39,40],"strong",{},"Move 1: Build the processor register."," Every vendor that touches personal data: who they are, what data, what purpose, under which contract, where they process it, which sub-processors they use. Build it from real flows, not only procurement records; business teams engage vendors directly.",[19,43,44,47],{},[38,45,46],{},"Move 2: Fix the contracts."," Every processor contract needs clauses covering permitted use, the safeguards required, sub-processing rules, incident notification, and deletion or return of data at the end. Remediate legacy contracts signed before these clauses existed; prioritise by the sensitivity of what the vendor holds, and give the plan dates.",[19,49,50,53],{},[38,51,52],{},"Move 3: Monitor what moves and enforce consent."," Compare real data flows to vendors against what contracts allow. When consent for a purpose dies, the stop signal must reach every partner who received data under it, technically, with confirmation. Contract alone does not do this.",[19,55,56,59],{},[38,57,58],{},"Move 4: Oversee on a rhythm and keep evidence."," Tiered checks matched to vendor risk: attestations, evidence requests, review meetings. Keep the contract inventory with status, partner attestations, oversight records and withdrawal-propagation test results.",[14,61,63],{"id":62},"template-the-processor-register","Template: the processor register",[19,65,66],{},"One row per vendor or partner. Copy this and fill it in.",[68,69,70,104],"table",{},[71,72,73],"thead",{},[74,75,76,80,83,86,89,92,95,98,101],"tr",{},[77,78,79],"th",{},"Vendor",[77,81,82],{},"What data",[77,84,85],{},"Purpose",[77,87,88],{},"Contract status",[77,90,91],{},"Key clauses present",[77,93,94],{},"Sub-processors",[77,96,97],{},"Where processed",[77,99,100],{},"Tier",[77,102,103],{},"End-of-contract handling",[105,106,107,137],"tbody",{},[74,108,109,113,116,119,122,125,128,131,134],{},[110,111,112],"td",{},"Example: collections agency",[110,114,115],{},"Customer contact, loan status",[110,117,118],{},"Collections on overdue accounts",[110,120,121],{},"Signed",[110,123,124],{},"All",[110,126,127],{},"None",[110,129,130],{},"India, vendor DC",[110,132,133],{},"High",[110,135,136],{},"Return plus certified deletion",[74,138,139,141,143,145,147,149,151,153,155],{},[110,140],{},[110,142],{},[110,144],{},[110,146],{},[110,148],{},[110,150],{},[110,152],{},[110,154],{},[110,156],{},[19,158,159],{},"The downloadable file adds the column guide and the clause checklist.",[161,162],"template-download-card",{"slug":163},"processor-register",[14,165,167],{"id":166},"what-good-looks-like-at-the-end","What good looks like at the end",[19,169,170],{},"You should have: a complete processor register, contracts brought up to standard or a dated plan to get there, a working oversight routine, and demonstrated withdrawal propagation to partners.",[19,172,173],{},"The live test: pick one customer who has withdrawn consent for marketing. Trace which partners ever received their data for that purpose, and produce the proof that each stopped. If the trail ends at \"we sent an email\", the propagation is not real.",[14,175,177],{"id":176},"where-enterprises-go-wrong","Where enterprises go wrong",[179,180,181,185,188,191],"ul",{},[182,183,184],"li",{},"A processor register built from procurement records only, missing the vendors business teams engaged directly.",[182,186,187],{},"Legacy contracts left unremediated because there are too many. Start with the vendors holding the most sensitive data.",[182,189,190],{},"Consent enforcement tested at your own systems but never at partners.",[182,192,193],{},"Oversight that ends at contract signing. The contract is the starting line, not the finish.",[14,195,197],{"id":196},"the-decisions-to-make","The decisions to make",[179,199,200,203,206,209],{},[182,201,202],{},"Oversight depth per vendor tier, and the tiering criteria.",[182,204,205],{},"How withdrawal propagation is implemented technically per partner.",[182,207,208],{},"The order and pace of legacy contract remediation.",[182,210,211],{},"Whether oversight evidence is produced for audits, and in what form.",[213,214,215,220],"blockquote",{},[19,216,217],{},[38,218,219],{},"Next step",[19,221,222,226,227,231],{},[26,223,225],{"href":224},"\u002Fenterprises\u002Ffocus-areas\u002Fretention-erasure-and-localisation","Retention, erasure and localisation",", which decides what your vendors are still holding at the end. If you need help with any of this, ",[26,228,230],{"href":229},"\u002Fcontact","write to us"," and we will help.",{"title":233,"searchDepth":234,"depth":234,"links":235},"",3,[236,238,239,240,241,242],{"id":16,"depth":237,"text":17},2,{"id":33,"depth":237,"text":34},{"id":62,"depth":237,"text":63},{"id":166,"depth":237,"text":167},{"id":176,"depth":237,"text":177},{"id":196,"depth":237,"text":197},null,"You remain responsible for personal data in your vendors' hands, in law and in reputation. Processors, outsourced providers and partners handle your...","md","Focus area 08","You remain responsible for personal data in your vendors' hands, in law and in reputation. Processors, outsourced providers and partners handle your customers' data every day, and the Act binds you, the data fiduciary, not them. Vendor risk is governed, not hoped away: a register, the contracts, working consent enforcement at partners, and evidence the ecosystem behaves.",{},true,8,"\u002Fenterprises\u002Ffocus-areas\u002Fthird-party-and-vendor-risk",{"title":5,"description":244},"enterprises\u002Ffocus-areas\u002Fthird-party-and-vendor-risk","eggOqzNNjEZHTRSMk_JKl_JhzSJmYaBXUynoMuj3ckM",1795073010229]