DORA Applications Are Failing—Here's What Malta's Regulator Just Revealed
Alejandro MartĂnez ·
Listen to this article~3 min

Malta's financial regulator just published its first review of DORA authorisation applications from 2025. From AI-generated policy gaps to generic exit plans, here's what supervisors found—and what 2026 applicants need to fix.
The Malta Financial Services Authority (MFSA) just dropped its first detailed look at what supervisors actually found while reviewing authorisation applications under the EU's Digital Operational Resilience Act (DORA) during 2025. And honestly? The results are a wake-up call for anyone planning to apply.
The findings apply equally to first-time applicants and to existing licence holders chasing an additional licence or an extension. Same problems, different files. That tells you something important: these aren't rookie mistakes. They're systemic gaps.
### The AI Problem Nobody Expected
Chief among the MFSA's concerns was the widespread use of generative AI in application documents. Now, the regulator isn't against AI. You can absolutely use it to help draft or structure a document. But there has to be a human review layer on top—someone who actually checks that the data in your policies is accurate, complete, and applicable to your business.
Skipping that step is where things fall apart. A policy that reads well but doesn't match your actual operations won't survive scrutiny.
### Chapter by Chapter: Where Applicants Stumbled
The MFSA went through DORA chapter by chapter, and the results were mixed. Here's the breakdown:
- **Chapter IV:** Largely satisfactory. This was the bright spot.
- **Chapter III:** Missing measures and procedures for consistent, integrated monitoring, handling, and recording of ICT-related incidents and significant cyber threats.
- **Chapter V:** Applicants struggled to integrate DORA's general principles.
- **Chapter II:** The biggest trouble zone—response and recovery, building a comprehensive risk management framework, identification, protection, prevention, and governance.
Under the technical standards, the weak spots kept piling up: asset and patch management, vulnerability tracking, third-party due diligence, and exit planning. Some applicants relied on a single generic exit plan for all providers. That's a red flag supervisors notice immediately.
### A Word on AX50 and the New Annexes
The MFSA also urged applicants to assess carefully whether AX50 applies—there's a possible exemption where the ICT provider is itself a regulated financial entity. Don't assume; check.
Streamlined annexes published in December 2025 now function as a self-assessment tool. If you're applying in 2026, the regulator expects you to use them fully. Not partially. Fully.
### The Bigger Picture
Here's the takeaway that matters most: the majority of shortcomings stem from documentation gaps and applicants simply not understanding how DORA functions in practice. That's fixable—but only if you start earlier and tailor your implementation to your actual business.
> The MFSA expects earlier alignment and more tailored implementation, which should make authorisation more efficient.
In other words, the regulator isn't trying to trip you up. It wants applications that reflect real operational resilience, not templated paperwork. Get aligned early, review your AI-generated drafts with human eyes, and build exit plans that actually fit each provider. Do that, and the authorisation process gets a whole lot smoother.