Vendor Due Diligence for Digital Banking in Lebanon: What BDL Expects of Your Supplier

By Eurisko Team · Last reviewed November 2026

Mobile banking app, card stack and security shield

In Lebanon the bank stays accountable for what its technology supplier does. Banque du Liban regulates electronic banking through Basic Circular 69, rewritten in January 2026 to require local data hosting and set terms for third parties that process customer data, and supervises the technology with the Banking Control Commission. It has no single instrument on technology outsourcing that we could find, so the bank’s own due diligence and contract do most of the work. That file covers the supplier’s security, resilience, data location, sub-contractors, financial strength, audit access and exit.

This guide covers what BDL’s circulars require, the international baseline to benchmark against, how the Gulf markets differ, the evidence to request in each area, the contract clauses and what to keep monitoring.

Lebanon: what do BDL’s circulars say about technology suppliers?

We did not find a single Banque du Liban instrument dedicated to technology outsourcing by banks, so in Lebanon two basic circulars set the frame and the contract carries more of the weight. Basic Circular 69 (Basic Decision 7548) governs electronic banking and financial operations, and its articles were replaced in full by Intermediate Decision 13791 of 9 January 2026, so a supplier quoting the older text is out of date. Under the current text a bank notifies BDL in writing ninety days before starting or promoting an electronic operation, or before changing one already declared, describing the services, the associated risks and the technical procedures in place. It must cooperate with technical control by BDL or the Banking Control Commission, inform them of any amendment to its working procedures and technical rules, and have its external auditors report each year, by the end of April, on its electronic operations.

Two articles bear directly on the supplier. Article 7 requires all data on customers and executed operations to be stored in Lebanon. Article 8 covers any contract with a third party that processes customers’ personal data: the bank must inform the customer and obtain explicit written consent limited to specific purposes, and the contract must confine the third party to the original purpose, bind it to the utmost security standards, and leave the bank responsible towards the customer for the protection of the data and for any misuse by the third party.

For a platform purchase this has four practical consequences. A new or replaced digital channel is a notifiable change, so build the ninety days into the plan. Settle where every environment is hosted before the notice is filed. Write the Article 8 terms into the supplier contract and check your customer consents cover the supplier’s processing. And agree at the outset what evidence the supplier will provide for supervisors’ technical control and for the annual auditor report.

Basic Circular 128 (Basic Decision 11323) draws one more line: banks and financial institutions are prohibited from outsourcing compliance monitoring, in whole or in part. Beyond that, use the Basel Committee’s principles as the benchmark for due diligence, contract content and exit, since correspondent banks and auditors will measure against them. BDL amends its basic decisions through intermediate circulars, so check the current consolidated text before you file.

Why can’t a bank outsource accountability?

The international baseline is the Basel Committee’s Principles for the sound management of third-party risk, published in December 2025. Its first principle states that the board of directors has ultimate responsibility for the oversight of the bank’s third-party risks. The principles that follow track the life cycle of a supplier relationship: risk assessment, due diligence before entering an arrangement, a legally binding written contract, onboarding, ongoing monitoring, business continuity, and exit plans for both planned and unplanned termination.

On due diligence the Committee is specific. A bank should assess the supplier’s operational and technical capability, its internal controls including cyber risk, its ability to manage its own supply chain (the “nth parties”), its continuity and disaster recovery plans, its financial soundness, the jurisdictions the service depends on, and its track record, including complaints, investigations or litigation. The Committee’s earlier Principles for operational resilience add a useful test: verify that the third party has at least an equivalent level of operational resilience to the bank’s own for the critical operations it supports.

National rules in the region follow the same logic and add two things: a filing with the central bank, and rules on where data may sit.

How the neighbours differ

Saudi Arabia: SAMA’s Rules on Outsourcing require a written no objection before any material outsourcing and before any outsourcing to a provider located overseas, and its Cyber Security Framework requires SAMA approval before a bank uses hybrid or public cloud services, which should in principle be located in the Kingdom.

UAE: the CBUAE’s Outsourcing Regulation for Banks (Circular 14/2021) and its Standards require the Central Bank’s non-objection before a material business activity is outsourced, an outsourcing register, and a master system of record, including all confidential customer data, kept within the UAE.

Kuwait: the Central Bank of Kuwait’s Cyber and Operational Resilience Framework, issued in December 2025, carries a dedicated set of third-party risk management baselines covering contracts, sub-contracting, exit strategy, data storage, cross-border transactions and the use of cloud services.

Oman: the Central Bank of Oman’s circular BM 1080 restricts outsourcing to non-core activities and asks for prior approval in the exceptional cases where a core activity is outsourced, with core broadly meaning anything that touches customer data or the bank’s systems.

If your supplier will serve entities in more than one of these markets, run the due diligence once to the strictest standard and file separately with each regulator.

Is your engagement “material outsourcing”, and does it need approval?

Decide this before the shortlist, not after the award, because it sets your timeline. The SAMA and CBUAE texts define materiality in near-identical terms: an activity that, if disrupted, could have a material or significant impact on the bank’s business operations or its ability to manage risks. Both then list factors to weigh, including the effect of a supplier failure, the bank’s ability to keep meeting regulatory requirements, how hard the supplier would be to replace and whether customer data is shared.

A digital banking platform is the channel through which customers reach their accounts and it processes customer data, so treat it as material unless your compliance function documents why it is not. A plain licence for software that the bank installs and runs entirely on its own infrastructure, with its own staff, may fall outside the definition of outsourcing altogether; a hosted or managed service, or a supplier that operates and supports the platform on a continuing basis, usually falls inside it. Put the classification in writing either way, and ask the supplier early for the documents the filing needs.

What should you check, and what evidence should you ask for?

Ask for documents, not assurances. For each area below there is a piece of evidence a serious supplier can hand over under a non-disclosure agreement, and a warning sign that should slow you down. Score each area on the evidence you actually received, and record who reviewed it and when: that record is what your regulator and your internal audit will ask to see.

Three areas deserve more time than they usually get. Sub-contractors: the supplier’s hosting provider, its support partner and any offshore development centre are your fourth parties, and several regulators expect you to know and approve them. Key-person risk: ask who would maintain the product if five named engineers left. Exit: ask the supplier to describe, step by step, how you would leave.

Vendor due diligence: evidence to request and red flags
AreaEvidence to requestRed flag
Information security managementPolicies, ISO/IEC 27001 certificate with scope statement and Statement of Applicability, latest audit findingsCertificate scope excludes the product or team you are buying
Secure development and testingDevelopment lifecycle description, code scanning results, recent independent penetration test summary and remediation logNo independent test in the past year, or findings left open
Data residency, hosting and cloudData flow diagram, list of hosting locations, cloud provider and region, who holds encryption keysCannot say where backups, logs and support copies sit
Business continuity and disaster recoveryContinuity and recovery plans, recovery time and recovery point objectives, last test reportPlans exist but have never been tested
Sub-contractors and fourth partiesFull list by function and country, the contracts’ flow-down terms, change notification processSub-contractors disclosed only after signature
Financial viability and key peopleAudited financial statements, ownership, client concentration, succession and staffing planDependence on one client or a handful of individuals
Regulatory track recordReferences from regulated banks, disclosed incidents, litigation and regulatory findingsNo reference will take a call
Access and audit rightsDraft clause granting the bank, its auditors and its regulator access to premises, data and staffAudit limited to a questionnaire or a shared report
Exit, transition and escrowExit plan, data export formats, transition support terms, source-code escrow agreementNo exit plan, or data returned only in a proprietary format

What does an ISO/IEC 27001 certificate actually cover?

ISO/IEC 27001 is the international standard for an information security management system. A certificate shows that an accredited body audited the supplier’s management system against the standard, which is worth having. It is issued for a stated scope, and the scope is where buyers get caught: it may cover one office, one hosting service or one business unit, and not the product team that will write and support your software.

So read the scope statement, ask for the Statement of Applicability (the list of controls the supplier applies and those it excludes), and check the certification body and expiry date. A certificate is not a test of the product: it does not replace a penetration test of the release you will run, nor a review of how the platform is configured in your environment. A supplier that is working towards certification should say so plainly and show you its policies, its gap assessment and its target date instead.

Which contract clauses does the regulator expect?

Due diligence findings only bind the supplier once they are in the contract. The Basel principles and the regional rules converge on a common list, and a contract that omits any of these will draw questions:

  • Scope, service levels and performance measures, with remedies when they are missed.
  • Access, audit and information rights for the bank, its internal and external auditors, and the regulator, including on-site access and direct requests from the regulator to the supplier.
  • Data: ownership stays with the bank and its customers, the locations where data is processed and stored, confidentiality, segregation from other clients’ data, and return and deletion on termination.
  • Security obligations and notification of incidents and data breaches without undue delay.
  • Sub-contracting: whether it is allowed, prior notice or approval for changes, and the same obligations flowed down.
  • Business continuity and disaster recovery commitments, including recovery objectives and participation in the bank’s tests.
  • Termination and exit: grounds, notice periods, transition support, handover of data and documentation, and source-code escrow where the bank depends on the supplier’s code.
  • Liability, indemnity and insurance, governing law and jurisdiction, and a mechanism to amend the contract when regulation changes.

What must you keep monitoring after signature?

Due diligence is not a gate you pass once. The Basel principles ask banks to assess and monitor a supplier’s performance, and changes in its risk and criticality, on an ongoing basis and to report to the board. In practice that means a named owner for the relationship, an entry in the outsourcing register, service reports reviewed on a fixed cycle, renewed certificates and penetration test summaries each year, notice of any change of sub-contractor or hosting location, and a joint continuity test.

Keep the exit plan alive as well. Review it yearly, confirm the escrow deposit matches the release in production, and rehearse a data export. Regulators in the region also expect to hear about change: SAMA’s rules, for example, require a bank to notify it immediately when a material outsourcing agreement is terminated, and the CBUAE’s regulation requires immediate notice of a material breach of an outsourcing agreement.

How Eurisko fits

Eurisko has delivered banking software since 2009 with more than 200 engineers, and expects to be put through the process described above. Eurisko DXP, our digital banking platform, runs in front of any core and is deployed inside the bank’s own estate, on-premises or in its private cloud, so data, logs and encryption keys stay with the bank and the residency question is answered by the bank’s own infrastructure. Its controls are aligned with ISO/IEC 27001, releases go through code scanning and independent penetration tests, and every release ships with a software bill of materials.

One point of honesty: Eurisko’s ISO/IEC 27001 certification is in progress, not yet held. If your procurement policy requires a supplier that already holds the certificate today, or you want a platform hosted and operated for you as a public cloud service, we are not the right choice at this moment. If you can assess controls on the evidence, we will share ours under a non-disclosure agreement.

FAQ

Frequently asked questions.

Does a Lebanese bank need to tell BDL before launching a new digital channel?

Yes. Under Basic Circular 69 (Basic Decision 7548) as replaced in January 2026, a bank notifies Banque du Liban in writing ninety days before starting or promoting an electronic banking operation, or before changing one already declared. It must also inform BDL and the Banking Control Commission of changes to its working procedures and technical rules, and store customer and transaction data in Lebanon. Check the current consolidated text, since BDL amends it by intermediate circular.

Is buying a digital banking platform considered outsourcing?

It depends on who runs it. A supplier that hosts, operates or supports the platform on a continuing basis is performing an activity the bank could perform itself, which is how regulators such as SAMA and the CBUAE define outsourcing. Software the bank installs and operates entirely with its own staff may fall outside the definition, but the classification should be documented by compliance in either case.

What documents should a bank request from a software vendor during due diligence?

At minimum: security policies and any ISO/IEC 27001 certificate with its scope statement, a recent independent penetration test summary, a data flow diagram with hosting locations, continuity and disaster recovery plans with the last test report, the list of sub-contractors, audited financial statements, references from regulated banks and a draft exit plan. Review them under a non-disclosure agreement and record who reviewed what.

Does an ISO/IEC 27001 certificate mean a vendor is secure?

It means an accredited body audited the vendor’s information security management system within a stated scope. It does not test the product, and the scope may exclude the team or service you are buying. Read the scope statement and the Statement of Applicability, and still ask for a penetration test of the release you will run.

Do we need source-code escrow?

Consider it whenever the bank depends on code it does not own and could not replace quickly. SAMA’s Cyber Security Framework and the CBK’s third-party baselines both mention escrow arrangements where applicable. An escrow is only useful if the deposit is updated with each release and the release conditions are clear, so verify both each year.

Let’s build

Have something ambitious in mind?

Start a project →

Popular searches

Jump to