DORA Foundation — Lesson 1: DORA Scope, Objectives, Governance, Proportionality, Roles, and Regulatory Context

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping dora scope, objectives, governance, proportionality, roles, and regulatory context.
• Apply a practical workflow and create a reviewable DORA scope and responsibility map.
• Evaluate the exception where critical services are mapped without underlying ICT dependencies and determine proportionate follow-up.

Detailed Topics

• DORA Scope applied to the course scenario and expected evidence.
• Objectives applied to the course scenario and expected evidence.
• Governance applied to the course scenario and expected evidence.
• Proportionality applied to the course scenario and expected evidence.
• Roles applied to the course scenario and expected evidence.
• and Regulatory Context applied to the course scenario and expected evidence.

Instructor Demonstration

The instructor traces a case involving a financial entity mapping regulatory resilience responsibilities across business, technology, security, continuity, and suppliers. The demonstration links decisions to objective evidence, records the result in DORA scope and responsibility map, and tests the condition where critical services are mapped without underlying ICT dependencies.

Hands-On Exercise

Complete a controlled exercise covering DORA Scope, Objectives, Governance, Proportionality, Roles, and Regulatory Context. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in DORA scope and responsibility map.

1. Define the objective, boundaries, stakeholders, criteria, and expected work product.
2. Perform the activity while recording assumptions, observations, evidence, and decisions.
3. Test normal operation, the exception, and an escalation or follow-up condition.
4. Document conclusions, owners, deadlines, verification methods, and review triggers.

Scenario Analysis

• Identify the requirement or control with the strongest influence on the scenario outcome.
• Compare two defensible responses and explain their risk, operational, and evidence trade-offs.
• Decide how the DORA scope and responsibility map should be approved, retained, reviewed, and updated.

Troubleshooting Guidance

Start where expected practice and observed evidence first diverge. Separate a missing record from an ineffective process, distinguish unclear ownership from a control failure, and treat “critical services are mapped without underlying ICT dependencies” as a hypothesis until tested against the applicable criteria and intended outcome.

Validation Checklist

• Scope, roles, criteria, stakeholders, dependencies, and intended outcomes are explicit.
• The DORA scope and responsibility map connects conclusions to objective, reviewable support.
• Normal operation, the stated exception, escalation, and follow-up were evaluated.
• Owners, due dates, verification methods, review triggers, and improvement actions are clear.

Lesson Outcome

Learners can apply DORA Scope, Objectives, Governance, Proportionality, Roles, and Regulatory Context, explain the reasoning used, and defend the result through DORA scope and responsibility map.