DORA Foundation — Lesson 3: Incident Classification, Reporting, Testing, Threat-Led Exercises, and Evidence

Learning Objectives

• Interpret the requirements, principles, roles, and dependencies shaping incident classification, reporting, testing, threat-led exercises, and evidence.
• Apply a practical workflow and create a reviewable incident and testing evidence checklist.
• Evaluate the exception where resilience tests exclude outsourced platforms and determine proportionate follow-up.

Detailed Topics

• Incident Classification applied to the course scenario and expected evidence.
• Reporting applied to the course scenario and expected evidence.
• Testing applied to the course scenario and expected evidence.
• Threat-Led Exercises applied to the course scenario and expected evidence.
• and Evidence 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 incident and testing evidence checklist, and tests the condition where resilience tests exclude outsourced platforms.

Hands-On Exercise

Complete a controlled exercise covering Incident Classification, Reporting, Testing, Threat-Led Exercises, and Evidence. Confirm scope and responsibilities, examine the stated exception, reach a supported conclusion, and preserve the outcome in incident and testing evidence checklist.

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 incident and testing evidence checklist 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 “resilience tests exclude outsourced platforms” 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 incident and testing evidence checklist 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 Incident Classification, Reporting, Testing, Threat-Led Exercises, and Evidence, explain the reasoning used, and defend the result through incident and testing evidence checklist.