Skip to content

ICT risk and resilience operations

DORA execution in Modulos covers the full ICT resilience cycle: plan, protect, detect, respond, recover, learn, classify, and report.

Organization-level resilience governance (OFF-16)

RequirementTopicRegulation reference
ORF-367ICT systems capacity, availability, and resilience governanceArt. 7
ORF-368ICT asset, function, data, and dependency inventory governanceArt. 8(1), 8(4)-(7)
ORF-369Continuous ICT risk identification, assessment, and vulnerability governanceArt. 8(2), 8(3)
ORF-370ICT protection and prevention governanceArt. 9
ORF-371ICT detection and alert governanceArt. 10
ORF-372ICT response, recovery, and crisis-management governanceArt. 11(1)-(9)
ORF-373Backup, restoration, recovery objectives, and continuity methods governanceArt. 12
ORF-374Post-incident review, learning, and resilience-improvement governanceArt. 13
ORF-375Crisis communication, client disclosure, and public communication governanceArt. 14, 19(3)

Organization-level incident and reporting duties (OFF-16)

RequirementTopicRegulation reference
ORF-376ICT-related incident management process governanceArt. 17
ORF-377Major incident classification and materiality assessment governanceArt. 18
ORF-378Major ICT-related incident reporting governanceArt. 19, 20
ORF-379Significant cyber threat voluntary notification governanceArt. 19(2), 20
ORF-380Aggregated annual major-incident costs and losses estimation and reporting governanceArt. 11(10)-(11)
ORF-381Operational or security payment-related incident reporting governanceArt. 19, 20, 23

App-side execution requirements (MFF-16)

RequirementTopicRegulation reference
MRF-294ICT capacity, availability, and resilience executionArt. 7
MRF-295ICT asset, function, data, and dependency mapping executionArt. 8(1), 8(4)-(7)
MRF-296Continuous ICT risk and vulnerability assessment executionArt. 8(2), 8(3)
MRF-297ICT protection and prevention control executionArt. 9
MRF-298ICT detection and alert-threshold executionArt. 10
MRF-299ICT response, recovery, and crisis-operations executionArt. 11
MRF-300ICT backup, restoration, and recovery executionArt. 12
MRF-301Post-incident learning and resilience-improvement executionArt. 13
MRF-302ICT-related incident logging and evidence-handling executionArt. 17
MRF-303Major incident classification and materiality assessment executionArt. 18
MRF-304Major ICT-related incident reporting preparation executionArt. 19, 20

Incident model in practice

The current DORA incident family is deliberately more explicit than the old framework attempt:

  • ORF-376 governs the incident-management process itself
  • ORF-377 governs major-incident classification and materiality
  • ORF-378 governs staged DORA reporting
  • ORF-379 keeps voluntary significant-cyber-threat notification separate
  • ORF-380 preserves the standing capability to estimate annual major-incident costs and losses for entities that are not operating under the Article 16 simplified-framework carve-out for that duty
  • ORF-381 isolates the Article 23 payment-related reporting cohort

On the app side, MRF-302 to MRF-304 provide the operational evidence path: logging, classification inputs, and reporting-preparation evidence.

Execution checkpoints

  • critical service and dependency inventories are current and reviewable
  • anomaly thresholds and escalation paths are documented and tested
  • continuity and restoration evidence includes test frequency and outcomes
  • major-incident classification and staged-reporting logic is reproducible
  • cohort-specific duties such as payment-related reporting are justified through the requirement applicability record

Disclaimer

This page is for general informational purposes and does not constitute legal advice.