FTC Safeguards Rule
Build the written information security program required for covered financial institutions under FTC jurisdiction.
Digital Operational Resilience Act · Regulation (EU) 2022/2554
Organize ICT risk, incident reporting, resilience testing and third-party oversight for EU financial entities.
Financial entities listed in Article 2, subject to exclusions and proportionality. Separate provisions govern oversight of designated critical ICT third-party providers.
Evidence of digital operational resilience governance, testing and ICT provider management.
Use applicable technical standards and competent authority instructions for incident templates, timing, registers and threat-led penetration testing.
Track critical functions without tested recovery, invalid register rows, open contract or exit gaps, and incident-report deadlines as separate items.
Fill this in with your sponsor and send it to the people who own the work.
DORA kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Confirm entity scope and accountability · Management body + legal [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Pick a critical client or business service and map the people, systems, contracts, suppliers and recovery dependencies required to deliver it. 2. Reconcile the ICT register to Procurement and Finance records. Identify contracts, provider identifiers and functions with missing data. 3. Walk an outage scenario with Operations, Security and Compliance. Ask the reporting owner to demonstrate how they classify it and find the correct template and regulator.
A financial firm models loss of a managed database service. Its third-party risk team confirms which functions depend on it, tests data export and includes subcontractors in the relevant register fields.
Review cloud switching obligations that may also affect the arrangement.
Compare operational resilience work for an Australian regulated entity if relevant.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Confirm entity scope and accountability | Management body + legal | At initiation | Set a start date | Scope memo; Accountability map; Critical-function inventory | Open |
| Operate ICT risk and incident controls | CISO + resilience lead | Ongoing and on incidents | Set a start date | ICT risk framework; Incident procedure; Recovery evidence | Open |
| Build the ICT third-party register | Vendor risk + contracts | Before contracting and ongoing | Set a start date | Register of information; Contract gap analysis; Exit plans | Open |
| Test operational resilience | Resilience lead + independent testers | On applicable test schedule | Set a start date | Testing program; Test reports; Remediation evidence | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify regulated entities, critical functions and proportionality. Assign responsibility for ICT risk, incident and third-party governance.
Regulatory permissions, group chart, service inventory, business impact records and competent authority instructions.
The scope matrix links a regulated entity and critical function to its accountable executive, service map and competent authority.
Escalate an uncertain entity classification or a critical function whose provider and recovery dependencies nobody owns.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
Each item has one accountable owner. The source and as-of date let a reviewer trace it back.
Share the reviewed inventory with the people building the control, privacy or testing scope.
Map assets, dependencies and recovery objectives. Classify ICT incidents, test escalation and prepare current reporting templates and clocks.
ICT inventory, service dependencies, approved tolerances, applicable classification criteria and regulatory portal contacts.
An exercise ticket includes the original alert, timestamps, classification reasoning, regulator destination and the actual restore results.
Raise an unstaffed filing route, an incident approaching a deadline or a recovery result outside the approved tolerance.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Maintain register entries at the applicable organizational levels, review contract clauses, concentration and subcontracting, and plan tested exits.
Contracts, service inventories, provider identifiers, subcontracting records and the reporting templates for the regulated entity.
One linked set of register rows connects a critical function to its ICT service, signed contract, provider and relevant subcontracting records.
Escalate missing information, contract terms that block oversight or an exit plan with unresolved data access or migration barriers.
Fictional details. Use the same fields with evidence from your work.
Each provider and contract record links to an actual function and all required identifiers are present.
Use the verified register in supplier reviews and put required submissions in the authority’s prescribed format.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Run risk-based testing and track remediation. Confirm whether authorities require threat-led penetration testing and on what scope.
Critical function map, risk analysis, incident history, recovery objectives and applicable testing obligations.
The test report shows what was exercised, measured results, limitations, fixes and evidence from a retest.
Raise recurring failed tolerance tests or an upcoming required exercise without resources or provider participation.
Fictional details. Use the same fields with evidence from your work.
A person who receives the plan can tell when to act, what to check and where to save the result.
Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.