- 17th Nov 2026
- 1 min read
Effective Third-Party Information Gathering: 2026 Due Diligence Guide
- Written by
In Short..
- Third-party risk is an information problem: Questionnaires and one-off assessments are not enough to establish a reliable picture of a vendor's security, financial stability and operational resilience.
- Supply chain threats are increasing: Third-party involvement in data breaches is growing, making effective vendor due diligence essential to identifying risks before they escalate.
- Structured information gathering is key: Organisations need a consistent approach to vendor identification, risk classification, due diligence, evidence collection and validation.
- Assessments should reflect vendor risk: The depth of information gathered should be proportionate to each supplier's risk, criticality and access to organisational systems or data.
- Evidence must be verified: Questionnaires alone cannot guarantee accuracy. Organisations need to validate vendor responses using supporting documentation and independent evidence.
- Monitoring must be ongoing: Third-party oversight should continue throughout the relationship, rather than stopping once onboarding checks are complete.
Effective third-party risk management depends on having accurate, validated and up-to-date information. By combining structured due diligence, risk-based assessments and continuous monitoring, organisations can strengthen vendor oversight and make better-informed risk decisions.
Introduction
Third-party risk management is not a questionnaire problem. It is an information problem.
Organisations continue to onboard vendors without a reliable picture of their security posture, financial stability, or operational resilience. They complete due diligence at the start of the relationship and treat it as done.
The result is oversight that looks complete on paper and fails under scrutiny.
The consequences are measurable. According to IBM's Cost of a Data Breach Report 2025, supply chain compromise accounted for approximately 15 percent of initial attack vectors studied, at an average cost of $4.91 million per incident, and took 267 days to detect and contain: the longest of any vector. Verizon's 2025 Data Breach Investigations Report found that third-party involvement in confirmed breaches doubled in a single year, rising from 15 to 30 percent.
These are the costs of information gaps that structured due diligence should catch early.
Executive Summary
The regulatory environment governing third-party risk has moved from expectation to enforcement. Organisations that have not yet updated their TPRM programmes to reflect this shift are already behind.
The core problem: Most third-party due diligence programmes are still built around manual questionnaires, inconsistent assessment practices, and limited evidence validation. That model was never strong. Against the current environment, it is no longer defensible.
The regulatory position as of November 2026
|
Regime |
Status |
Key obligation |
|
DORA |
In force since January 2025; national supervisors actively scrutinising ICT third-party registers |
Register of Information; critical ICT third-party oversight |
|
NIS2 |
Enforcement active; full compliance deadline passed October 2026 |
Supply chain security; personal management liability |
|
UK Critical Third Parties regime |
Live from 13 July 2026 |
Joint FCA/PRA/Bank of England oversight of designated CTPs |
|
UK Cyber Security and Resilience Bill |
Lords Third Reading completed 2 November 2026; Commons consideration of Lords amendments scheduled 24 November 2026; carry-over extended to 29 April 2027 |
Expanded scope; managed service providers and critical suppliers brought in |
|
EU AI Act |
Phasing in through 2027 |
AI risk management obligations for high-risk AI systems |
DORA has been in force since January 2025. National supervisors are now scrutinising ICT third-party registers rather than waiting for them. The European Supervisory Authorities designated 19 critical ICT third-party service providers on 18 November 2025, including the major cloud providers, triggering lead overseer obligations under Chapter V.
NIS2 enforcement is now active. The full compliance deadline passed in October 2026, bringing manufacturing into scope for the first time and extending supply chain obligations to suppliers of in-scope entities. Personal liability for management is explicit under Article 20.
The UK Critical Third Parties regime is no longer forthcoming. It is live. HM Treasury designated Amazon Web Services EMEA SARL, Google Cloud EMEA Limited, Microsoft Ireland Operations Limited, and Oracle Corporation UK Limited as critical third parties with effect from 13 July 2026 under SI 2026/777. The FCA, PRA, and Bank of England now jointly oversee the systemic services these providers deliver to UK financial firms. Firms relying on any of these four providers must ensure their own due diligence and contractual arrangements reflect this oversight context. The regime is described by HM Treasury as rolling; further designations are expected.
The Cyber Security and Resilience Bill completed its Lords Third Reading on 2 November 2026. The House of Commons has scheduled consideration of Lords amendments for 24 November 2026. A carry-over motion passed on 4 November 2026 extends the deadline to 29 April 2027. The Government has tabled amendments to introduce a new vendor risk management framework, and the definition of "regulated person" has been clarified to include operators of essential services, digital service providers, managed service providers, and critical suppliers. Royal Assent is expected before the carry-over expires, with most operational duties anticipated around 2028.
The framework in this guide builds in sequence: inventory, tiering, proportionate collection, validation, and technology at scale. Each step depends on the ones before it. Organisations that invest in structured, lifecycle-aware information gathering will identify vendor risk earlier, make governance decisions they can defend, and respond faster when a vendor's risk profile changes. Those that do not will find it harder to satisfy regulators or avoid consequences they could have seen coming.
The Third-Party Risk Environment and Why Programmes Fail
The third-party ecosystem has become the primary attack surface for most organisations. Supply chain compromise, credential theft via managed service providers, and data exposure through unsecured vendor integrations are now among the most common sources of material incidents.
The scale of exposure is larger than most organisations recognise. Large enterprises now manage thousands of active vendor relationships. A 2024 Prevalent survey found that 52 percent of organisations experienced a third-party data breach or incident in the preceding 12 months. The same research found that only 35 percent of organisations conducted ongoing monitoring after initial onboarding. The gap between those two numbers is the risk window most programmes leave open.
Why traditional programmes fail
The typical TPRM programme fails at one or more of five predictable points:
- Incomplete inventory. Vendors are added without formal registration. Relationships expand beyond their original scope. Shadow IT and departmental procurement create third-party relationships that the risk function never sees.
- Inconsistent tiering. Vendors are assessed at the same depth regardless of the risk they represent. Critical providers receive the same questionnaire as low-risk software licences. Neither assessment is calibrated to the actual exposure.
- Self-reported information, unverified. Questionnaire responses are accepted at face value. Certifications are noted but not validated against current status. Financial information is not independently confirmed.
- Point-in-time assessment. Due diligence happens at onboarding and, if the programme is disciplined, at annual renewal. In between, the vendor's risk profile can change materially without the organisation knowing.
- No closure loop. Issues identified during assessment are logged but not tracked to resolution. The programme records the finding; it does not confirm the fix.
The result: A programme that produces documentation rather than assurance. It may satisfy a first-line audit. It will not satisfy a regulator who asks what changed between assessments.
The regulatory shift from expectation to obligation
For most of the last decade, third-party risk management was treated as a recognised good practice. Frameworks such as ISO 27001, SOC 2, and the NCSC's supply chain guidance set expectations. Regulators noted deficiencies in supervisory reports.
That period is over. DORA imposes mandatory ICT third-party registers, contractual requirements, and critical provider oversight with direct regulatory consequences. NIS2 creates personal liability for management bodies that fail to implement adequate supply chain security measures. The FCA and PRA are jointly supervising the systemic services of designated critical third parties in real time.
The question is no longer whether third-party oversight is good practice. It is whether your programme is designed to produce the evidence that regulators will ask to see.
The Foundations of Effective Third-Party Information Gathering
Effective third-party information gathering is not a single activity. It is a programme built on four interdependent foundations: a complete and current vendor inventory, a risk-based tiering model, proportionate due diligence design, and a lifecycle approach that does not treat onboarding as the end point.
Foundation 1: A complete vendor inventory
You cannot manage risk from relationships you do not know exist. Before any assessment framework is designed, the organisation needs a definitive register of every third-party relationship, including:
- Technology and software providers (SaaS, IaaS, PaaS, on-premise)
- Managed service providers and outsourced operations
- Data processors and sub-processors
- Professional services firms with system access
- Fourth parties: the critical suppliers your key vendors rely on
The DORA requirement is specific. Article 28 requires in-scope financial entities to maintain a register of information on all contractual arrangements with ICT third-party service providers. The register must be kept current and made available to competent authorities on request. An incomplete register is not a minor procedural gap; it is a regulatory finding.
Practical steps to build a complete inventory:
- Cross-reference procurement records, accounts payable data, and IT asset registers
- Conduct interviews with business unit heads and IT teams to surface shadow procurement
- Map data flows to identify processors not visible in the contract register
- Review fourth-party dependencies for critical vendors
Foundation 2: Risk-based tiering
Not every vendor warrants the same depth of assessment. A risk-based tiering model ensures that due diligence effort is proportionate to the exposure a vendor represents.
|
Tier |
Characteristics |
Assessment depth |
|
Critical |
Systemic dependency; access to sensitive data or core systems; no viable short-term substitute |
Full due diligence; on-site or virtual review; independent validation; continuous monitoring |
|
High |
Significant data access or operational dependency; substitutable but with material effort |
Comprehensive questionnaire; evidence validation; annual reassessment |
|
Medium |
Limited data access; not operationally critical |
Standard questionnaire; periodic review |
|
Low |
Minimal data access; easily substitutable |
Simplified intake; periodic spot-check |
The tiering criteria should reflect the specific risk dimensions most relevant to your organisation and sector. For financial services firms under DORA, the distinction between "critical or important functions" and other services is a regulatory classification, not just an internal one. The assessment depth applied to critical ICT third-party service providers must be demonstrably more rigorous.
Foundation 3: Proportionate due diligence design
Once tiering is established, the due diligence process for each tier should be designed before any individual assessment begins. This means defining in advance:
- What information categories will be collected (see Section 3)
- What evidence will be required to validate responses
- What questionnaire framework will be used
- What the escalation path is for identified issues
- What the minimum acceptable standard is before the relationship proceeds
Designing the process in advance prevents the common failure mode of assessments that are customised ad hoc, producing results that cannot be compared across the vendor population.
Foundation 4: Lifecycle-aware oversight
Third-party risk does not peak at onboarding. It evolves throughout the relationship. A programme built only on initial due diligence has a structural blind spot for everything that happens after a vendor is approved.
Key lifecycle trigger points that should initiate a reassessment:
- A vendor announces a merger, acquisition, or significant ownership change
- A vendor experiences a publicly disclosed security incident
- A vendor's financial position deteriorates materially
- The scope of services or data access changes
- A vendor undergoes a significant subcontractor change
- A regulatory designation or sanction is applied to the vendor
Building these triggers into the programme structure, rather than relying on manual monitoring, is the difference between a responsive programme and one that discovers problems through incident reports.
Key Categories of Third-Party Information to Collect
The specific information collected during due diligence should be determined by the vendor's tier and the nature of the relationship. Across all tiers, the information landscape covers six core domains.
1. Information security and cyber posture
This is the most consistently required domain and the area where regulatory expectations are most explicit.
Minimum information to collect:
- Current certifications: ISO 27001:2022, SOC 2 Type II, Cyber Essentials Plus (for UK suppliers), PCI-DSS where relevant
- Penetration testing: scope, frequency, independent tester, most recent report summary
- Vulnerability management programme: patching cadence, critical vulnerability SLAs
- Incident response capability: documented plan, testing frequency, notification obligations
- Access controls: privileged access management, multi-factor authentication, identity governance
- Encryption standards: data at rest and in transit
- Business continuity and disaster recovery: RTO/RPO commitments, testing evidence
Regulatory note: Under DORA Article 30, contracts with ICT third-party service providers for critical or important functions must include provisions for information security, audit rights, and incident reporting. The information collected during due diligence should map directly to these contractual requirements.
2. Data protection and privacy
Where a vendor processes personal data on your behalf, data protection due diligence is a legal obligation under UK GDPR and the EU GDPR, not a discretionary check.
Key information to collect:
- Data processing agreement (DPA) in place and current
- Sub-processor register: who the vendor uses and where data flows
- Data residency commitments: where data is stored, processed, and backed up
- Data subject rights capability: response times, process, evidence of compliance
- Breach notification: contractual obligation and historical track record
- Cross-border transfer mechanisms: Standard Contractual Clauses, adequacy decisions, or UK IDTA
For vendors processing special category data, the due diligence depth should increase accordingly, including a Data Protection Impact Assessment (DPIA) where required.
3. Financial stability
A vendor that is financially distressed represents an operational risk that no security certification can offset. Financial due diligence is particularly important for critical and high-tier vendors.
Information to collect and assess:
- Most recent audited accounts (two to three years)
- Credit ratings or credit reference agency reports where available
- Key financial ratios: current ratio, debt-to-equity, operating margin trends
- Ownership structure: parent company, private equity backing, recent changes
- Customer concentration: if your contract represents a significant proportion of revenue, vendor viability is tied to your own decisions
- Any publicly disclosed financial difficulties, restructuring, or regulatory sanctions
4. Operational resilience and business continuity
Operational resilience has moved from a financial services concept to a broadly applicable regulatory obligation. Under DORA, in-scope entities must ensure their critical ICT third-party service providers maintain resilience standards consistent with their own obligations.
Key areas to assess:
- Business continuity plan: documented, tested, available for review
- Disaster recovery: separate infrastructure, tested failover, evidence of RTO/RPO achievement
- Concentration risk: reliance on a single cloud provider, data centre, or geography
- Subcontractor dependencies: fourth-party resilience for critical functions
- Incident management: historical incident record, root cause analysis practice, lessons learned
5. Regulatory compliance and legal standing
Information to collect:
- Regulatory registrations and licences relevant to the services provided
- Sanctions screening: OFAC, HM Treasury, EU sanctions lists
- Litigation and regulatory action: any material pending or recent proceedings
- Anti-bribery and corruption (ABC) programme: policy, training, due diligence on own supply chain
- Modern Slavery Act compliance: statement, due diligence process, supply chain visibility
- ESG and sustainability disclosures where required by your own reporting obligations
6. Governance and ethical standards
Governance quality is a leading indicator of risk management maturity. A vendor with weak governance is more likely to have gaps in every other domain.
Information to collect:
- Organisational structure: clear ownership, defined accountability for risk and compliance
- Board-level oversight of information security and risk
- Third-party risk management programme: does the vendor manage its own supply chain?
- Code of conduct and ethics policy
- Whistleblowing mechanism
- Training and awareness programme for employees
Key takeaway: These six domains are not independent. A vendor with strong information security but weak financial stability and no tested business continuity plan is not a low-risk vendor. Due diligence must be read holistically, not domain by domain.
Standardised Questionnaires and Frameworks
Bespoke questionnaires built from scratch for each vendor are inefficient and produce results that cannot be compared. Standardised frameworks solve both problems while providing the additional benefit of regulatory and industry recognition.
The Standardised Information Gathering (SIG) questionnaire
The Shared Assessments SIG is the most widely used standardised third-party risk questionnaire globally. The 2024 SIG update integrated Supply Chain Risk Management (SCRM) and AI risk domains, making it directly relevant to the current regulatory environment.
SIG variants:
- SIG Core: Full questionnaire covering all risk domains. Appropriate for critical and high-tier vendors.
- SIG Lite: Condensed version for medium and lower-risk vendors.
- SIG Cyber: Focused on cybersecurity controls. Appropriate for technology vendors where cyber risk is the primary concern.
The advantage of using SIG is vendor familiarity. Many large vendors complete SIG responses as a standard part of their customer due diligence process. A completed SIG from a vendor's library can significantly reduce the time to initial assessment, provided the response is current (within 12 months) and the scope matches your requirements.
Other frameworks relevant to UK and EU organisations
|
Framework |
Scope |
Best suited for |
|
NCSC Cyber Assessment Framework (CAF) v4.0 |
UK critical national infrastructure and regulated sectors |
Assessing vendors operating in or supplying to UK CNI |
|
NIST Cybersecurity Framework 2.0 |
Broad cybersecurity risk management |
Technology vendors; mapping to DORA technical standards |
|
ISO 27001:2022 Annex A controls |
Information security management |
Any vendor with significant data access; certification validation |
|
DORA RTS/ITS templates |
ICT third-party risk for financial services |
DORA Register of Information; contractual requirements |
|
Cloud Security Alliance CAIQ |
Cloud service providers |
SaaS, IaaS, PaaS vendors |
Designing a tiered questionnaire approach
Rather than selecting a single framework, most mature TPRM programmes use a layered approach:
- Universal intake questionnaire: A short set of questions (15 to 20 items) completed by all vendors. Covers basic identification, services provided, data access, and certifications held. Used to confirm tier placement.
- Tier-specific questionnaire: The main assessment. SIG Core for critical and high-tier; SIG Lite or equivalent for medium. Supplemented with sector-specific questions where relevant.
- Domain-specific supplements: Additional modules for specific risk dimensions. For example, a data residency supplement for vendors processing personal data outside the UK, or an AI risk supplement for vendors using AI in service delivery.
AI risk in vendor assessments
The EU AI Act is phasing in through 2027. For vendors deploying AI systems in high-risk categories (as defined by Annex III of the Act), organisations should now be collecting information on:
- The AI system's risk classification under the EU AI Act
- Conformity assessment status for high-risk systems
- Human oversight mechanisms
- Training data governance and bias testing
- Incident and near-miss reporting for AI systems
The SIG 2024 AI risk domain provides a starting point, but organisations with significant exposure to AI-enabled vendors should supplement it with questions mapped to the Act's specific requirements. The EU AI Act published in the Official Journal of the EU on 12 July 2024 is the authoritative reference.
Validating and Verifying Vendor Information
Collecting information is not the same as validating it. A questionnaire response is a vendor's self-assessment. Treating it as verified evidence is a programme design error that regulators and auditors will identify.
Validation is the process of confirming that what a vendor has stated is accurate, current, and complete. The depth of validation should match the vendor's tier.
Certification validation
Certifications are the most commonly cited but least consistently validated element of vendor due diligence.
ISO 27001: Certificates issued by UKAS-accredited certification bodies can be verified through the UKAS certified organisations register. Verify the certificate number, the scope statement (which defines what is actually certified), the expiry date, and the issuing body's accreditation status. A certificate that does not cover the services provided to your organisation is not evidence of the controls you are relying on.
SOC 2 Type II: Request the full report, not just the summary or management assertion. The full report contains the auditor's description of the system, the control objectives tested, the test procedures applied, and any exceptions noted. Exceptions in a SOC 2 Type II report are not automatically disqualifying, but they require a management response and evidence of remediation.
Cyber Essentials Plus: Verify against the NCSC Cyber Essentials certified organisations database. Confirm the scope covers the systems and infrastructure relevant to your relationship.
Evidence-based validation
Beyond certifications, validation requires collecting and reviewing primary evidence rather than accepting vendor statements.
|
Claim |
Validation approach |
|
Regular penetration testing |
Request the most recent executive summary; confirm scope, tester independence, and remediation status |
|
Patching within defined SLAs |
Request vulnerability scan summary or patch compliance report |
|
MFA enforced for privileged access |
Review access control policy; request evidence of configuration |
|
Business continuity plan tested |
Request most recent test report with date, scope, and outcomes |
|
Incident response plan in place |
Review the plan; confirm notification obligations are contractually documented |
|
Data processed in UK/EU only |
Request data flow diagram; confirm sub-processor agreements |
On-site and virtual assessments
For critical-tier vendors, questionnaire responses and document review should be supplemented by direct assessment. This may take the form of:
- On-site visit: Appropriate for vendors with significant physical infrastructure or data centre operations. Review the environment directly rather than relying on a vendor-produced tour.
- Virtual assessment: Structured interview with the vendor's CISO, Head of Risk, or equivalent. Use a structured question set derived from the questionnaire responses to probe gaps and inconsistencies.
- Shared audit: Where multiple customers share the cost and output of a single vendor audit. Increasingly common for large cloud providers where individual customer audits are not practical.
Fourth-party visibility
For critical vendors, due diligence should extend to the vendor's own critical subcontractors. This does not require a full assessment of every fourth party. It does require:
- A current list of critical subcontractors from the vendor
- Confirmation that the vendor has assessed those subcontractors
- Evidence of the vendor's own TPRM programme maturity
- Contractual flow-down of key security and resilience obligations
Under DORA, the concentration risk created by common fourth-party dependencies (particularly hyperscale cloud providers) is an explicit supervisory concern. The Register of Information must capture subcontracting chains, and competent authorities are actively reviewing concentration across the financial sector.
Validation principle: Every control you are relying on a vendor to maintain should have a corresponding validation activity. If you cannot validate it, you are assuming it rather than assuring it.
Technology as an Information Gathering Enabler
At scale, manual third-party risk management does not work. A programme managing hundreds or thousands of vendor relationships through spreadsheets and email cannot maintain the assessment cadence, evidence quality, or audit trail that the current regulatory environment requires.
The scale problem is real. A 2024 Deloitte survey found that 83 percent of organisations reported an increase in the number of third-party relationships over the previous three years, while 56 percent said their TPRM resources had not kept pace. The arithmetic of manual assessment at scale produces either a backlog or a programme that is less thorough than it appears.
Technology addresses this in four ways.
1. Centralised vendor register and workflow management
A dedicated TPRM platform provides a single register of all vendor relationships, with tier classifications, assessment status, evidence records, and issue tracking in one place. This replaces fragmented spreadsheets with a single source of truth that can be queried, reported on, and made available to auditors and regulators without manual compilation.
What good looks like:
- All vendors registered with standardised metadata
- Assessment workflows triggered automatically by tier and lifecycle events
- Evidence stored against the vendor record, not in email inboxes
- Issues tracked from identification through to confirmed remediation
- Audit trail of every assessment action, decision, and change
2. Automated questionnaire distribution and tracking
Questionnaire management is one of the most time-consuming elements of vendor risk programmes. Platforms that automate distribution, chase incomplete responses, and flag overdue submissions reduce the administrative burden significantly.
Efficiency gains in practice: SureCloud's TPRM platform delivers 50 percent faster vendor risk assessments and 40 percent faster vendor onboarding compared to manual processes, with a 35 percent increase in assessment consistency across the vendor population.
3. External threat intelligence integration
Questionnaire-based due diligence captures what a vendor tells you about their posture. External threat intelligence captures what is actually observable about their environment.
This includes:
- External attack surface monitoring: Exposed services, unpatched vulnerabilities, misconfigured assets visible from outside the vendor's perimeter
- Dark web monitoring: Credential exposure, data listings, threat actor discussion of specific vendors
- Financial intelligence feeds: Credit rating changes, Companies House filings, adverse media
- Regulatory and sanctions screening: Real-time alerts on regulatory actions, sanctions designations, and enforcement notices
Integrating external intelligence with questionnaire data produces a materially more accurate picture of vendor risk than either source alone.
4. Continuous monitoring and automated alerts
The shift from periodic assessment to continuous monitoring is the most significant operational change in mature TPRM programmes. Rather than reassessing a vendor annually and hoping nothing changed in between, continuous monitoring surfaces changes in real time and routes them to the appropriate owner for action.
Triggers that continuous monitoring should capture:
- New critical vulnerabilities in vendor-used software
- Changes in external attack surface (new exposed services, lapsed certificates)
- Adverse media or regulatory announcements
- Certification expiry approaching or lapsed
- Significant changes to vendor ownership or financial position
The NCSC's supply chain security guidance recommends continuous monitoring as a core element of supplier assurance for organisations with significant supply chain dependencies. For financial services firms under DORA, ongoing monitoring of ICT third-party service providers is not optional; it is a regulatory requirement.
The technology principle: Technology does not replace judgement. It removes the manual bottlenecks that prevent judgement from being applied consistently, at scale, across the full vendor population.
Moving from Periodic Assessment to Continuous Monitoring
The annual assessment model is structurally inadequate for the current threat and regulatory environment. A vendor assessed in January and not reviewed again until December can experience a significant security incident, a material change in ownership, a regulatory sanction, or a critical vulnerability in their infrastructure in the intervening months. The organisation would not know.
Continuous monitoring does not mean continuous reassessment. It means maintaining real-time awareness of material changes in a vendor's risk profile and acting on them when they occur.
What a continuous monitoring programme looks like in practice
Tier 1 (Critical vendors): Real-time external monitoring; automated alerts on any material change; formal reassessment triggered by defined events; quarterly relationship review with the vendor; annual full assessment regardless of events.
Tier 2 (High vendors): Automated alerts on material changes; event-triggered reassessment; six-monthly or annual full assessment.
Tier 3 (Medium vendors): Annual questionnaire refresh; event-triggered review where monitoring surfaces material changes.
Tier 4 (Low vendors): Periodic spot-check; event-triggered review for significant changes.
Defining material change
The programme needs a clear, documented definition of what constitutes a material change requiring action. Without this, monitoring alerts become noise rather than signal.
Material changes that should trigger a formal response:
|
Category |
Trigger |
Response |
|
Security incident |
Vendor discloses a breach or incident affecting services you rely on |
Immediate escalation; assess impact on your organisation; review contractual notification obligations |
|
Critical vulnerability |
CVSS 9.0+ vulnerability in vendor-used software with no patch available |
Assess compensating controls; request vendor response timeline |
|
Ownership change |
Acquisition, merger, or significant private equity restructuring |
Reassessment of financial stability and operational continuity; review contractual change of control provisions |
|
Regulatory action |
Sanction, enforcement notice, or fine from a relevant regulator |
Assess implications for the services provided; review contractual representations |
|
Certification lapse |
ISO 27001 or SOC 2 certificate expired or suspended |
Immediate request for status update; assess whether reliance on the certification in your own reporting needs to be flagged |
|
Financial distress |
Credit downgrade, adverse accounts, or public restructuring announcement |
Financial assessment; business continuity planning for the relationship |
Building the feedback loop
Continuous monitoring only adds value if the intelligence it generates reaches the right people and produces action. The programme needs:
- Defined ownership: Each vendor has a named risk owner responsible for acting on alerts
- Escalation paths: Clear routes from monitoring alert to risk committee or executive decision where the situation warrants it
- Issue tracking: Every alert that generates a response is tracked to closure with a documented outcome
- Reporting: Periodic summary of monitoring activity, issues identified, and resolution status for senior stakeholders and the board
The regulatory case for continuous monitoring
Continuous monitoring is no longer a maturity aspiration. It is a regulatory expectation for organisations in scope of DORA, NIS2, and the UK Critical Third Parties regime.
Under DORA Article 28(3), in-scope financial entities must monitor the performance and availability of ICT third-party service providers on an ongoing basis. Under the UK CTP regime, designated critical third parties are required to maintain and test their own operational resilience, and the firms that rely on them must maintain oversight of that resilience. The NIS2 supply chain security obligation, now enforceable, requires in-scope entities to address risks in supplier relationships as part of their overall cybersecurity risk management.
The practical implication: A programme that can only demonstrate periodic assessments will not satisfy these requirements. The evidence required is ongoing, not annual.
Building a Programme That Holds Up Under Scrutiny
The test of a third-party risk management programme is not whether it produces documentation. It is whether it produces assurance: a defensible, evidence-backed position on the risk your vendor relationships represent, updated as those relationships and their risk profiles change.
The framework in this guide builds to that standard in sequence.
The five elements of a defensible TPRM programme
|
Element |
What it requires |
Why it matters |
|
Complete inventory |
Every third-party relationship registered; fourth-party dependencies mapped for critical vendors |
You cannot assure what you cannot see |
|
Risk-based tiering |
Tier criteria documented and applied consistently; tier decisions reviewable |
Proportionate effort; defensible prioritisation |
|
Structured information gathering |
Standardised questionnaires; defined evidence requirements by tier; domain coverage across all six risk areas |
Consistent, comparable, complete assessments |
|
Evidence validation |
Certifications verified at source; evidence reviewed rather than accepted; on-site or virtual assessment for critical vendors |
Self-assessment is not assurance |
|
Lifecycle oversight |
Continuous monitoring for critical and high-tier vendors; event-triggered reassessment; issues tracked to closure |
Risk changes between assessments; the programme must too |
Common gaps that regulators and auditors identify
Based on the current regulatory environment and the obligations described in this guide, the gaps most frequently identified in TPRM programmes under scrutiny are:
- Incomplete vendor registers that do not capture all contractual relationships, particularly those procured outside the central IT function
- Tiering models not applied consistently, with critical vendors assessed at the same depth as low-risk ones
- Certifications recorded but not validated, with expired or out-of-scope certificates treated as current assurance
- No fourth-party visibility for critical vendors, particularly regarding hyperscale cloud dependencies
- Assessment findings not tracked to closure, with issues logged but no evidence of remediation
- Monitoring that is periodic rather than continuous, with no mechanism to surface material changes between formal assessments
Each of these gaps is addressable. None of them requires a complete programme rebuild. They require a structured review of current practice against the framework described in this guide, followed by targeted improvement in the areas where the gap is most significant.
The regulatory direction of travel
The trajectory is clear. Supply chain security obligations are expanding in scope, deepening in specificity, and moving from guidance to enforcement. The UK Cyber Security and Resilience Bill, expected to receive Royal Assent before April 2027, will extend NIS-style obligations to managed service providers and critical suppliers for the first time in UK law. The EU AI Act will require organisations to assess AI risk in their vendor relationships. The UK CTP regime will designate further critical third parties as the financial sector's dependency on concentrated technology providers continues.
Organisations that build structured, evidence-based TPRM programmes now will be better positioned for each successive regulatory development than those that continue to manage third-party risk reactively.
The information gathered during due diligence is not a compliance artefact. It is the foundation of every governance decision made about the vendor relationship. Collect it systematically, validate it rigorously, maintain it continuously, and the programme will hold up when it needs to.
Prove Your Security Programme Reduces Exposure — Not Just That It Runs Tests
Found this useful?
Choose SureCloud as a preferred source in Google and you will see more of our GRC guidance in Top Stories, AI Overviews and AI Mode. It takes one click and you can undo it at any time.
Let Gracie get the work done.
Gracie drafts summaries, evidence requests and audit narratives across your programme — you stay in control.
See Gracie in action or book a full platform demo →See what SureCloud costs
A short form, no sales call. Pricing built around your GRC estate.
Get PricingIDC names SureCloud the industry's first cross-domain agentic GRC platform
Read the independent analyst view on how SureCloud is redefining risk and compliance.
Download for freeFAQ’s
Why is third-party due diligence important?
Effective due diligence helps organisations identify vulnerabilities before they become incidents. It supports informed vendor selection, strengthens supply chain security and provides evidence that third-party risks are being appropriately managed.
What information should organisations collect during vendor due diligence?
-
Information should cover areas such as:
-
Information security policies and controls
-
Data protection and privacy practices
-
Financial health and business continuity
-
Incident response and disaster recovery
-
Regulatory compliance and certifications
-
Subcontractors and fourth-party relationships
-
Operational resilience and service dependencies
How should organisations classify third-party risk?
Organisations should use a risk-based tiering approach that considers factors such as the sensitivity of data accessed, service criticality, system connectivity, regulatory exposure and potential business impact if the supplier fails. Higher-risk vendors should receive more detailed assessments.
Are vendor questionnaires enough for effective due diligence?
No. Questionnaires provide a useful starting point, but responses should be supported by evidence. Organisations should validate important claims through independent reports, certifications, audit findings, security documentation and other relevant records.
How do DORA and NIS2 affect third-party risk management?
DORA places requirements on financial entities to manage ICT third-party risk, including oversight of contractual arrangements and critical ICT service providers. NIS2 strengthens supply chain security expectations for in-scope organisations, requiring them to consider vulnerabilities and the cybersecurity practices of suppliers and service providers.
Platform +
Frameworks +
Products +
Industries +
Resources +
Company +
London Office
Esavian House 181A High Holborn, London, WC1V 7QX, United Kingdom.
Tel: +44 20 8142 8890
US Headquarters
6010 W. Spring Creek Pkwy., Plano, TX 75024, United States of America
© SureCloud 2026. All rights reserved.
Gracie is a registered trade mark of SureCloud Limited in the United Kingdom.