DORA: 10 evidence items a Moroccan ICT provider should prepare for an EU financial client
Ten evidence items for a Moroccan ICT provider answering an EU financial customer’s DORA due diligence across service, incidents, audit, recovery, and exit.
DORA Moroccan ICT provider: a company established in Morocco is not automatically a financial entity subject to the EU regulation. It may nevertheless receive concrete DORA requirements when it provides cloud, software, data, cybersecurity, or support services to a bank, insurer, payment institution, or another EU financial entity.
The practical response is not to promise a “DORA certification.” The provider should define the service, understand the customer’s classification, and prepare evidence it can genuinely maintain. The ten items below support due diligence, contract negotiations, and operations without replacing legal analysis.
What is DORA and why can it affect a Moroccan provider?
DORA is Regulation (EU) 2022/2554 on digital operational resilience in the financial sector. It has applied since 17 January 2025. Its main duties address covered financial entities. ICT third-party providers experience them through customer selection, contracts, monitoring, incidents, audits, testing, and exit planning.
An official ESMA answer on non-EU providers states that the EU financial entity remains responsible for operational resilience and must validate that a non-EU provider does not prevent DORA compliance. Only ICT providers formally designated as critical enter the direct EU oversight framework described by the authorities.
Evidence 1 — A precise description of the ICT service
Describe functions, users, components, data, dependencies, support hours, interfaces, environments, and responsibilities. Separate what belongs to the provider, customer, public cloud, and each subcontractor.
The financial customer decides whether the service supports a critical or important function, but the supplier must provide the facts needed for that decision. Keep the service sheet versioned so the contract and operating model refer to the same scope.
Evidence 2 — A map of locations and data flows
Article 30 requires contracts to identify the regions or countries where services are delivered and data is processed or stored, with advance notice of changes. Distinguish production, backups, logs, support, disaster recovery, and external tools.
Record source, destination, data category, encryption, access, retention, and return mechanism. Kanteek’s guide to data hosting in Morocco separates residency, transfers, access, and recovery. Data-protection conclusions require qualified legal review.
Evidence 3 — The complete subcontracting chain
List the cloud, monitoring, support, messaging, security, CDN, backup, and SaaS providers required by the service. For each, record the role, country, data access, substitutability, and change time.
The delegated regulation on ICT third-party policy requires proportionate due diligence by the financial entity. Prepare a change-notification process, an objection route where agreed, and an alternative if an essential subcontractor fails.
Evidence 4 — Measurable service levels
Replace “high availability” with indicators: uptime, latency, acknowledgement time, recovery time, backup success, update frequency, and the calculation method. Link each threshold to a data source, period, exclusions, and corrective action.
Keep reports the customer can review. Cloud observability connects logs, metrics, and traces to actionable alerts and supports explanations when a service level is missed.
Evidence 5 — Incident assistance
The contract should define assistance when an incident related to the ICT service occurs, either without additional cost or at a cost set in advance. Specify channels, hours, severity levels, escalation times, owners, and information delivered.
The provider should not decide for the customer whether an incident is “major” under DORA. It should deliver reliable facts: timeline, affected systems and data, observed impact, containment, restoration, and updates.
Evidence 6 — Security controls actually operated
Provide a service-specific inventory of identity, least privilege, secrets, encryption, segmentation, patching, vulnerabilities, hardening, logging, and access reviews. Attach an owner, frequency, and recent evidence to each control.
Kanteek’s guides to secrets management and Zero Trust cover two useful foundations. Share evidence through a secured channel with authorised recipients and an agreed classification.
Evidence 7 — Tested continuity and recovery
Continuity plans should cover scenarios, roles, dependencies, communications, degraded modes, and return-to-normal criteria. Recovery plans should define backups, objectives, emergency access, and restart order.
The decisive evidence is a test report: date, scenario, data, outcome, gap, action, and retest. The cloud disaster recovery guide links RTO, RPO, restoration, and business decisions. Never present an untested objective as a guarantee.
Evidence 8 — A proportionate audit package
DORA calls for access, inspection, and audit rights, especially for services supporting critical or important functions. Prepare architecture, relevant policies, test reports, control lists, significant incidents, subcontractors, restoration results, and remediation tracking.
Contracts should define notice, confidentiality, security, scope, pooled audits where appropriate, competent-authority access, and finding management. External assurance may help, but it does not replace contractual rights or service-specific evidence.
Evidence 9 — Data return and an exit plan
The customer needs accessible data in case of termination, insolvency, or service discontinuation. Define formats, volume, encryption, transfer, timelines, integrity verification, residual deletion, and transition assistance.
Test a sample export. A viable exit also covers configurations, useful logs, dependencies, and knowledge needed for continuity. Termination rights alone do not create an executable migration.
Evidence 10 — A verifiable DORA contract matrix
Map each contract requirement to a legal reference, deliverable, owner, and evidence. The official DORA text includes service descriptions, locations, data protection and return, service levels, incident assistance, authority cooperation, termination, and stronger provisions where relevant.
The matrix distinguishes provisions for all ICT services from additional terms for services supporting critical or important functions. It prevents the supplier from accepting obligations it cannot operate or evidence it does not possess.
A four-workshop preparation method
Workshop 1 — Scope and classification
Bring together sales, legal, security, and operations. Describe the service, customer, supported function, data, countries, and subcontractors. Record questions the customer must decide.
Workshop 2 — Technical evidence
Collect service measurements, controls, incidents, continuity, restoration, and exports. Mark each item available, incomplete, pending test, or not applicable, with a reason.
Workshop 3 — Contract and gaps
Compare draft clauses with real capabilities. Estimate changes such as longer retention, on-call support, audits, exports, tests, or subcontractor replacement. Obtain qualified legal validation.
Workshop 4 — Simulation
Simulate an incident and an exit. Check contacts, timelines, evidence, decisions, and dependencies. Turn every gap into an owned and dated action.
Common mistakes
- claiming every Moroccan provider is directly subject to DORA;
- promising a DORA certificate instead of maintaining evidence;
- hiding processing countries or subcontractors;
- accepting incident timelines without matching on-call capacity;
- providing generic policies unrelated to the service;
- confusing an available backup with tested restoration;
- signing audit rights without a secure process;
- providing termination rights without export and transition assistance.
FAQ — DORA and Moroccan ICT providers
Does DORA directly apply to every Moroccan IT company?
No. Its main obligations address covered financial entities. A Moroccan supplier is often affected through the customer’s due diligence and contract. Direct oversight applies to ICT providers designated as critical under the EU mechanism.
Can the customer request an audit?
Yes. Contracts may need access, inspection, and audit rights, especially for a critical or important function. The process should be proportionate and secure without making the right ineffective.
Must all data stay in the EU?
DORA does not impose a universal rule that all data remain in the EU. It requires locations and risks to be documented. Data-protection law and customer requirements may add constraints.
Is an ISO certification sufficient?
No. It may provide useful assurance, but the customer still needs to assess the service, contract, subcontractors, incidents, continuity, audit rights, and exit arrangements.
Where should a provider start before answering a DORA questionnaire?
Start with the service sheet, countries, subcontractors, service levels, incident process, controls, latest restoration test, and export format. Identify gaps before answering.
Prepare usable evidence, not a promise
For a DORA Moroccan ICT provider, a reasonable goal is to make the service understandable, measurable, auditable, and reversible for the EU financial customer. The customer’s regulatory responsibility does not remove the supplier’s technical and contractual commitments.
Kanteek can support technical scoping, architecture, observability, recovery, and documentation through Cloud & DevOps and Consulting & Strategy. Final regulatory classification and legal drafting require qualified professionals.
