DORA
DORA Chapter II: ICT Risk Management

DORA DORA-Art.10: Detection

What does DORA-Art.10 require?

Financial entities have mechanisms, aligned with the Article 17 incident process, that promptly detect anomalous activity, network performance problems and ICT-related incidents and flag possible material single points of failure; the mechanisms provide multiple control layers, alert thresholds and criteria that start incident response, automatic alerts to response staff, and are tested regularly under Article 25. Sufficient resources monitor user activity, anomalies and cyber-attacks. Data reporting service providers, where the entity is one, additionally check trade reports for completeness, omissions and obvious errors and ask for re-transmission (Art. 10(4)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 47 controls across 15 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 4 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.11 Tune Security Event Alerting Thresholds
  • CIS-13.2 Deploy a Host-Based Intrusion Detection Solution
  • CIS-13.3 Deploy a Network Intrusion Detection Solution

FedRAMP High · 4 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • CA-7 Continuous Monitoring
  • SI-4 System Monitoring
  • SI-5 Security Alerts, Advisories, and Directives

FedRAMP Moderate · 4 controls

  • AU-6 Audit Record Review, Analysis, and Reporting
  • CA-7 Continuous Monitoring
  • SI-4 System Monitoring
  • SI-5 Security Alerts, Advisories, and Directives
  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events

NIST SP 800-53 Rev 5 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

C5 (Germany) · 3 controls

ISO 27001:2022 · 3 controls

  • 5.25 Assessment and decision on information security events
  • 8.15 Logging
  • 8.16 Monitoring activities

ISO 27002:2022 · 3 controls

  • 5.25 Assessment and decision on information security events
  • 8.15 Logging
  • 8.16 Monitoring activities

NIST SP 800-161 Rev 1 · 3 controls

  • CPS230-P40 Required Content of the Business Continuity Plan
  • EBA-GL-3.4.5 Security monitoring

NIS2 Directive · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in DORA Chapter II: ICT Risk Management

You are reading one control. How much of DORA have you already done?

DORA DORA-Art.10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of DORA your existing evidence covers. Hold NIS2 Directive and 17 of 26 DORA controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIS2 Directive pair alone.

Query this from an agent

The graph holds this control, the 47 it maps to, and the evidence behind each claim, over MCP and REST.