SOX Section 404
Build management’s internal-control assessment and support an integrated external audit where required.
Technology and Cyber Risk Management for federally regulated financial institutions
Translate Canadian supervisory expectations into accountable technology and cyber operations.
Canadian federally regulated financial institutions to which the guideline and related supervisory publications apply.
Technology and cyber risk governance, resilient operations and a tested supervisory reporting process.
Treat B-13, third-party risk expectations and the incident reporting advisory as related work with separately mapped criteria and deliverables.
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Fill this in with your sponsor and send it to the people who own the work.
OSFI Guideline B-13 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 Map technology and cyber governance · Senior management + risk lead [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. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
A bank’s identity provider fails. Technology operations records the affected services and actions, while its reporting lead checks the supervisory criteria and contacts both OSFI recipients if the event qualifies.
Report sooner if possible. Use the advisory’s criteria, recipients and initial form.
Official reference (opens in a new tab)Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map technology and cyber governance | Senior management + risk lead | At program initiation and changes | Set a start date | ICT risk framework; Responsibility matrix; Critical-function inventory | Open |
| Run resilient technology operations | Technology operations + security | Ongoing | Set a start date | Control matrix; Test reports; Recovery evidence | Open |
| Exercise supervisory reporting | Incident lead + compliance | At incident and during drills | Set a start date | Reporting templates; Exercise report; Notification record | Open |
| Review residual issues with management | Risk governance + control owners | Regularly and after material changes | Set a start date | Corrective-action register; Management review minutes | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Set oversight, risk tolerance and ownership. Inventory critical technology, external dependencies and the controls supporting them.
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.
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.
Review architecture, change practices and asset dependencies. Test patching, access, monitoring, backup and recovery against documented objectives.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
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.
Apply the advisory criteria. Pre-stage the reporting form and route to the Technology Risk Division and lead supervisor. Track follow-up as facts develop.
Fictional details. Use the same fields with evidence from your work.
Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.
Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.
Fictional details. Use the same fields with evidence from your work.
An absent participant can see what was tested, what happened and why an action was assigned.
Send approved findings to action owners and file the record for governance or assessment.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.
Compare results to risk tolerance, assign remediation and keep accountable leadership informed of material issues and outcomes.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.