What are SOX ITGCs?
Section 404 of the Sarbanes-Oxley Act requires public companies to assess their internal control over financial reporting. IT general controls (ITGCs) are the controls over the systems that produce the financial numbers. Auditors typically group them into access to programs and data, program changes, program development and computer operations. If ITGCs fail, the auditor cannot rely on the automated controls and reports that depend on those systems.
404(a) and 404(b)
- 404(a): management assesses and reports on internal control over financial reporting each year.
- 404(b): the external auditor attests to that assessment, under PCAOB AS 2201. Non-accelerated filers are exempt, and newly public companies get a transition period (Regulation S-K Item 308).
In May 2026 the SEC proposed narrowing the 404(b) attestation requirement (File S7-2026-18). Check its status before planning around it.
Where ITGCs most often fail
- User access reviews done but not documented or evidenced
- Leavers' access removed late
- Segregation of duties conflicts, especially developers with access to production
- Change approvals missing, or given after the change
- Logging too thin to prove a control operated
Auditors also need evidence that a control operated for long enough; a control switched on just before year end often cannot be relied on.
What it costs
The estimator above adds readiness work (per system in scope, scaled by how many control areas are missing) to an external audit fee band for the auditor tier you choose. There is no public fee schedule, so the bands are our planning estimates.
We do the technical side: access reviews, deprovisioning, change control and logging. See vCISO services.
Sources
- Sarbanes-Oxley Act s.404, 15 U.S.C. 7262
- Regulation S-K Item 308 (eCFR)
- PCAOB AS 2201
- SEC proposed rule, File S7-2026-18 (May 2026)
Facts checked against the sources above on 22 October 2026. General information, not legal advice.
