A crypto-asset service provider preparing to onboard institutional clients in the EU discovers that an authorised CASP faces a second compliance layer beyond the capital and conduct rules: the Digital Operational Resilience Act imposes ICT risk management, incident reporting, third-party oversight and testing obligations that apply from the day the authorisation goes live. The obligations sit parallel to MiCA's core regime and carry their own enforcement machinery. For a business planning to operate an exchange, custody wallet or token-issuance platform, the question is how to build resilience controls that satisfy both the national competent authority and the digital operational resilience framework without duplicating infrastructure or delaying the launch.
Under MiCA, a CASP authorised by a national competent authority in the EU must comply with the digital operational resilience requirements that govern ICT systems, outsourcing arrangements and incident response. The framework applies to financial entities, and an authorised CASP falls within scope. The operational resilience regime requires the firm to identify and classify ICT-related incidents, maintain a documented risk-management framework, test critical systems and oversee third-party service providers on whom the business depends. The thresholds, reporting windows and testing frequencies are set by technical standards that evolve alongside the MiCA implementation. Firms expanding into the EU must map these obligations early, because a gap in ICT governance can delay authorisation or trigger supervisory action after go-live.
This guide sets out the operational resilience rules that apply to an authorised CASP in the EU, the practical steps to implement them and the cross-border considerations that affect a business whose infrastructure, custody and banking sit in multiple jurisdictions. OBOLUS advises exchanges, custodians and token issuers on the compliance stack that underpins a MiCA authorisation. We work with firms to design resilience frameworks that align with both the digital operational resilience regime and the operational standards of the national competent authority. To discuss your situation before the authorisation clock starts, contact info@oboluslaw.com.
Who is subject to operational resilience rules?
An authorised CASP in the EU is subject to the digital operational resilience requirements as a financial entity under the applicable framework. The regime covers banks, payment institutions, investment firms and crypto-asset service providers that hold authorisation from a national competent authority within the EU. A CASP that registers under a transitional arrangement or operates under a third-country equivalence route does not escape the obligations; once the firm is authorised or recognised within the EU regulatory perimeter, the resilience standards apply. The coverage turns on the authorisation, not the firm's domicile or the location of its infrastructure.
The obligations extend to ICT systems, data management, outsourcing arrangements and incident response. ICT risk is defined broadly: it includes cybersecurity threats, system failures, data breaches and third-party service disruptions that affect the firm's ability to provide the authorised service. A custody wallet provider must consider the resilience of its key-management infrastructure, its node operators and its communication channels with clients. An exchange must map the dependencies on order-matching engines, liquidity providers, stablecoin issuers and fiat on-ramps. A token issuer must address the resilience of the smart-contract deployment process, the reserve-custody arrangement and the communications systems that publish reserve attestations.
The regime distinguishes between critical and important ICT third-party service providers. A provider is critical if a failure would materially impair the firm's ability to deliver its service or comply with regulatory obligations. The classification affects the depth of oversight and the frequency of review. In practice, a cloud-infrastructure provider hosting the exchange's order book, a custodian holding client assets and a node operator validating blockchain transactions are likely to qualify as critical. The national competent authority expects the CASP to document the classification and revisit it whenever the service perimeter changes.
A common assumption is that resilience obligations apply only to the largest platforms. In our cross-border practice, we see national competent authorities apply the framework proportionately but universally: a smaller CASP may adopt lighter testing schedules and simpler documentation, but the obligation to identify, classify and report incidents applies from day one. The proportionality principle does not exempt a firm from having a documented ICT risk-management framework; it adjusts the depth and frequency of review.
What is the ICT risk management framework?
The ICT risk-management framework is the documented process through which the CASP identifies, assesses, mitigates and monitors ICT-related risks. The framework must cover the firm's internal systems, the third-party providers on whom it depends and the interfaces between them. The national competent authority expects the framework to be proportionate to the firm's size, complexity and risk profile, but it must exist in writing and be approved by the management body. The framework is the foundation for incident classification, reporting and testing; a gap here delays authorisation and triggers follow-up once the firm is live.
The framework must address several components. Identification requires the firm to map its ICT assets, data flows and dependencies – the exchange's matching engine, the custody wallet's signing infrastructure, the token issuer's reserve-custody arrangement. Protection covers access controls, encryption, network segmentation and physical security measures. Detection includes monitoring systems, alert thresholds and anomaly-detection protocols that flag unusual activity before it escalates. Response defines the escalation procedures, the communication plan and the decision authority when an incident occurs. Recovery sets the recovery-time and recovery-point objectives for critical systems and the process for restoring service after a disruption.
The framework must be reviewed at least annually and updated whenever a material change occurs – a new service launch, a change of cloud provider, a shift in custody arrangements. The review must be documented, and the updates must be approved by the management body. For a business preparing to launch in the EU, the practical path is to draft the framework before the authorisation application, because the national competent authority will review it as part of the assessment. Retrofitting a framework after go-live is slower and invites supervisory scrutiny.
In a multi-jurisdiction build, the ICT risk framework often overlaps with other operational standards. A Singapore MAS licensee implementing the technology risk-management framework, a UK FCA-registered VASP maintaining information-security policies and an EU CASP documenting ICT risk management are solving similar problems under different labels. The cross-border challenge is to design a single framework that meets all three regimes without duplicating audit trails or governance meetings. We work with firms to map the overlapping requirements and build a unified control environment that satisfies the EU national competent authority, MAS and the FCA concurrently.
How does incident classification work?
Incident classification is the process of determining whether an ICT-related event must be reported to the national competent authority and, if so, within what timeframe. The regime requires the CASP to maintain an incident-classification policy that assigns every event to a severity category. The categories are typically major, significant and minor, and the classification turns on the impact, the duration and the number of clients affected. A major incident – a system outage that prevents all withdrawals for more than a defined threshold period, a data breach exposing client credentials or a third-party failure that disrupts a critical service – must be reported to the national competent authority within a short window. The reporting timeline is set by technical standards; the firm must not wait for a root-cause analysis before filing the initial notification.
The classification policy must be documented and approved by the management body. The policy defines the criteria for each category, the escalation path inside the firm and the reporting window to the regulator. The policy must address both internal incidents – a bug in the exchange's matching logic, a key-compromise event in the custody infrastructure – and third-party incidents, where a cloud outage or a stablecoin-issuer freeze affects the CASP's service. The challenge for a crypto business is that many incidents sit at the boundary: a temporary liquidity-provider failure might delay order execution for minutes, not hours; a chain congestion event might slow withdrawals without stopping them. The policy must define the threshold clearly, and the management body must be prepared to explain the classification if the national competent authority asks.
The reporting obligation applies to incidents that meet the severity threshold, not to every minor disruption. A firm that over-reports – flagging every transient API timeout as a major incident – creates noise and invites deeper review; a firm that under-reports – treating a six-hour withdrawal freeze as minor – risks enforcement. The practical approach is to document the classification logic, apply it consistently and report when in doubt. The national competent authority expects a learning posture: the CASP should analyse each incident, identify the root cause and update the framework to prevent recurrence. A pattern of similar incidents signals a control weakness, even if each event is below the reporting threshold individually.
What are the third-party oversight requirements?
Third-party oversight is the obligation to monitor and manage the ICT service providers on whom the CASP depends. The regime distinguishes between critical and important providers; a critical provider is one whose failure would materially impair the firm's ability to deliver its service or comply with regulatory obligations. For a critical provider, the CASP must conduct due diligence before onboarding, maintain a written contract that addresses resilience and exit rights, monitor the provider's performance continuously and conduct periodic audits or reviews. The depth of oversight must be proportionate to the dependency, but the obligation exists even if the provider is a large, well-known platform.
The contractual relationship must include several elements. The contract must define the service level, the incident-notification procedure and the exit arrangements – the CASP must be able to switch providers or bring the service in-house if the relationship ends or the provider fails. For a cloud-infrastructure provider, the contract must address data-location, encryption, access controls and audit rights. For a node operator, the contract must cover uptime, failover and the process for upgrading node software. For a stablecoin issuer supplying the exchange's settlement token, the contract must address reserve transparency, freeze procedures and redemption windows. The national competent authority expects the CASP to document the negotiation and to explain why the contract terms are adequate for the dependency level.
The oversight obligation extends to subcontractors. If the cloud provider subcontracts data storage to a fourth party, the CASP must know about it and assess the risk. If the custodian delegates key-signing to a hardware-security-module vendor, the CASP must understand the delegation chain. The practical challenge is that many crypto-infrastructure providers operate under standard terms that do not anticipate this level of transparency. A business preparing to launch in the EU should review its provider contracts early, identify gaps in resilience clauses and negotiate amendments before the authorisation application. Retrofitting contract terms after go-live is slower and may require switching providers mid-operation.
In a cross-border build, the third-party landscape is often fragmented. The exchange's matching engine sits in one cloud region; the custody wallet's signing keys sit with a hardware-security-module vendor in another jurisdiction; the stablecoin reserves sit with a Swiss custodian; the fiat banking sits with a Lithuanian or Maltese EMI. Each provider falls under a different legal regime, and the CASP must map the entire chain to satisfy the EU national competent authority. We work with firms to conduct a provider inventory, classify each dependency and draft the oversight procedures that tie the pieces together. The goal is a single view that shows the regulator how the firm would respond if any critical provider failed.
How do testing obligations work?
Testing obligations require the CASP to assess the resilience of its ICT systems through structured exercises. The regime mandates several types of test: vulnerability assessments, penetration tests, scenario-based resilience tests and, for certain firms, threat-led penetration tests that simulate advanced-adversary tactics. The frequency and depth of testing depend on the firm's risk profile and the criticality of its systems. A firm that operates a hot wallet handling high-value withdrawals faces stricter testing expectations than a firm offering custody for small-balance retail wallets. The national competent authority expects the CASP to document a testing plan, execute it on schedule and remediate any findings within a reasonable timeframe.
Vulnerability assessments scan the firm's systems for known weaknesses – unpatched software, misconfigured access controls, exposed APIs. The assessment must cover the CASP's internal infrastructure and, where contractually possible, the interfaces with critical third-party providers. Penetration tests simulate an attack by an external adversary; the tester attempts to breach the perimeter, escalate privileges and access sensitive data. The test must be conducted by a qualified external party, and the report must be shared with the national competent authority on request. Scenario-based resilience tests assess the firm's ability to maintain service during a disruption – a cloud-region failure, a DDoS attack, a key-compromise event. The test validates the recovery-time objectives documented in the ICT risk framework and identifies gaps in the response plan.
For firms classified as systemically important or operating at scale, the regime may require threat-led penetration testing – a simulation of advanced-adversary tactics that goes beyond a standard penetration test. The test is designed by a regulator-approved provider and follows a defined methodology. The frequency is set by the national competent authority; the firm cannot self-schedule. The practical challenge is that threat-led testing is resource-intensive, and the findings often require architectural changes rather than configuration tweaks. A business planning to operate at scale in the EU should budget for testing costs and include remediation time in the launch roadmap.
The testing obligation does not end with the initial authorisation. The CASP must re-test on a defined schedule – annually for most systems, more frequently for critical components. The national competent authority expects the firm to track findings in a register, assign ownership for remediation and close each item within a deadline. A pattern of open findings from past tests signals weak governance, even if no incident has occurred. In our licensing practice, we see firms struggle with testing more than with any other resilience obligation, because testing reveals problems that require money and time to fix. The route through is to test early – before the authorisation application – so that the major findings surface when the firm still has flexibility to adjust the architecture.
What are the cross-border considerations?
The cross-border reality for a crypto business is that the ICT infrastructure, the custody arrangement and the banking relationship rarely sit in the same jurisdiction as the authorisation. A CASP authorised in Lithuania may run its exchange software in an Irish cloud region, custody client assets with a Swiss provider and settle fiat through a Maltese EMI. Each element sits under a different legal regime, and the CASP must explain to the Lithuanian national competent authority how it monitors and controls the entire stack. The resilience framework must address the risk that a provider failure in one jurisdiction disrupts the service offered to EU clients.
Data location is a recurring issue. The digital operational resilience regime does not prohibit storing data outside the EU, but it requires the CASP to assess the risks and to ensure that the national competent authority retains access and audit rights. A cloud provider that stores encrypted backups in a third country must allow the regulator to inspect those backups on request. A custodian holding keys in a hardware-security module outside the EU must permit the CASP to audit the controls and, if necessary, to move the keys back into the EU. The practical path is to document the data-location rationale, ensure that the provider contracts include audit and portability clauses, and notify the national competent authority of any material change.
Exit planning is mandatory for critical third-party providers. The CASP must document how it would migrate to an alternative provider or bring the service in-house if the current provider fails or terminates the relationship. For a cloud infrastructure provider, the exit plan must address data extraction, API compatibility and the time required to redeploy the application in a new region. For a custodian, the exit plan must address key transfer, client notification and the regulatory approval process for the new custody arrangement. The national competent authority expects the exit plan to be realistic, not theoretical; the plan must include timelines, cost estimates and fallback options if the primary alternative is unavailable.
In a multi-licence build, the operational resilience requirements of the EU, Singapore, Hong Kong and the UK overlap but do not align perfectly. A firm holding a MAS payment-institution licence and an EU CASP authorisation must satisfy both MAS's technology risk-management expectations and the EU digital operational resilience framework. The testing schedules, the incident-classification thresholds and the third-party oversight procedures differ in detail. The cross-border efficiency gain comes from designing a single control framework that meets the strictest standard – typically the EU or Singapore – and then documenting the delta for each additional jurisdiction. We map the overlaps and the gaps in the licensing phase, so that the firm builds the framework once and adapts the documentation for each regulator.
The route through. A business expanding into the EU often discovers that the operational resilience obligations are more detailed and more intrusive than the core MiCA conduct rules. The framework touches every part of the technology stack, and the testing obligations surface findings that require architectural changes. The practical path is to start early – map the ICT dependencies, draft the risk framework and conduct a baseline vulnerability assessment before the authorisation application. Retrofitting resilience controls after go-live is slower, more expensive and invites deeper regulatory scrutiny. If you are planning to apply for a CASP authorisation or adapting an existing VASP licence to the MiCA regime, contact OBOLUS at info@oboluslaw.com to map the resilience obligations alongside the licensing roadmap.
How do you document the framework?
Documentation is the evidence that the CASP has implemented the operational resilience requirements. The national competent authority expects a written ICT risk-management framework, an incident-classification policy, a third-party register, a testing plan and the reports from completed tests. The documentation must be approved by the management body – the board or the equivalent governance structure – and must be updated whenever a material change occurs. The challenge for a crypto business is that the technology stack evolves faster than traditional financial infrastructure; a documented framework can go stale within months if the firm launches a new service, switches cloud providers or adds a custody partner.
The ICT risk-management framework is the anchor document. It must describe the firm's approach to identifying, protecting, detecting, responding to and recovering from ICT risks. The framework must name the roles responsible for each stage – the chief technology officer, the information security officer, the compliance officer – and must define the escalation path when an incident occurs. The framework must address both internal systems and third-party dependencies, and it must set the review frequency. The document is typically structured as a policy – high-level principles and governance – supported by procedures that detail the technical controls. The national competent authority reviews the framework during the authorisation process and expects the firm to follow it once live.
The incident register is the running log of ICT-related events. Every incident – major, significant or minor – must be recorded, classified, investigated and closed. The register must capture the date and time, the systems affected, the root cause, the impact on clients and the remediation steps. The register is a supervisory artefact; the national competent authority may request it during a routine review or after a major incident. A gap in the register – missing entries, incomplete root-cause analyses, unresolved actions from past incidents – signals weak governance and invites enforcement.
The third-party register lists every ICT service provider on whom the CASP depends, the classification (critical or important), the contract terms and the oversight procedures. The register must be updated whenever a provider is onboarded or offboarded. For a critical provider, the register must include the last audit date, the next scheduled review and the exit plan. The register is the map that shows the regulator how the firm would respond if a provider failed. In a cross-border build with providers in multiple jurisdictions, the register is also the tool that identifies single points of failure and jurisdictional concentration risk.
The testing plan sets the schedule for vulnerability assessments, penetration tests and scenario-based resilience tests. The plan must align with the risk profile and the criticality of the systems. The plan must name the external parties conducting the tests, the scope and the expected completion dates. After each test, the firm must produce a report that lists the findings, assigns ownership for remediation and sets a deadline for closure. The national competent authority expects the firm to track remediation progress and to re-test when the fixes are complete. A business preparing for a CASP authorisation should include testing costs and remediation time in the budget, because the findings from the first test often require infrastructure changes that delay go-live.
When should you engage counsel?
The operational resilience obligations apply from the day the CASP authorisation goes live, but the framework must be in place during the authorisation process. The national competent authority reviews the ICT risk-management framework, the incident-classification policy and the third-party register as part of the application. A firm that submits the application without a documented framework faces questions, delays and, in some cases, rejection. The practical timeline is to draft the framework, conduct a baseline vulnerability assessment and negotiate the key provider contracts before the application is filed. That sequence takes weeks, and the work must happen in parallel with the capital, governance and conduct-rule preparation.
Engage counsel when the operational architecture is defined but before the contracts are signed. The resilience framework must reflect the actual infrastructure – the cloud region, the custody arrangement, the banking relationship – and the provider contracts must include the audit and exit clauses that the national competent authority expects. A firm that signs a cloud contract without resilience clauses and then applies for a CASP authorisation must either renegotiate the contract or accept a gap in the compliance posture. Renegotiation mid-application is slower and may require switching providers if the current provider refuses to amend the terms.
For a business operating in multiple jurisdictions, the cross-border efficiency comes from designing a single operational resilience framework that meets the EU, Singapore and UK regimes concurrently. The framework should adopt the strictest standard – typically the EU digital operational resilience requirements or the MAS technology risk-management guidelines – and then document the delta for each additional jurisdiction. The testing schedules and the incident-classification thresholds will differ in detail, but the core controls – the ICT asset inventory, the access controls, the monitoring systems, the escalation procedures – are universal. Counsel maps the overlaps and the gaps, drafts the unified framework and prepares the jurisdiction-specific appendices that satisfy each regulator without duplicating the control environment.
The common mistake is to treat operational resilience as a post-launch compliance obligation. In our licensing practice, we see firms apply for a CASP authorisation with a placeholder framework – "we will implement the controls after authorisation" – and then discover that the national competent authority will not approve the application without evidence that the framework exists. The route through is to build the framework early, test it before go-live and treat it as part of the licensing roadmap rather than a post-launch task. If the operational resilience obligations are new territory for your team, reach OBOLUS at info@oboluslaw.com to design the framework alongside the licensing strategy.
Related practices
Related at OBOLUS
- Licensing & Registration for Digital-Asset Businesses – the CASP authorisation roadmap across EU member states and allied jurisdictions.
- Stablecoin Distribution and Reseller Arrangements – the contractual and regulatory treatment of third-party issuers in the payment flow.
- VASP Licensing in Isle of Man – a comparative view of a nearby third-country regime for firms considering parallel licensing strategies.
FAQ
How long does a crypto licence take to obtain?
The timeline for a CASP authorisation in the EU varies by member state and by the completeness of the application. National competent authorities in jurisdictions with established crypto supervision – Lithuania, Malta, Ireland – typically process applications within a matter of months if the documentation is complete. Delays arise from gaps in the operational resilience framework, questions about the third-party oversight procedures or incomplete ICT testing reports. The practical path is to draft the framework, conduct baseline testing and negotiate provider contracts before filing the application, so that the regulator reviews a complete package rather than a work in progress. Cross-border applications – where the firm operates in multiple jurisdictions or relies on non-EU providers – take longer because the regulator must assess the dependency chain and the exit planning.
Which jurisdiction suits my crypto business?
The choice of authorisation jurisdiction depends on the business model, the target client base, the infrastructure location and the banking relationship. A firm targeting institutional clients across the EU benefits from a member state with established supervisory expertise and a functional banking market for crypto businesses. Lithuania and Malta remain practical entry points; Ireland and the Netherlands are gaining traction for larger operations. The operational resilience obligations apply uniformly across the EU once MiCA is fully in force, so the jurisdiction choice turns on the speed of authorisation, the depth of supervisory engagement and the availability of banking rather than on differences in the resilience framework itself. A firm with existing infrastructure in a non-EU jurisdiction – Singapore, Dubai, Switzerland – should assess the cross-border implications and map the provider oversight requirements before committing to an EU authorisation.
Do I need a separate custody licence?
Custody is a regulated activity under MiCA, but whether a separate licence is required depends on the business model and the entity structure. A CASP authorised to provide custody services holds that permission as part of the authorisation; there is no separate custody licence within the MiCA framework. The question arises when a firm operates a multi-entity structure – an exchange entity and a custody entity, or an EU-authorised entity that delegates custody to a non-EU affiliate. In that case, each entity must hold the appropriate authorisation or recognition in its home jurisdiction, and the cross-border delegation must be documented and disclosed to the national competent authority. The operational resilience obligations apply to both entities, and the contracts between them must meet the third-party oversight standards even if they are part of the same group.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, so that the operational resilience framework, the third-party oversight procedures and the testing plan align with the authorisation strategy from the start. For a scoped assessment of your operational resilience posture ahead of a CASP application, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – Aisha advises on the CASP authorisation process across EU member states and the operational compliance frameworks that underpin digital-asset licensing in MiCA jurisdictions.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.