FTC Safeguards Rule
Build the written information security program required for covered financial institutions under FTC jurisdiction.
Sarbanes–Oxley Act Section 404 · Internal control over financial reporting
Build management’s internal-control assessment and support an integrated external audit where required.
SEC reporting issuers subject to Section 404. External auditor attestation depends on filer status and applicable exemptions.
Management’s ICFR report and, where required, external auditor’s opinion on ICFR.
Confirm filer status and management assessment versus auditor attestation duties. Consider service organization controls and complementary user controls.
Report key controls without design or operating evidence, deficiencies by status and potential severity, and remediation that cannot be retested before reporting.
Fill this in with your sponsor and send it to the people who own the work.
SOX Section 404 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 Scope financial reporting risks · Controller + audit committee [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. Bring trial balance, consolidated financial statements, filer status, location information, prior findings and recent acquisitions or systems changes. 2. Choose a material transaction cycle and run one walkthrough. Confirm where evidence lives and who can extract complete populations. 3. Set the testing and reporting calendar around close cycles, remediation lead time, auditor coordination and the Audit Committee schedule.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Scope financial reporting risks | Controller + audit committee | Before annual testing | Set a start date | Scoping memo; Significant account map; Annual calendar | Open |
| Document key controls and ownership | Process owners + IT controls lead | Before walkthroughs | Set a start date | Narratives; Risk-control matrices; Evidence requirements | Open |
| Execute testing and evaluate deficiencies | Management testing team + external auditor where required | Throughout fiscal year and at year-end | Set a start date | Test workpapers; Deficiency evaluation; Remediation evidence | Open |
| Complete reporting and governance review | Management + audit committee + independent auditor if applicable | At annual filing milestones | Set a start date | Management report; Auditor opinion if required; Audit committee materials | 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 significant accounts, assertions, locations, processes, vendors and IT dependencies. Align criteria, scope and plan with leadership.
Trial balance, material accounts and disclosures, legal entity map, prior deficiencies and financial systems.
The account map connects revenue cut-off to order capture, invoicing, journals, report dependencies and the relevant locations.
Escalate a new acquisition, major system change or unresolved scope exclusion before testing plans are finalized.
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.
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.
Fictional details. Use the same fields with evidence from your work.
Every external deadline links to a real source. Planning targets are visibly marked.
Add approved dates to the team calendar and share them with the people scheduled to deliver or review.
Trace end-to-end flows and risks. Identify key control activities, IT general controls, relevant reports and complementary user controls.
Process narratives, scoped assertions, system reports and evidence of a recent transaction.
A revenue cut-off review records the reporting parameters, shipments near period end, reviewer’s criteria, exceptions and disposition.
Raise missing segregation of duties, review thresholds or report validation when they affect the control design.
Fictional details. Use the same fields with evidence from your work.
The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.
Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.
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.
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.
Evaluate design and operating effectiveness. Document populations and samples, classify deficiencies and assess remediation and retesting.
Approved test plan, dated population extracts, evidence, earlier test results and remediation status.
A reviewer can trace a result from the workpaper to the sampled transaction, supporting evidence and documented conclusion, with reviewer and date.
Promptly raise possible significant deficiencies or material weaknesses through the agreed governance route, including recurring or interacting deficiencies.
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.
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.
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.
Coordinate year-end roll-forward and evidence. Finalize management’s assessment and reporting, auditor attestation where required and governance communications.
Testing conclusions, deficiency evaluations, compensating control results, remediation retests and financial reporting timetable.
The reporting pack includes final management and governance approvals and traceable conclusions for issues that could affect internal control reporting.
Raise disagreements about severity, scope or disclosure with the Controller and Legal before reporting and arrange timely communication with the Audit Committee.
Fictional details. Use the same fields with evidence from your work.
The signer can explain the basis for each statement and the record reflects the required scope and period.
Give the executed document to the relevant recipient under the engagement or regulation. Use the worksheet to organize review.
Fictional details. Use the same fields with evidence from your work.
The original can be traced to the issuer and its scope and date match the engagement or application.
Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.
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.