A supplier providing authentication, encrypted connectivity or key management faces requests for inventories, migration support and a quantum-safe warranty. Those requests have different foundations. Some implement bank security and outsourcing obligations. Others reflect supervisory expectations, national planning targets or additional commercial protection. The contract needs to identify the source and scope of each commitment.
The practical choice is to promise a defined, evidenced migration outcome and continuing support. An unrestricted promise of immunity from future attacks creates exposure that a product roadmap or algorithm specification cannot substantiate. The following comparison covers North America, Europe, Asia, the Middle East, Africa, Latin America and Oceania, focusing on differences that change the agreement.
Start with the bank duty and supplier role
The bank should identify its regulated entity, the service it receives and the consequences of failure. Authentication supporting customer payments, a managed cryptographic platform and a software licence can engage different requirements. Classify criticality, customer-information access, subcontracting and overseas performance before selecting the contract annex.
In the EU, the Digital Operational Resilience Act (DORA) Article 28 keeps responsibility with the financial entity. Article 30(2) prescribes baseline terms for covered information and communication technology (ICT) services; Article 30(3) adds requirements where those services support critical or important functions. These include service descriptions, data arrangements, assistance, cooperation and termination rights, with stronger testing, audit and exit provisions for critical functions. The bank therefore has a legal basis for seeking practical migration evidence and control over changes. DORA, Articles 28–30.
The Monetary Authority of Singapore (MAS) Notice 658 uses a different classification: outsourced relevant services, ongoing arrangements, materiality and customer information. Material ongoing arrangements carry a defined package of contractual, diligence, audit and termination obligations. Other outsourced relevant services involving customer information have a separate set of requirements. The notice’s exclusions and exemptions must be tested against the actual service. Its general effective date was 11 December 2024. For relevant existing arrangements, the specified contractual terms apply from the next tenure extension or 11 December 2024, whichever is later. New arrangements and reclassification have separate paragraph 14 tests. Establish the actual tenure event before applying the transition. MAS Notice 658, paragraphs 2, 7, 12 and 14; Annexes A–D.
US federal information-security standards require covered banks to obtain appropriate service-provider safeguards and monitor them according to risk. The 2023 interagency third-party guidance supplies a wider contract framework while expressly creating no new requirements. Canadian federally regulated institutions have the Office of the Superintendent of Financial Institutions (OSFI) B-10 and B-13 expectations on third parties, inventories, technology lifecycle and cryptographic controls. Canadian provincial institutions require their own perimeter analysis. 12 CFR part 30, Appendix B, III.B–E; US interagency guidance, contract negotiation; OSFI B-10, Annex 2; OSFI B-13.
Supplier obligations can also arise directly. Covered US bank service providers face statutory examination and applicable incident-notification duties. EU critical ICT providers face designation-based oversight, while separate processor, digital-service or product-manufacturer roles can attract other legislation. Singapore’s bank-customer secrecy rules directly restrict specified recipients of customer information. A contract schedule should therefore record three things: the bank’s duty, the supplier promise supporting it and any law applying independently to the supplier. 12 USC §1867(c); 12 CFR §53.4; DORA, Articles 31 and 35; Singapore Banking Act, section 47(5), (7) and Third Schedule Part 2.
Check each date against its source status and system scope
A bank can negotiate supplier delivery earlier than its own target to allow integration, testing and controlled rollout. Record that earlier date as a contractual milestone, with its dependencies and acceptance criteria. National roadmaps and regulator publications need their own status labels.
- Hong Kong: Hong Kong Monetary Authority (HKMA) circular to authorized institutions. Relevant timetable as at 18 November 2026: Sectoral Quantum Preparedness Index (QPI) score 5–6 at the Q2 2028 survey; full sectoral readiness, QPI 10, by 2030. Contract consequence: Build bank-specific milestones and supplier evidence around the supervisory readiness objective.
- Singapore: Cyber Security Agency (CSA) guidance for critical information infrastructure (CII) owners. Relevant timetable as at 18 November 2026: CII migration plans through Sector Leads by 31 March 2027; contracts awarded from 1 January 2028 to procure and implement new CII systems with digital components that support quantum-safe technology or can support it by 31 December 2031, except systems without cryptographic assets; CII migration by 31 December 2031. Contract consequence: Confirm the bank’s CII status, affected systems and Sector Lead instructions.
- Singapore: MAS P019-2026 consultation. Relevant timetable as at 18 November 2026: Proposed general plans by 31 December 2027, critical systems by 31 December 2030 and remaining systems by 31 December 2034. Certain institutions would submit plans earlier; CII owners’ (CIIOs’) CII systems have a proposed 2029 date. Contract consequence: Track the consultation outcome and reconcile it with existing CSA expectations.
- Saudi Arabia: Saudi Central Bank (SAMA) supervised financial institutions. Relevant timetable as at 18 November 2026: Accurate, comprehensive cryptographic identification/classification procedures by end-Q4 2026; enterprise assessment and action plans by end-Q1 2027. Contract consequence: Obtain inventory and dependency evidence promptly enough for the institution’s actual requirements.
- EU coordinated roadmap. Relevant timetable as at 18 November 2026: Recommended first steps by end-2026; high-risk transition by end-2030; medium-risk transition by end-2035, with low-risk migration as feasible. Contract consequence: Classify each use and distinguish roadmap targets from DORA duties.
- UK: National Cyber Security Centre (NCSC) guidance, reinforced by Financial Conduct Authority (FCA) preparation expectations. Relevant timetable as at 18 November 2026: Plan by 2028; high-priority activities by 2031; completion by 2035. Contract consequence: Set achievable supplier milestones and preserve the bank’s time for safe change.
- Australia: Australian Signals Directorate (ASD) planning guidance. Relevant timetable as at 18 November 2026: Refined plan by end-2026; start priority migration by end-2028; completion by end-2030. Contract consequence: Use the guidance as a planning input, alongside the bank’s applicable prudential duties.
The Hong Kong dates come from the separate 2 November 2026 HKMA circular, pages 1–3. The jointly developed PQC Accountability and Controlled Transition (PACT) toolkit expressly states that it creates no new regulatory requirements or supervisory expectations. It supplies a useful method for evidence, ownership and controlled transition. Its questionnaire and maturity measures do not certify a supplier’s completed migration. PACT Reference Manual, page 2 and sections 4–6.
Singapore needs particular care. MAS’s 6 November 2026 consultation, with a closing date of 23 November 2026, describes a proposed circular that is not intended to be legally binding. The proposed 30 June 2027 plan submission covers CIIOs, domestic systemically important banks and NETS; the proposed 31 December 2029 completion date concerns CIIO CII systems. CSA’s guidance separately specifies its March 2027, 2028 and 2031 milestones, describes regulatory expectations and reserves stronger intervention. The procurement condition concerns contracts awarded to procure and implement new CII systems with digital components. Earlier awards fall outside that gate; systems under contracts continuing beyond 31 December 2031 remain subject to that migration date. A bank should confirm how the two routes apply before treating any later proposed date as an extension. CSA’s broader October 2026 advisory encourages other exposed organisations to plan by end-2027 and migrate by 2035. MAS P019-2026, paragraphs 1.1 and 2.2–2.5; CSA CII guidance, paragraphs 5–8 and FAQ 2; CSA advisory, 14 October 2026.
Saudi Arabia supplies a supervisory requirement for the financial institution. SAMA’s circular also requires priority-asset resilience plans and continuing committee attention. The immediate supplier task is evidence for identification, classification, risks and dependencies; the service’s implementation date still needs its own plan and agreement. SAMA circular 482021280, 27 August 2026, First–Fourth.
In North America, the source’s addressee is decisive. The US National Institute of Standards and Technology (NIST) IR 8547 became final on 27 October 2026 and sets out deprecation of quantum-vulnerable public-key cryptography after 2030 and disallowance after 2035 within its standards-transition framework. The 2026 US executive order and Office of Management and Budget (OMB) memorandum have separately scoped federal-agency stages. Canada’s government roadmap also addresses government systems. OSFI expressly describes its technology-risk bulletins, including the 2026 quantum-readiness bulletin, as discretionary sound practice. A private bank’s obligations require the additional banking-law, supervisory or contractual connection. NIST IR 8547, sections 2–4; OMB M-26-15; Canadian government roadmap, scope and milestones; OSFI bulletin status.
EU and German planning material also requires classification. The EU FAQ distinguishes high-risk uses from automatically classifying every critical-infrastructure system as high risk. Germany’s September 2026 guideline describes urgent recommendations and envisages binding specifications by competent bodies. For German institutions, DORA, the applicable German Banking Act (KWG) transition and the Federal Information Security Act (BSIG) financial-sector carveout must be read together. The supplier may independently fall within German cybersecurity law even where the bank has the DORA overlap exception. EU roadmap, section 4.1; FAQ, question 7.3; German guideline, section 4.1; BSIG §28(6).
The UK comparison should use the Prudential Regulation Authority (PRA) statement: the November 2024 SS2/21 version took effect on 31 December 2024; the March 2026 revision applies from 18 March 2027. The FCA’s November 2026 communication expects immediate preparation and refers to NCSC’s recommended milestones. Licentium’s earlier FCA quantum-risk coverage provides the news context; the agreement should identify the underlying authority and its actual status. PRA SS2/21 version history; FCA, 4 November 2026; NCSC migration timelines.
Make the inventory usable for a migration decision
The contract should require a versioned inventory connecting each service to the cryptography on which it depends. Include protocols, algorithms and parameters; libraries, hardware and firmware; certificates and trust chains; key custodians; data flows and required confidentiality or verification lifetimes; support expiry; and internal, group and external dependencies. Cover dormant, backup, fallback and recovery paths as well as ordinary production.
Record who supplied the information, when it was collected, how it was checked and what remains unknown. The PACT questionnaire usefully separates four claims: a product supports a capability; the capability is present in an installation; configuration permits it; and observation shows it in use. It also separates a bank’s required date from a supplier forecast, an existing contractual commitment and an evidenced achievement. Preserve a quarter or range as given. An authorised delivery agreement is needed to turn a planning response into a binding milestone. PACT Dependency Questionnaire, Questions C01–C12, Cryptography, Delivery and Guidance.
Specify access to the evidence needed for assessment and migration: technical documentation, scoped test reports, configuration records, relevant audit results, support rights and update notices. Distinguish ownership of bank data, supplier background intellectual property, commissioned work and the licences needed through transition and exit. A regulator-access clause and a commercial licence serve different purposes; both may be necessary. Hong Kong TM-G-1 expressly addresses performance, ownership, subcontracting and critical-provider assessment. TM-G-1, paragraph 7.1.1; SA-2, paragraphs 2.4–2.9.
Protect sensitive evidence through a defined disclosure route. Ordinary inventories should use key references and custody metadata. Raw private keys, passwords, seeds and unrelated customer records should remain outside them. Redaction, controlled review and suitably scoped independent assurance may protect supplier or other-customer information, provided the arrangement preserves the bank’s and regulator’s required access. The contract should identify an escalation route where the supplier cannot provide necessary evidence. PACT Questionnaire, Guidance, information handling; DORA Article 30(3)(e).
Local rules can change the delivery method
In the United Arab Emirates (UAE), begin with the bank’s regulator. Onshore Central Bank of the UAE (CBUAE) Article 13 requires written third-party terms, regulatory cooperation, relevant subcontractor protections and critical-operation controls. Material outsourcing under the bank standards requires prior non-objection; Article 13 also addresses outsourcing capable of significantly affecting critical operations. The Dubai International Financial Centre (DIFC) and Abu Dhabi Global Market (ADGM) have separate ICT-risk frameworks. Dubai Financial Services Authority (DFSA) guidance says provider self-verification alone is insufficient. Financial Services Regulatory Authority (FSRA) guidance permits review by the provider or bank, independent audit reports or other suitable evidence, with the method calibrated to system criticality and information sensitivity; it cautions that provider self-review may be inappropriate in some circumstances. A single self-attestation clause across all three regimes would miss those differences. CBUAE C1/2026, Article 13; C14/2021 Standards, sections 5, 7–8; DFSA GEN 5.5.3; FSRA GEN 3.5.2 amendments.
South Africa’s binding Joint Standard 2 of 2024 has applied since 1 June 2025. It expressly addresses third-party assets, cryptographic key lifecycles, established international algorithms, rigorous testing and supplier assurance. Its data-exit requirements preserve legally required retention. Kenya’s 2017 banking cybersecurity baseline supports inventory and third-party controls, while its data-protection legislation adds direct controller/processor security and written processing-contract requirements. The Kenyan regulator’s September 2026 replacement package remained a draft as at 18 November 2026, despite the consultation closing on 7 November 2026. South African Joint Standard 2/2024, paragraphs 7.1.1, 7.2.3, 7.2.6 and 7.7.1; commencement notice; CBK 2017 cybersecurity guidance, sections 1.2–1.3 and 3.3; CBK September 2026 consultation notice; Kenya Data Protection Act, sections 41–43; General Regulations, regulations 24–26.
For Brazil, a proposed migration service can fail at the key-access design. Article 3-A(I)(f) of National Monetary Council (CMN) Resolution 4.893 prohibits service companies from accessing the private keys associated with certificates used by the institution to sign messages in the specified National Financial System Network (RSFN) communication context. Establish whether the service and certificate use fall within that rule before permitting access. A promise of confidentiality, or the absence of raw-key export, is insufficient to settle the permitted access architecture. The rule is narrower than every cryptographic key used by a Brazilian bank. CMN 4.893, Articles 3-A, 16–17, as amended by CMN 5.274.
Brazil’s relevant outsourced-service contracts also need foreign-access and supervisory-cooperation assessment, usable data transfer before deletion, and resolution-continuity provisions. The December 2025 amendment’s adaptation date, 1 March 2026, concerned its cybersecurity changes. It supplies no basis for calling that date a universal PQC deadline. These requirements affect proposed service locations, transition assistance and termination rights. CMN 4.893, Articles 16–17; CMN 5.274, Article 2.
Mexico’s Credit Institutions Law (LIC) Articles 46 Bis 1–2 preserve bank accountability and the regulator’s provider-information and inspection route. The banking-rules (CUB) security provisions and amendments support infrastructure inventories, controlled change, encryption, testing and records for third-party infrastructure. A technical supplier must also be distinguished from a technology-based commission agent acting in the bank’s name. Before an offshore arrangement proceeds, confirm the CUB authorisation route and exemptions. Ley de Instituciones de Crédito, Articles 46 Bis 1–2; CNBV CUB publication.
Australia and New Zealand provide a useful contrast in contract classification. Australian Prudential Regulation Authority (APRA) CPS 230, effective 1 July 2026, prescribes terms for material service-provider agreements, including subcontractor responsibility, access, liability and exit. Its paragraph 57 exception requires both a listed provider category and the specified standard-term or no-formal-agreement condition. Standard terms alone do not exempt an ordinary technology supplier. CPS 234 security assessment remains relevant. CPS 230, paragraphs 46–61; CPS 234.
The Reserve Bank of New Zealand (RBNZ) BS11 outsourcing policy operates through the relevant bank’s conditions of registration and its defined scope. Its exempt list includes public key infrastructure (PKI) certificate management, but the cover condition requires the function not to be directly relevant to BS11’s outcomes. A critical authentication dependency needs that functional assessment. B2.9 distinguishes required statutory-management continuity and RBNZ access from a wider list of expected contractual subjects. Test continued recovery and separation when the bank is under stress, as well as ordinary service compatibility. BS11, A2, B2.9 and C2; exempt list, cover note and item 9.1.
Define acceptance for the service that will actually run
NIST’s three 2024 Federal Information Processing Standards (FIPS) serve different functions: FIPS 203 specifies ML-KEM for key encapsulation; FIPS 204 specifies ML-DSA signatures; FIPS 205 specifies SLH-DSA signatures. The contract should identify the function, standard, parameter set, product release and configuration, together with the exact validation claim and its evidence. Check publisher updates when fixing the baseline. NIST’s conformity cautions expressly leave implementation and overall system security to further assessment. FIPS 203; FIPS 204; FIPS 205, applicability and implementation provisions.
Define each protected path. A connection may use post-quantum key establishment while certificate authentication, update signatures or an upstream connection still use earlier mechanisms. A gateway protects the leg it terminates. Hybrid designs need an agreed construction, negotiated profile and downgrade controls. Preserve the distinction between present algorithm support, demonstrated interoperability and deployed protection across the agreed scope. PACT Reference Manual, sections 4.4–4.6.
An acceptance schedule should contain the following gates. These are contractual implementation choices supporting the applicable legal controls; local annexes identify additional mandatory conditions.
- Inventory and design. Required result: Agreed scope, priority uses, target configuration, owners and dependencies. Evidence for the bank’s decision: Versioned inventory; gap register; approved design; upstream commitments and cost assumptions.
- Integration testing. Required result: Candidate release meets specified functional, interoperability, security and capacity criteria. Evidence for the bank’s decision: Exact build/configuration; representative workloads; positive and negative tests; defects, retests and limitations.
- Controlled pilot. Required result: Approved exposure and operating limits, with usable monitoring and recovery. Evidence for the bank’s decision: Bank release authority; applicable approvals; measured service levels; tested fallback and incident contacts.
- Production acceptance. Required result: The defined service meets the agreed protection and performance criteria. Evidence for the bank’s decision: Deployment/configuration records, observed use, recovery results and a signed acceptance decision.
- Retirement and completion. Required result: Agreed predecessor mechanisms withdrawn, with controlled historical uses and continuing owners. Evidence for the bank’s decision: Checks of dormant and recovery paths; reconciled inventory; retention/deletion records; explicit residual exceptions.
Tests should cover failed handshakes, invalid signatures, certificate and key changes, peak workloads, constrained devices, partial rollout, failover, recovery and downgrade behaviour. Set measurable latency, throughput and recovery thresholds from the bank’s actual tolerances. A supplier laboratory report needs an applicability assessment before the bank relies on it for a different production configuration. PACT Reference Manual, sections 4.5–4.6 and 5.2–5.6.
Specify who can stop a release and what happens if rollback restores vulnerable cryptography. A temporary exception should identify its scope, reason, owner, expiry, compensating measures and exit. Keep the original missed milestone and outstanding criteria visible. Approval of an exception cannot waive a binding obligation or transform an unmet test into achieved completion. Licentium’s analysis of supplier change control for Singapore banks addresses the related discipline of approved baselines, evidence and release authority.
Allocate cost by the event and the party controlling it
A fixed price is workable when the parties can define the work. If legacy components, upstream capability or the acceptance scope remain uncertain, use a bounded discovery phase followed by a priced implementation baseline. State the assumptions, included capacity and duration, contingency rates, change authority and evidence needed to claim relief.
- Ordinary product migration. Proposed negotiation position: Identify the upgrades, licences, support and deployment assistance included in the existing or revised fee.
- Supplier failure to meet an agreed requirement. Proposed negotiation position: Require cure and necessary retesting at the supplier’s cost, subject to the agreed remedies and applicable law.
- Legacy replacement. Proposed negotiation position: List affected equipment, firmware, certificates and licences; allocate replacement and integration work expressly.
- Bank-requested expansion. Proposed negotiation position: Use a priced change order with revised dependency, testing and delivery commitments.
- Extended parallel operation. Proposed negotiation position: Define the included period, additional rates, security controls and authority to retire old paths.
- New standards or mandatory requirements. Proposed negotiation position: Require a documented applicability and impact assessment, options and a timely change decision.
- Upstream delay or non-cooperation. Proposed negotiation position: Require notice, proof of impact, mitigation and alternatives; allow only the relief justified by the actual affected dependency.
- Urgent remediation and rollback. Proposed negotiation position: Agree protective authority, spending limits, escalation and later price reconciliation before an incident.
DORA has a specific price rule: Article 30(2)(f) requires assistance for an ICT incident related to the supplied service at no additional cost or at a cost determined in advance. Planned migration work needs its own pricing provision. ASD’s November 2026 vendor guide recommends including PQC capability in base licensing and identifies premium add-ons as a concern; this is a negotiation benchmark whose applicability must be distinguished from a statutory pricing restriction. Its 2030 date is expressly a planning milestone for vendor discussion, aligned to jurisdiction, sector and risk. DORA, Article 30(2)(f); ASD vendor guide, footnote 4 and licensing/commercial tables.
Dependency relief should preserve the supplier responsibility and bank rights required locally. The EU regulatory technical standards on subcontracting require advance information and contractual controls for material changes, including objection and termination mechanisms. Australian CPS 230 requires relevant provider responsibility for subcontractor failure. A blanket exclusion for every upstream problem can frustrate those controls. Require the supplier to obtain the rights it promises, identify any unresolved gap before commitment and demonstrate a workable alternative where the dependency fails. Regulation (EU) 2025/532, Articles 4–6; CPS 230, paragraph 53.
Scope the warranty and preserve workable remedies
A useful warranty identifies what the supplier knows and controls: the accuracy of specified inventory information, conformity of named releases to agreed standards, performance against acceptance criteria, authority to supply updates and continuing remediation obligations. Define the date and environment to which each assurance relates. Address new vulnerabilities and standards through continuing support and controlled change.
The parties can negotiate broader risk, but the price, insurance, exclusions and remedies must reflect that choice. Read caps together with service credits, exclusive remedies, indemnities, termination rights and the practical cost of recovering the service. Different legal systems can change the result:
- New York and Quebec: in a pure contract dispute, the New York Court of Appeals’ Part 60 decision distinguishes meaningful contractual remedies from exculpatory or nominal-remedy provisions. In Prelco, the Supreme Court of Canada upheld a negotiated Quebec technology-contract limitation on facts involving sophisticated parties, simple fault, material injury and surviving remedies. Neither decision supplies a universal cap for a future result warranty. Part 60 Put-Back Litigation, 36 NY3d 342, 349, 352–359; 6362222 Canada inc. v Prelco inc., 2021 SCC 39, paragraphs 43–56 and 87–104.
- Germany: a guarantee or assumed procurement risk can increase responsibility under the German Civil Code (BGB) §276. Advance exclusion of intentional liability is prohibited. Business-to-business standard terms remain subject to §307 through §310, including transparency and protection of essential contractual rights. The special rule for specified financial transactions does not apply simply because the customer is a bank. BGB §§276, 307 and 310.
- UK, Hong Kong and Singapore: the relevant exclusion-control statutes can subject negligence and standard-business-term restrictions to reasonableness. Resources, available insurance, formation circumstances and the statutory burden matter. Territorial, pure-choice-of-law, international-goods and intellectual-property exceptions require classification of the actual service, hardware and licence. UK UCTA, sections 2–3, 11, 26–27 and Schedule 1; Hong Kong Cap 71, sections 3, 7–8, 16–17 and Schedule 1; Singapore UCTA, sections 2–3, 11, 26–27 and First Schedule.
- Saudi Arabia, South Africa and Kenya: distinguish the debtor’s own misconduct, employee conduct, the actual claim and statutory scope. Saudi Civil Transactions Law Article 173 limits contractual exemptions for the debtor’s own fraud or gross fault and separately addresses tort liability; agreed compensation has statutory adjustment rules. South Africa’s Fujitsu majority and Kenya’s Onyango and Gas Kenya decisions show that particular negligence or employee-risk allocations can be upheld. Applicable consumer-law restrictions need their own scope test. Saudi Civil Transactions Law, Articles 168, 173 and 178–180; Fujitsu v Schenker, [2023] ZACC 20, majority paragraphs 133–142; Securicor Courier v Onyango, [2008] eKLR; Gas Kenya v Technology Today, [2025] KEHC 8237, paragraphs 17–19.
Marketing and procurement statements also need support. Australian Consumer Law regulates misleading conduct and future representations; New Zealand’s Fair Trading Act addresses misleading and unsubstantiated representations. In New Zealand, the statutory route for contracting out between parties in trade has cumulative written-agreement and fairness conditions. An entire-agreement or non-reliance clause should be assessed against that route and the surviving enforcement powers. Australian Consumer Law, sections 4 and 18; New Zealand Fair Trading Act, sections 5C–5D, 9, 12A–12C and 43.
Settle the evidence and documents before signing
The signing pack should contain the service and cryptographic inventory, regulatory classification, approved design, dependency commitments, testing and acceptance schedule, allocation of costs, scoped warranties, incident/change procedures and an operational exit plan. Each local annex should identify mandatory terms, supervisory expectations and separately negotiated protection. Name the owners responsible for maintaining the evidence and deciding exceptions.
Before accepting a fixed price or completion promise, resolve five questions: which systems and cryptographic uses are included; which dependencies are committed and controllable; what the bank will test; which permissions and data/key constraints govern deployment; and which costs follow from defects, changes or delays. Where a dependency cannot be secured, choose an alternative component, a lawful narrower scope or a later release. Record the consequence for service coverage and the original target.
Completion should leave the bank with an accurate record of the protection achieved, any remaining obligations and the ability to make the next cryptographic change. Continuing support, usable evidence and lawful transition rights are part of that result.
Review the migration commitments
For review of bank supplier questionnaires, migration commitments and security warranties across the relevant markets, contact Licentium.