For fintechs, banks, and regulated financial services firms

Vendor Risk Management
for Financial Institutions

DORA, OCC, FCA, and EBA all require financial institutions to formally manage vendor risk — with documented registers, assessed vendors, and evidence available on demand. VendorAuditly generates regulator-ready evidence packs at $49/month, without the enterprise GRC price tag.

The regulatory reality for financial institutions
Financial institutions face stricter vendor risk requirements than any other sector. DORA (EU/EEA, effective Jan 2025), OCC Bulletin 2013-29 (US national banks), FCA SYSC 8 (UK), and EBA outsourcing guidelines all require formal third-party risk assessment, documented registers, and evidence of ongoing oversight. Regulators are asking. Do you have the evidence?

Regulatory framework

Four regimes. One vendor risk requirement.

Whether you are a UK-licensed payment institution, an EU fintech under DORA, a US bank overseen by the OCC, or an APAC firm with EBA-aligned requirements, the core obligation is the same: document your vendors, assess their risk, and prove it.

EU/EEA

DORA — Digital Operational Resilience Act

Effective January 2025. Applies to credit institutions, payment institutions, e-money institutions, investment firms, and crypto asset service providers. Requires an ICT third-party register, pre-contract due diligence, mandatory contractual provisions, and risk-proportionate ongoing assessments.

Art. 28: full third-party risk framework required
US

OCC Bulletin 2013-29 — Third-Party Relationships

OCC-supervised banks must maintain a risk management framework for all third-party relationships, with heightened oversight for critical activities. The framework must cover planning, due diligence, contract negotiation, ongoing monitoring, and termination.

Updated 2021 with interagency guidance
UK

FCA SYSC 8 — Outsourcing and Governance

FCA-regulated firms must maintain appropriate oversight of outsourced activities. Material outsourcing requires enhanced due diligence, contracts with specific provisions, and documented ongoing monitoring. FCA expects a risk register for material third parties.

EU

EBA Guidelines on Outsourcing Arrangements

Applies to EU credit institutions and investment firms. Requires a register of all outsourcing arrangements, risk assessments before entry, contractual safeguards, and periodic review. The EBA guidelines substantially overlap with DORA for ICT outsourcing.

The pattern across all four regimes
Every regulator demands the same four things: (1) a documented register of third-party vendors, (2) pre-contract due diligence, (3) risk-proportionate ongoing assessments, and (4) evidence you can produce on demand. The difference is in the specific contractual requirements and the definition of “critical.” VendorAuditly covers all four.

DORA Article 28 deep dive

What DORA specifically requires from your vendor risk programme

DORA Article 28 sets out the most prescriptive third-party risk requirements any financial services regulator has published to date. Here is what it actually demands — and what evidence you need to show.

Art. 28.2

ICT third-party register

Maintain a complete, up-to-date register of all ICT third-party service providers, including contractual arrangements. The register must distinguish between providers supporting critical or important functions and those that do not.

VendorAuditly: live vendor register with risk classification, exportable on demand
Art. 28.3

Pre-contract due diligence

Before entering a contract with an ICT provider, conduct and document due diligence proportionate to the risk. For critical/important functions, this includes a formal assessment of the provider’s ICT security, business continuity, and resilience capabilities.

VendorAuditly: DORA-specific questionnaire template, response tracking, dated evidence
Art. 28.4

Mandatory contractual provisions

Contracts with ICT providers must include: full service descriptions, data location provisions, audit rights, sub-outsourcing conditions, exit rights, and incident notification requirements. Document which contracts include each provision.

Art. 28.5

Ongoing risk-based assessments

Periodically re-assess the risk of ICT providers, with frequency proportionate to criticality. Critical/important function providers require annual assessment. Assessments must be documented with dated evidence of completion.

VendorAuditly: assessment scheduling by risk tier, dated completion records
Art. 28.7

Exit strategies for critical providers

For critical ICT providers, document how you would exit the relationship if required — including data migration, alternative providers, and transition timelines. This is particularly relevant for cloud and core banking providers.


The evidence gap

What regulators ask for vs what most firms have

Most fintech startups and challenger banks know they need vendor risk management. Few have the evidence organised and ready to produce. That gap is exactly what DORA enforcement targets.

❌
What most firms have
Before VendorAuditly
Vendor registerSpreadsheet, often outdated
Risk classificationsNone or informal
Due diligence recordsEmail threads
Certificates on fileEmail attachments, untracked
Assessment datesUnknown
Evidence to regulator2-5 days to assemble
✓
What VendorAuditly provides
DORA-ready at $49/month
Vendor registerLive, with risk classification
Risk classificationsCritical / High / Medium / Low
Due diligence recordsDated questionnaire responses
Certificates on fileStored, with expiry alerts
Assessment datesRecorded for every vendor
Evidence to regulatorOne-click export

Implementation

Build a DORA-compliant vendor risk programme in days, not months

No GRC consultant. No six-figure platform. No six-month implementation. VendorAuditly gets a regulated financial institution from spreadsheet to DORA-ready in a single week.

1

Build your ICT third-party register

Import your vendor list and classify each vendor by function type (critical/important or non-critical), data access, and operational dependency. This forms the foundation of your DORA Article 28.2 register.

2

Send DORA due diligence questionnaires

Use VendorAuditly’s DORA-aligned questionnaire template to assess ICT security, resilience, data location, and sub-outsourcing arrangements. Responses are dated and stored as evidence of pre-contract or periodic due diligence.

3

Upload and track compliance certificates

Store SOC2, ISO 27001, and cyber liability certificates for each vendor. VendorAuditly tracks expiry dates and alerts you 90, 60, 30, and 7 days before each certificate lapses — so your evidence file is always current.

4

Schedule annual assessments for critical vendors

Set reassessment schedules by risk tier. Critical ICT providers get annual assessment prompts. VendorAuditly tracks completion dates and surfaces overdue assessments — demonstrating to regulators that your programme is systematic, not ad hoc.

5

Generate your DORA evidence pack

When an inspection arrives, click export. VendorAuditly generates a complete evidence pack: ICT register, risk classifications, assessment records with dates, certificates on file, and audit trail. Everything DORA Article 28 requires, in a single export.


Common questions

Frequently asked questions

What are the vendor risk management requirements for financial institutions?
Financial institutions face vendor risk requirements from multiple regulators: DORA (EU/EEA, effective Jan 2025), OCC Bulletin 2013-29 (US national banks), FCA SYSC 8 (UK regulated firms), and EBA Guidelines on outsourcing. All require formal third-party risk assessment, documented vendor registers, and evidence of ongoing oversight. The documentation standard is the same — what varies is the specific contractual requirements and the definition of “critical” outsourcing.
What does DORA require for vendor risk management?
DORA Article 28 requires financial entities to: maintain a register of ICT third-party service providers with risk classifications; conduct pre-contract due diligence proportionate to criticality; include mandatory contractual provisions (audit rights, exit rights, SLAs, data location, sub-outsourcing conditions); and perform ongoing risk-based assessments with dated evidence. Critical ICT providers face the highest scrutiny and may be subject to direct DEIAA oversight.
Do fintech startups need to comply with DORA?
Yes, if they are licensed or operating in the EU/EEA. DORA applies to credit institutions, payment institutions, e-money institutions, investment firms, and crypto asset service providers — covering most licensed fintechs. Challenger banks, neobanks, and PSPs are all in scope. Even UK firms serving EU customers may face DORA requirements through their EU counterparties, particularly if they provide ICT services to DORA-regulated entities.
What evidence does a financial institution need for DORA vendor risk compliance?
DORA compliance evidence for vendor risk includes: a complete ICT third-party register with risk classifications, pre-contract due diligence records with dates, contractual clause documentation (exit rights, audit rights, SLAs, data location), ongoing assessment records with completion dates, and incident or breach notifications from vendors. VendorAuditly generates all of this in an exportable evidence pack — organised exactly as an inspector would expect to see it.
How is VendorAuditly priced for financial institutions?
VendorAuditly starts at $49/month — designed for fintech startups, challenger banks, payment institutions, and growing financial services firms that need DORA, FCA, and OCC vendor risk compliance without a $100,000+/year GRC platform. The $49/month plan includes the full vendor register, questionnaires, certificate tracking, risk scoring, and evidence pack export.
DORA-ready in days

Generate your DORA evidence pack at $49/month

ICT third-party register, risk assessments, certificate tracking, and one-click evidence export. Built for the financial services firm that cannot afford a $100k GRC platform.

No credit card required. Set up in under an hour.