- SOC 2 Readiness
- 24/7 incident line
- 24/7 security operations team
Financial Controls Compliance
SOX & CSOX ComplianceSarbanes-Oxley & NI 52-109 Financial Controls
Strengthen internal controls over financial reporting and support CEO/CFO certification with comprehensive SOX and Canadian NI 52-109 compliance services.

Key SOX/CSOX Requirements
Internal Controls over Financial Reporting (ICFR)
CEO/CFO Certification (NI 52-109)
Disclosure Controls & Procedures
Documentation & Testing
SOX and CSOX side by side
| Topic | US SOX (sections 302 and 404) | Canada (NI 52-109) |
|---|---|---|
| Who | Companies filing with the US SEC, including Canadian cross-listed issuers | Reporting issuers in Canada; venture issuers file simpler certificates |
| Officer certification | CEO and CFO certify each quarterly and annual report | CEO and CFO file annual and interim certificates |
| Management assessment | Annual assessment of internal control over financial reporting (404(a)) | Non-venture issuers certify design, and annually evaluate effectiveness, of disclosure controls and ICFR, with conclusions in the MD&A |
| Auditor opinion on ICFR | Required for accelerated and large accelerated filers (404(b)) | Not required |
| Control framework | Usually COSO 2013 | A suitable framework, usually COSO 2013 |
The four IT general control domains
Typical controls
- Approved access requests before access is granted
- Timely removal of access for leavers
- Periodic user access reviews, including privileged and service accounts
- Password, MFA and session settings
- Segregation of duties in the ERP and between development and production
What auditors test
- Samples of new users, with approval dated before access
- All leavers matched to account disable dates
- Completeness of the user list used in each review
- System settings exported from the application, not described
Typical controls
- Change requests, testing and approval before deployment
- Separation between who builds and who deploys
- Emergency change procedure with after-the-fact review
- Control over configuration changes and direct data changes
What auditors test
- A complete population of changes taken from the system
- Samples traced from request through test and approval to deployment
- Who had the ability to deploy to production during the year
Typical controls
- Job scheduling and monitoring of batch jobs and interfaces
- Handling of failed jobs and incidents
- Backups and periodic restore tests
What auditors test
- Who can change job schedules
- Samples of failed jobs and how they were resolved
- Backup logs and restore test evidence
Typical controls
- Project governance for new financial systems
- Testing and user acceptance before go-live
- Data conversion and migration checks
- Go-live approval
What auditors test
- Migration reconciliations (record counts, totals)
- Signed user acceptance and go-live approvals
- That ITGCs were in place from day one on the new system
The evidence auditors test, and how much
| How often the control runs | Typical sample |
|---|---|
| Annually | 1 |
| Quarterly | 2 |
| Monthly | 2 to 5 |
| Weekly | 5 to 15 |
| Daily | 20 to 40 |
| Many times a day | 25 to 60 |
Typical ranges only. Your auditor sets sample sizes based on risk and their methodology.
Information produced by the entity (IPE)
Any report used in a control, such as a user listing, a change log or an aging report, must be shown to be complete and accurate. Expect to show how the report was generated, its parameters and a check against the source.
Service organizations
For cloud or outsourced financial systems, auditors rely on SOC 1 Type 2 reports. You need to read them, cover any gap in their period, assess exceptions and operate the complementary user entity controls they assume you have.
How deficiencies are rated
A deficiency is a control that does not prevent or detect misstatements on time. A significant deficiency is serious enough to merit the attention of those overseeing financial reporting. A material weakness means a reasonable possibility that a material misstatement would not be prevented or detected, and must be disclosed.
Our SOX/CSOX Compliance Process
- 1Weeks 1-3
Control Environment Assessment
Evaluate your current internal control environment, identify significant accounts and processes, and assess control design against SOX/NI 52-109 requirements. - 2Weeks 4-8
Control Design & Documentation
Design or remediate internal controls, create process narratives, risk-control matrices, and control documentation aligned with COSO and COBIT frameworks. - 3Weeks 9-14
Testing & Remediation
Execute control testing programs including walkthroughs, sample-based testing, and IT general controls testing. Remediate identified deficiencies before certification. - 4Ongoing
Certification Support & Monitoring
Support CEO/CFO certification process, establish ongoing monitoring programs, coordinate with external auditors, and maintain control effectiveness year-round.
Where cyber security meets financial reporting
Incident disclosure
Privileged access is the overlap
Logs as evidence
IT general controls readiness quick check
How ready are you for SOX and CSOX IT general controls?
Ten questions on the IT general controls auditors test for financially significant systems. Answer for your ERP and other in-scope applications.
Where GuardsArm fits
We help design and pre-test IT general controls, fix the access and change gaps that produce deficiencies, and supply monitoring evidence from our around-the-clock detection and response, with data kept in Canada. Management concludes on internal control and your external auditor forms its own opinion; GuardsArm is not your auditor.
Benefits of SOX/CSOX Compliance
Regulatory Compliance
Investor Confidence
Fraud Prevention
Operational Efficiency
Industries We Serve
- Public companies listed on TSX/TSX-V
- US-listed Canadian companies (SEC registrants)
- Dual-listed companies (cross-border)
- Financial services and banking institutions
- Insurance companies
- Mining and natural resources companies
- Technology and SaaS organizations
- Manufacturing and industrial companies
Why Choose GuardsArm for SOX/CSOX?
- 1
Financial Controls Expertise
Deep experience with COSO, COBIT, and both US SOX and Canadian NI 52-109 requirements
- 2
Cross-Border Compliance
Seamless support for dual-listed and cross-border companies meeting both SOX and CSOX obligations
- 3
Year-Round Support
Ongoing monitoring, testing, and certification support throughout the annual compliance cycle
Evidence, not assumptions
SOX & CSOX Compliance: evidence and assessment handoff
Readiness is preparation, not an outcome determination. The exact evidence and external review process depend on the applicable requirements and agreed scope.
Readiness support
Define the boundary, review control design, coordinate remediation and organize an evidence index. Control owners remain responsible for operating controls and supplying accurate records.
Independent audit or certification
Where applicable to SOX & CSOX Compliance, an independent auditor, assessor, certification body or authority sets its own procedures, evaluates the evidence and reaches its own conclusion. Readiness support does not replace that work or guarantee its outcome.
Evidence examples
Control design and governance
- Approved policies, standards and procedures with version and ownership history.
- A scope and control matrix showing requirement coverage and control owners.
- Risk decisions, exceptions, remediation approvals and leadership review records.
Operating and technical records
- Dated access reviews, change tickets, training completion and vulnerability follow-up.
- Source exports for identity, MFA, logging, backup and other in-scope configurations.
- Records that show both the review period and any gaps, failures or corrective actions.
Data, third parties and testing
- Relevant data inventories or flow maps, vendor records and contractual control evidence.
- Test plans and results, exercise records, incident timelines and tracked follow-up actions.
- An evidence index linking each source item to its owner, control and assessment request.
Roles and handoff
Your control owners
Operate controls, provide authentic source evidence, explain variations and complete remediation.
GuardsArm readiness team
Map requests, review completeness and consistency, track gaps and prepare the handoff package.
Independent reviewer, where applicable
Defines its requests and procedures, evaluates evidence independently and issues conclusions within its remit.
- 1
Request
Tie each evidence request to the agreed scope, criterion, owner and review period.
- 2
Collect
Preserve source context and record dates, coverage and known limitations.
- 3
Review
Mark items ready, open or not applicable, with rationale and follow-up ownership.
- 4
Hand off
Provide the index, source access and outstanding-item log to the intended reviewer.
SOX & CSOX Compliance FAQs
Common questions about SOX, CSOX, and NI 52-109 financial controls compliance
What is CSOX (Canadian SOX)?
CSOX refers to the Canadian equivalent of the US Sarbanes-Oxley Act, primarily implemented through National Instrument 52-109 (Certification of Disclosure in Issuers' Annual and Interim Filings). NI 52-109 requires CEOs and CFOs of reporting issuers to certify the design and effectiveness of disclosure controls and procedures (DC&P) and internal controls over financial reporting (ICFR).
How does NI 52-109 differ from US SOX?
While NI 52-109 shares the same objectives as SOX Section 302/404, there are key differences. NI 52-109 does not require a separate auditor attestation report on ICFR effectiveness for most issuers (unlike SOX 404(b)). It uses a "basic" and "full" certificate approach based on issuer size, and allows for a scope limitation disclosure rather than requiring complete remediation of all control weaknesses before certification.
Who needs SOX/CSOX compliance?
All reporting issuers in Canada are subject to NI 52-109, including companies listed on the TSX and TSX Venture Exchange. Canadian companies listed on US exchanges must also comply with US SOX requirements. Venture issuers may use simplified "basic" certificates, while non-venture issuers must use "full" certificates with more detailed ICFR evaluations.
What frameworks are used for SOX/CSOX internal controls?
The COSO (Committee of Sponsoring Organizations) Internal Control-Integrated Framework is the most widely used framework for evaluating ICFR. For IT general controls, organizations typically use COBIT (Control Objectives for Information and Related Technologies). These frameworks provide structured approaches to identifying, designing, and assessing internal controls over financial reporting.
How long does SOX/CSOX compliance take?
Initial SOX/CSOX compliance implementation typically takes 14-20 weeks, including control environment assessment (2-3 weeks), control design and documentation (4-6 weeks), testing and remediation (5-7 weeks), and certification support (3-4 weeks). Ongoing annual compliance cycles require 8-12 weeks of concentrated effort for testing, remediation, and certification preparation.
Still Have Questions?
Our cybersecurity experts are here to help. Get personalized answers and a free security consultation.