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 Blokdyk·Verified 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.
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.