Back to Blog
    Compliance
    European Union

    DORA and IAM: Achieving ICT Risk Compliance for EU Financial Services

    How the EU Digital Operational Resilience Act (DORA) impacts Identity and Access Management. A practical guide for financial institutions to align IAM controls with DORA's ICT risk management requirements.

    April 12, 202512 min readBy iamsoftware.ai

    Introduction: What Is DORA and Why Does IAM Matter?

    The Digital Operational Resilience Act (DORA) — Regulation (EU) 2022/2554 — entered into full application on January 17, 2025. It establishes a comprehensive framework for ICT risk management across the EU financial sector, covering banks, insurance companies, investment firms, crypto-asset service providers, and critically, their ICT third-party service providers.

    DORA's scope is broad, but its implications for Identity and Access Management are particularly significant. The regulation mandates that financial entities maintain robust ICT risk management frameworks that explicitly address access control, identity governance, authentication, and privilege management.

    For IAM and security teams in financial services, DORA is not just another compliance checkbox — it is a regulatory mandate that requires demonstrable, continuously monitored identity security controls.

    DORA's Five Pillars and IAM Implications

    DORA is structured around five pillars. Each has direct or indirect implications for IAM:

    Pillar 1: ICT Risk Management (Articles 5-16)

    This is the core pillar with the most direct IAM requirements. Article 9 specifically addresses "Protection and prevention" and mandates:

    • Access control policies: Financial entities must define, implement, and review policies for granting, managing, and revoking access rights to ICT systems and data.
    • Strong authentication: Implementation of strong authentication mechanisms, including multi-factor authentication where appropriate.
    • Least privilege: Access rights must be granted on a need-to-know, need-to-use basis and reviewed regularly.
    • Segregation of duties: ICT functions must maintain appropriate segregation to prevent conflicts of interest and unauthorized activities.
    • Privileged access management: Enhanced controls for accounts with elevated privileges, including administrative accounts and service accounts.

    Article 9 also requires financial entities to "implement policies that limit physical and logical access to ICT assets and data to what is required for legitimate and approved functions and activities only."

    For NHIs, this is particularly challenging. Service accounts, API keys, and machine identities in financial services environments often have broad access privileges that were granted during initial setup and never right-sized.

    DORA requires financial entities to establish processes for detecting, managing, and reporting ICT-related incidents. IAM is central to incident management:

    • Detection: Identity-based anomaly detection to identify compromised accounts, privilege escalation, and unauthorized access.
    • Classification: Incidents must be classified by severity, with access control breaches potentially meeting "major incident" thresholds.
    • Reporting: Major incidents must be reported to competent authorities within specific timeframes (initial notification within 4 hours of classification, intermediate report within 72 hours, final report within one month).

    IAM systems must provide the telemetry needed to detect identity-based incidents and the forensic data needed to classify and report them accurately.

    Pillar 3: Digital Operational Resilience Testing (Articles 24-27)

    Financial entities must conduct regular testing of their ICT systems, including:

    • Vulnerability assessments: Regular scanning of IAM infrastructure for misconfigurations and vulnerabilities.
    • Penetration testing: Advanced testing including Threat-Led Penetration Testing (TLPT) for significant financial entities, which specifically tests identity and access control defenses.
    • Scenario testing: Testing incident response procedures including identity compromise scenarios.

    Pillar 4: ICT Third-Party Risk Management (Articles 28-44)

    Financial entities must manage risks arising from ICT third-party service providers. This has major IAM implications:

    • Third-party access governance: Controlling and monitoring access granted to third-party vendors, contractors, and service providers.
    • NHI management for third-party integrations: Service accounts, API keys, and tokens used for third-party integrations must be inventoried, monitored, and governed.
    • Concentration risk: Managing dependency on critical third-party providers, including IAM platform providers.
    • Exit strategies: Maintaining the ability to transition away from third-party providers without service disruption.

    Pillar 5: Information Sharing (Article 45)

    DORA encourages financial entities to share threat intelligence. IAM context enriches shared intelligence:

    • Identity-based indicators of compromise
    • Attack patterns targeting identity infrastructure
    • Best practices for identity security in financial services

    Mapping DORA to IAM Controls

    Access Control and Authentication

    DORA RequirementIAM Control
    :---:---
    Strong authentication mechanismsMFA for all users; phishing-resistant MFA (FIDO2) for privileged accounts
    Access on need-to-know basisRBAC/ABAC with regular access reviews
    Regular review of access rightsQuarterly access certification campaigns
    Revocation of access upon role changeAutomated deprovisioning tied to HR events
    Segregation of dutiesSoD policy enforcement with conflict detection

    NHI Controls for DORA

    Non-human identities in financial services present unique DORA compliance challenges:

    • Trading systems: Algorithmic trading platforms use service accounts with broad market data and execution access.
    • Payment processing: Payment gateways use API keys and service accounts that access sensitive financial data.
    • Regulatory reporting: Automated reporting systems use machine identities to access and transmit regulatory data.
    • Third-party integrations: Banking platforms connect to dozens of third-party services via API keys and OAuth tokens.

    Each of these NHI categories must be:

    • Inventoried and classified by risk level
    • Assigned to a human owner
    • Governed with least-privilege policies
    • Continuously monitored for anomalous behavior
    • Included in incident response procedures

    OrchidSecurity provides purpose-built NHI governance that addresses these DORA requirements, offering automated discovery, risk classification, and continuous monitoring of every non-human identity across the financial institution's technology stack.

    DORA Compliance Implementation Roadmap

    Phase 1: Gap Assessment (Months 1-2)

    • Inventory all human and non-human identities across critical ICT systems
    • Map current access control policies against DORA Article 9 requirements
    • Identify gaps in authentication, authorization, and monitoring
    • Assess third-party identity governance maturity

    Phase 2: Foundation (Months 3-6)

    • Deploy MFA for all users with phishing-resistant authentication for privileged accounts
    • Implement privileged access management (PAM) with just-in-time access
    • Deploy NHI discovery and classification across cloud and on-premises infrastructure
    • Establish automated access review processes

    Phase 3: Advanced Controls (Months 7-9)

    • Implement real-time identity threat detection (ITDR)
    • Deploy automated least-privilege enforcement for NHIs
    • Establish third-party identity governance framework
    • Configure compliance reporting aligned to DORA requirements

    Phase 4: Continuous Compliance (Months 10-12+)

    • Automated DORA compliance dashboards and evidence generation
    • Regular resilience testing including identity-focused penetration testing
    • Continuous improvement based on threat landscape and regulatory guidance
    • Integration with EU-wide incident reporting infrastructure

    Regulatory Technical Standards (RTS) and IAM

    The European Supervisory Authorities (ESAs) have published Regulatory Technical Standards that provide detailed implementation guidance. Key RTS relevant to IAM:

    RTS on ICT Risk Management Framework

    Specifies detailed requirements for:

    • Access control policy content and review frequency
    • Authentication mechanism requirements by access type
    • Logging and monitoring requirements for access events
    • Change management procedures for access control configurations

    RTS on ICT Third-Party Risk

    Details requirements for:

    • Due diligence on third-party identity practices
    • Contractual provisions for access control
    • Monitoring and audit rights for third-party access
    • Exit strategy identity management requirements

    RTS on Incident Reporting

    Specifies:

    • Identity-related incident classification criteria
    • Reporting templates that include access control context
    • Root cause analysis requirements for identity-based incidents

    Common DORA IAM Compliance Gaps

    Based on regulatory examinations and industry assessments, the most common IAM gaps in DORA compliance include:

    1. **Incomplete NHI inventory**: Financial institutions typically know about 30-40% of their non-human identities. DORA requires comprehensive visibility.

    2. **Insufficient privileged access controls**: Many institutions lack JIT access, session recording, and real-time monitoring for privileged operations.

    3. **Manual access reviews**: Quarterly access reviews conducted via spreadsheets do not meet DORA's expectations for documented, repeatable processes.

    4. **Weak third-party identity governance**: Limited visibility into access granted to vendors, outsourcers, and cloud service providers.

    5. **No NHI anomaly detection**: While human user behavior analytics may be deployed, NHI monitoring is often absent.

    The Role of IAM Posture Management

    DORA compliance requires not just implementing controls but continuously validating their effectiveness. Cloud IAM Posture Management (CIAPM) platforms like OrchidSecurity are essential because they provide:

    • Continuous compliance monitoring: Automated validation of IAM controls against DORA requirements
    • Evidence generation: Automated compliance reports for regulatory examinations
    • Risk prioritization: Focus remediation efforts on the highest-risk identity gaps
    • Third-party visibility: Unified view of direct and third-party identity risks
    • NHI governance: Comprehensive management of the non-human identities that DORA explicitly requires organizations to control

    Conclusion

    DORA represents a step change in ICT risk regulation for European financial services. Its explicit requirements for access control, authentication, privilege management, and third-party governance make IAM a critical compliance domain.

    Financial institutions that take a proactive, platform-based approach to IAM governance — encompassing both human and non-human identities — will not only achieve DORA compliance but will build a more resilient identity security posture overall.

    The investment in comprehensive IAM posture management is not just a regulatory necessity — it is a competitive advantage that demonstrates operational maturity to regulators, customers, and counterparties.

    Have questions about this topic?

    Ask our AI-powered IAM expert for instant, personalized answers.