The Digital Operational Resilience Act (DORA)<\/a> is a new set of rules passed by the European Union that came into effect on January 16, 2023, with full application beginning on January 17, 2025, to strengthen the financial sector’s digital defenses, requiring banks, insurance firms, investment companies, and similar institutions to improve their digital security. This includes having good plans, training employees, testing systems regularly, and being transparent when problems arise. DORA aims to prevent widespread disruptions caused by cyberattacks, system failures, and other tech-related problems.<\/span><\/p>\n The core themes of DORA are risk management, incident response and reporting, digital operational resilience testing, third-party risk management, and information sharing. These elements build a comprehensive strategy for assessing risks, handling incidents, testing defenses, ensuring vendor security, and collaborating through information sharing.<\/span><\/p>\n With recent increased frequency and sophistication of cyberattacks, DORA aims to prevent severe consequences from cyber crime by setting strict risk management<\/a> standards across the board for financial institutions like banks, insurance firms, investment companies, and even crypto-asset service providers. This applies not only to the institutions themselves, but also to the tech companies they rely on for services like cloud and data management.\u00a0<\/span><\/p>\n Penalties for noncompliance with DORA can be severe, including:<\/p>\n 1. Financial Penalties<\/b><\/p>\n Entities that fail to comply with DORA may face substantial fines. The amount can vary, but is typically proportionate to the gravity of the breach and the financial strength of the entity. Fines can be revenue-based, daily, cumulative, or a combination of various fine types depending on the violation. In some instances, fines may be reduced if the entity can demonstrate that it has taken steps to mitigate the impact of the breach or has cooperated fully with regulatory authorities during the investigation.<\/p>\n 2. Operational Restrictions<\/b><\/p>\n In cases of severe noncompliance, regulatory authorities may impose restrictions on the entity\u2019s operations. This could include limiting the scope of activities the entity is allowed to perform or suspending certain operations until compliance is achieved.<\/p>\n 3. Increased Supervision<\/b><\/p>\n Entities that fail to meet DORA\u2019s requirements may be subject to increased supervision by regulatory authorities. This could involve more frequent audits, mandatory reporting requirements, or other oversight measures designed to ensure future compliance.<\/p>\n 4. Reputational Damage<\/b><\/p>\n Noncompliance with DORA can lead to reputational damage, especially if breaches are made public. Regulatory authorities may disclose noncompliance to the public, damaging the entity\u2019s reputation and trustworthiness in the market.<\/p>\n 5. Legal Consequences<\/b><\/p>\n In some cases, noncompliance could lead to legal actions by affected parties, including customers, partners, or other stakeholders who may have suffered losses due to the entity\u2019s failure to meet DORA\u2019s standards.<\/p>\n 6. Regulatory Actions<\/b><\/p>\n Authorities have the power to impose various regulatory sanctions, including issuing warnings, mandating corrective actions, or even revoking licenses in extreme cases.<\/p>\n DORA places a significant responsibility on management to stay informed about Information Communication and Technology (ICT) risks and create robust risk management frameworks. This means top executives and board members can be held accountable if their firm doesn’t meet DORA’s requirements. Firms must be proactive, documenting their systems and regularly assessing their risk profiles.<\/span><\/p>\n Under DORA, businesses must analyze their entire technology landscape. This involves identifying critical functions and assets, understanding their interconnections, and documenting their dependencies on each other and external providers. It’s like drawing up a battle plan for the digital world, identifying weaknesses and strengths.<\/span><\/p>\n Consider a bank relying on a cloud provider to store sensitive customer data. DORA requires the bank to assess the cloud service’s security and document potential risks, holding both the bank and the cloud provider responsible for maintaining high-security standards.<\/span><\/p>\n DORA mandates business impact analysis to play out “what if” scenarios, including service disruptions, cyberattacks, or natural disasters. Through these simulations, institutions determine their risk appetite, strengthen their digital infrastructure, and create robust business continuity plans.<\/span><\/p>\n If a major incident occurs, firms must be transparent with regulators and affected parties. They must file detailed reports outlining what happened, how they are addressing it, and how they’ll prevent it from happening again. There’s a clear structure for reporting serious incidents: an initial notification, updates on the resolution process, and a final, detailed analysis identifying root causes.<\/span><\/p>\n Incident reporting could become complex across different countries and authorities. However, the European Supervisory Authorities (ESAs) are streamlining the process. They aim to establish common templates and explore a centralized EU reporting hub. This simplification will speed up response times and coordination across the financial landscape.<\/span><\/p>\n DORA requires financial institutions to prove their defenses are strong through regular testing of their systems. This helps identify vulnerabilities and ensure protection measures are effective. These tests include vulnerability assessments, incident scenario simulations, and threat-led penetration testing (TLPT), essentially simulated cyberattacks.<\/span><\/p>\n The test results are reviewed by authorities, meaning firms must address weaknesses. This demonstrates a commitment to continuous improvement in their resilience.<\/span><\/p>\n Testing is an ongoing process. Each year, institutions must conduct basic tests to identify vulnerabilities early on. However, institutions critical to the financial system undergo a full TLPT simulation every three years. This testing also involves their key tech providers, ensuring everyone is on the same page regarding security. This strengthens the overall security posture.<\/span><\/p>\n DORA emphasizes third-party risk management, explicitly addressing the tech providers serving financial institutions. This is because a secure system is only as strong as its weakest external link. Financial institutions must proactively mitigate the risks posed by these third-party service providers.<\/span><\/p>\n Financial institutions must ensure that any provider handling critical or important functions meet DORA’s strict security and operational requirements. This is because the institutions remain responsible even if the problem originates with an outside vendor.<\/span><\/p>\n For instance, if a financial institution contracts a company for data processing, they can’t assume the processor’s security is adequate. DORA mandates strict contract agreements covering exit strategies, regular audits, security requirements, and performance benchmarks. These measures shift the responsibility for strong security from a “hope for the best” approach to a legally binding and supervised reality.<\/span><\/p>\n In 2019, the EBA established the<\/span> Guidelines on ICT and security risk management<\/span><\/a> and<\/span> Guidelines on outsourcing arrangements<\/span><\/a>. Building on these, the MFSA released its Guidance on Technology Arrangements, ICT and Security Risk Management, and Outsourcing Arrangements in December 2020.<\/span><\/p>\n DORA empowers regulators to take action if necessary. They can force firms to terminate agreements with non-compliant tech companies, reinforcing that cybersecurity is not optional but the law.<\/span><\/p>\n Research shows that financial companies could spend up to 3% of their payroll on regulatory compliance. While this seems significant, compare it to the cost of major security breaches and reputational damage. The upfront investment in compliance is more appealing.<\/span><\/p>\n While not mandatory, DORA encourages financial services firms to collaborate and share threat intelligence. This means firms are encouraged to share information about cyber threats they’ve faced and the mitigation strategies they\u2019ve used. This fosters a collective defense effort, making everyone smarter and more effective.<\/span><\/p>\n However, sharing sensitive information requires clear ground rules. Any intelligence sharing must comply with existing regulations for personal data protection. This ensures sensitive data remains protected even in collaborative environments.<\/span><\/p>\n Employees are often an organization’s most significant vulnerability regarding cyber threats. DORA emphasizes ongoing training and awareness programs for all staff members. These programs educate employees about cybersecurity threats, security procedures, and how to react during an technology incident.<\/span><\/p>\n Many resources are available for staff training in data protection, cyber security, and compliance frameworks like GDPR, ISO 27001, PCI DSS, and CCPA. Training methods include classroom sessions, in-house training, live online courses,<\/span> self-paced online training<\/span><\/a>, and<\/span> e-learning programs<\/span><\/a>.<\/span><\/p>\n Craft\u2019s<\/span> supplier risk management solutions<\/span><\/a> are designed to streamline compliance and enhance reporting. With our platform:<\/span><\/p>\nHow will DORA affect businesses?<\/h2>\n
What are DORA’s key requirements?<\/h2>\n
ICT Risk Management and Governance<\/h3>\n
Incident Response and Reporting<\/h3>\n
Digital Operational Resilience Testing<\/h3>\n
Third-Party Risk Management<\/h3>\n
Information Sharing<\/h3>\n
Training and Staff Awareness<\/h3>\n
How Craft Can Help<\/h2>\n
\n