EVIDENCE PLANNER
Reuse evidence across programs
Choose the programs on your desk. See where a single evidence packet can help and check the scope, dates and proof each reviewer still needs.
5Evidence packets
0Shared across programs
0Marked prepared on this device
| Evidence packet | DORA |
|---|---|
| Candidate | |
| Candidate | |
| Candidate | |
| Candidate | |
| Candidate |
EVIDENCE PACKET
Backup restoration test
Who prepares it Infrastructure and the business service owner
- Approved recovery targets, test conditions and systems exercised
- Dated logs, restored data validation and actual recovery time
- Failed measures, corrective actions and results of the next test
What it can look like
The billing database restored in 37 minutes, inside the 60-minute target. The payment queue was outside the test and remains an open action.
What each program still needs
DORA
ICT recovery and restoration evidence
Tie the restore to the affected business function and its recovery objectives. Retain any additional testing required for that regulated entity.
View the preparation plan
Evidence preparation plan DORA Backup restoration test [to prepare] Suggested owner Infrastructure and the business service owner - Approved recovery targets, test conditions and systems exercised - Dated logs, restored data validation and actual recovery time - Failed measures, corrective actions and results of the next test DORA · ICT recovery and restoration evidence Tie the restore to the affected business function and its recovery objectives. Retain any additional testing required for that regulated entity. Critical supplier review [to prepare] Suggested owner Procurement, service owner and Security - Service contract, relevant data and systems, and a responsibility matrix - Dated assurance evidence and the boundaries it covers - Open gaps, renewal or exit decision, and accountable owner DORA · ICT third-party risk evidence Link arrangements to the register of information and functions supported. Check applicable contract and exit duties for critical or important functions. Production change approvals [to prepare] Suggested owner Engineering and release management - Complete production deployment list and documented query - Linked request, independent review or approval and release event - Tests, emergency exceptions and reviews after deployment DORA · ICT change management evidence Show documented assessment, approval, testing and implementation on relevant ICT systems. Include effects on critical or important functions. Incident exercise and case file [to prepare] Suggested owner Security operations, Legal and the service owner - Case timeline with detection, awareness and classification recorded separately - Impact, evidence, documented reporting decision and any submission receipts - Exercise observations, corrective actions and retest owner DORA · ICT incident handling and reporting evidence Capture awareness and classification times and test the competent authority channels and required reporting steps. Vulnerability scan and retest [to prepare] Suggested owner Security engineering and asset owners - Scoped inventory, scan parameters and coverage reconciliation - Original findings with asset, severity, owner and dates - Remediation or documented decision, followed by dated verification DORA · ICT vulnerability management evidence Use the results in the regulated entity’s risk and testing program. Track critical functions and obligations for any additional tests.