Support your SOX IT controls with less manual evidence work
SOX, the Sarbanes-Oxley Act of 2002, is a US federal law that requires public companies to certify the accuracy of their financial reports and to maintain and assess internal control over financial reporting.
- Full name
- Sarbanes-Oxley Act of 2002 (Public Law 107-204)
- Signed into law
- 30 July 2002
- Enforced by
- US Securities and Exchange Commission (SEC), with the PCAOB overseeing auditors
- Applies to
- Companies filing periodic reports with the SEC under the Securities Exchange Act of 1934
Is SOX right for your organisation?
It was passed after the Enron and WorldCom accounting scandals and also created the Public Company Accounting Oversight Board (PCAOB) to oversee auditors. For technology teams, SOX compliance largely means proving IT general controls such as access management, change management and system operations.
SOX applies to companies that file annual and quarterly reports with the US SEC, including foreign companies listed in the US. Private companies preparing for a US IPO usually start building SOX controls well before listing, and SaaS and service providers to public companies are often asked for evidence, such as a SOC 1 report, that supports their customers' SOX audits.
How OneClickComply helps with SOX
SOX is supported in OneClickComply today. We help you run the IT general controls behind Sections 302 and 404 by collecting access, change and configuration evidence automatically from your systems, monitoring for control drift, and reusing evidence you already hold for ISO 27001 or SOC 2. Our in-house audit team can guide you on scoping, but your external auditor performs any Section 404(b) attestation.
Requirements covered
SOX has 11 titles; the core compliance obligations sit in Section 302 (CEO and CFO certification of periodic reports), Section 404 (management assessment of internal control over financial reporting and auditor attestation) and Section 906 (criminal certification).
Manual SOX compliance vs OneClickComply
Doing it manually
- Screenshots of user access reviews collected by hand every quarter
- Change tickets and approvals chased across engineering tools before each audit
- Control gaps found during fieldwork rather than when they happen
- The same access and change evidence rebuilt separately for SOX, SOC 2 and ISO 27001
- Spreadsheets of control owners and test results that go out of date quickly
With OneClickComply
- Access evidence collected automatically from connected identity and SaaS tools
- Change and configuration evidence gathered from your systems and stored in one place
- Continuous monitoring flags control drift as soon as it occurs
- Evidence collected once and mapped to every framework it supports
- A live control register with owners, status and evidence always current
Everything you need for SOX
Automated evidence for SOX IT general controls: access, change and operations
User access review evidence pulled from identity providers and SaaS admin consoles
Continuous monitoring with alerts when a financially relevant control drifts
OneClickFix for supported misconfigurations, with each change logged as evidence
Control mapping so SOC 2 and ISO 27001 evidence also counts towards SOX
Ask an Auditor and vCISO guidance on scoping your SOX IT controls
Three steps to SOX compliance
Connect and scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against SOX and shows which controls pass and which fail.
Fix and generate
OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts SOX policies from your real environment.
Monitor and evidence
Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.
See how far your current setup is from SOX.
Sarbanes-Oxley Act requirements
The Act's 11 titles, followed by the sections most relevant to internal control and IT compliance, with the Section 302 certification points listed individually.
| Reference | Requirement |
|---|---|
| Title I | Public Company Accounting Oversight Board |
| Title II | Auditor Independence |
| Title III | Corporate Responsibility |
| Title IV | Enhanced Financial Disclosures |
| Title V | Analyst Conflicts of Interest |
| Title VI | Commission Resources and Authority |
| Title VII | Studies and Reports |
| Title VIII | Corporate and Criminal Fraud Accountability |
| Title IX | White-Collar Crime Penalty Enhancements |
| Title X | Corporate Tax Returns |
| Title XI | Corporate Fraud and Accountability |
| Section 301 | Public company audit committees |
| Section 302(a)(1) | Signing officer has reviewed the report |
| Section 302(a)(2) | Report contains no untrue or misleading statement of material fact |
| Section 302(a)(3) | Financial statements fairly present financial condition and results |
| Section 302(a)(4) | Officers responsible for designing, maintaining and evaluating internal controls |
| Section 302(a)(5) | Disclosure of significant deficiencies, material weaknesses and fraud to auditors and audit committee |
| Section 302(a)(6) | Disclosure of significant changes in internal controls and corrective actions |
| Section 404(a) | Management assessment of internal control over financial reporting |
| Section 404(b) | Auditor attestation of management's internal control assessment |
Always check the official text of SOX for the exact wording.
SOX questions, answered
Can't find what you need? Our in-house auditors can talk you through SOX on a 30-minute call.
What is SOX?
SOX, the Sarbanes-Oxley Act of 2002, is a US federal law that tightened financial reporting and corporate governance rules for public companies. It requires the CEO and CFO to certify periodic financial reports, requires management to assess internal control over financial reporting each year, strengthened auditor independence and created the PCAOB to oversee auditors of public companies. The SEC enforces it.
Who must comply with SOX?
SOX applies to companies that file annual and quarterly reports with the US Securities and Exchange Commission, including foreign private issuers with US-listed securities. Private companies are generally not required to comply, but those planning a US IPO build SOX controls in advance, and service providers to public companies are often asked to support their customers' SOX audits with evidence or a SOC 1 report.
What is the difference between SOX Section 302 and Section 404?
Section 302 requires the CEO and CFO to certify in each annual and quarterly report that they have reviewed it, that it is not misleading, and that they are responsible for and have evaluated internal controls. Section 404 requires an annual internal control report in which management assesses the effectiveness of internal control over financial reporting, and in 404(b) an external auditor attests to that assessment for larger filers.
What are the penalties for SOX non-compliance?
Under Section 906, an officer who certifies a periodic report knowing it does not comply faces a fine of up to $1 million and up to 10 years in prison. Wilfully certifying such a report raises the maximum to $5 million and 20 years. Other sections add criminal penalties for destroying or altering records, and the SEC can bring civil enforcement actions and bar individuals from serving as officers or directors.
Do all public companies need a SOX 404(b) auditor attestation?
No. Every reporting company must include management's internal control assessment under Section 404(a), but the external auditor attestation in Section 404(b) does not apply to companies that are neither accelerated nor large accelerated filers, following the Dodd-Frank Act in 2010. Emerging growth companies are also exempt from 404(b) under the JOBS Act of 2012.
What are SOX IT general controls?
SOX IT general controls are the technology controls that support reliable financial reporting. SOX does not list them itself; auditors and companies typically group them into access to programs and data, program change management, program development and computer operations. Common evidence includes user access reviews, joiner and leaver records, change approvals, segregation of duties and backup and job monitoring logs.
How does SOX relate to SOC 2 and ISO 27001?
SOX is a legal requirement focused on financial reporting, while SOC 2 and ISO 27001 are voluntary security frameworks. They overlap heavily on IT general controls such as access management, change management and logging, so evidence gathered for SOC 2 or ISO 27001 can often support SOX IT controls. Service organisations usually provide a SOC 1 report, rather than SOC 2, to support customers' SOX audits.
Does OneClickComply support SOX?
Yes. SOX is supported in OneClickComply today. We collect evidence for SOX IT general controls automatically, monitor those controls continuously and reuse evidence from SOC 2 or ISO 27001. OneClickComply does not perform the Section 404(b) attestation, which must come from your registered public accounting firm.
Related frameworks
- NAIC Insurance Data Security Model Law (MDL-668)Law · United States
- NYDFS Cybersecurity Regulation (23 NYCRR Part 500)Regulation · United States
- FTC Safeguards Rule (GLBA, 16 CFR Part 314)Regulation · United States
- FCA Cyber Risk Management Rule (12 CFR Part 609)Regulation · United States
- SEC Cybersecurity Disclosure RuleRegulation · United States
- Payment Services Directive 2 (PSD2)Law · EU
- PCI DSS v4.0.1Standard · Global
- MAS Technology Risk Management GuidelinesGuidance · Singapore
Start working towards SOX
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.