Law · Financial reporting · United States
SOX ITGC: the IT general controls auditors test and how to pass
SOX ITGCs are the IT general controls that support financial reporting at US-listed companies under Sections 302 and 404 of the Sarbanes-Oxley Act. Auditors test three areas every year: access to programs and data, program changes, and computer operations, plus reliance on SOC 1 reports for outsourced systems.
What you need to know about SOX ITGC
Who needs SOX ITGCs?
US-listed companies and the teams and providers that support their financial reporting.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What do SOX ITGCs cover?
SOX ITGCs cover who can access financially significant systems, how changes reach production, and how systems run and recover. Auditors test them so they can rely on application controls and system reports.
Access to programs and data
Provisioning, removal, reviews, privileged access, SoD.
In QULDEX: Sampling per controlProgram changes
Authorise, test, approve, segregate.
In QULDEX: Change population per periodComputer operations
Jobs, backups, incidents.
In QULDEX: Operational evidenceService organisations
SOC 1 reports and CUECs.
In QULDEX: Reports tracked per vendorDeficiencies
Deficiency, significant deficiency, material weakness.
In QULDEX: Findings with severityWhich SOX ITGCs do auditors test?
These 18 controls and concepts carry most ITGC testing, grouped by area. Select any one to see what it asks for, typical evidence and how QULDEX handles it.
Showing up to 6 per group. Search, filter, or open a group to see all 18.
Access to programs and data 6
APD-01User access provisioningNew and changed access to in-scope systems is requested, approved and granted as approved.
In QULDEXProvisioning tickets are sampled in the audit workspace.
- Typical evidence
- Approved tickets
- Maps to
- ISO 27001 A.5.18SOC 2 CC6.2
APD-02User access removalLeavers' access is removed promptly.
In QULDEXLeaver lists are matched to access removal automatically for sampling.
- Typical evidence
- HR leaver list, removal evidence
- Maps to
- ISO 27001 A.5.18
APD-03Periodic user access reviewsBusiness owners review access to financially significant applications, typically quarterly.
In QULDEXReviews run as recurring tasks with sign-off and revocations tracked.
- Typical evidence
- Signed review, revocations
- Maps to
- SOC 2 CC6.3
APD-04Privileged accessAdministrator and superuser access is restricted, approved and monitored.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Privileged user list, monitoring
- Maps to
- ISO 27001 A.8.2
APD-05Segregation of dutiesConflicting duties are separated or monitored with compensating controls.
In QULDEXSoD conflicts are tracked with owners.
- Typical evidence
- SoD matrix
APD-06AuthenticationPassword and MFA settings meet policy for in-scope systems.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Configuration evidence
- Maps to
- ISO 27001 A.8.5
Program changes 5
PC-01Change authorisationChanges to in-scope systems are authorised before development.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Change tickets
- Maps to
- ISO 27001 A.8.32
PC-02Change testingChanges are tested and test results approved.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Test evidence
PC-03Change approval for productionChanges are approved before migration to production.
In QULDEXChange population and samples are kept per period.
- Typical evidence
- Approval evidence
PC-04Developer access to productionDevelopers cannot move their own changes to production without control.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Access lists
- Maps to
- ISO 27001 A.8.31
PC-05Emergency changesEmergency changes are documented and approved after the fact.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Emergency change log
Computer operations 3
CO-01Job scheduling and monitoringBatch jobs and interfaces are scheduled, monitored and failures resolved.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Job logs
CO-02Backup and recoveryFinancial data is backed up and restores are tested.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Backup logs, restore tests
- Maps to
- ISO 27001 A.8.13
CO-03Incident and problem managementIT incidents affecting financial systems are tracked to resolution.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Incident tickets
Audit and evaluation 4
AS 2201Integrated auditThe external auditor audits internal control over financial reporting alongside the financial statements.
In QULDEXAuditors get view-only, logged access to the evidence.
- Typical evidence
- Auditor requests
SOC 1Service organisation relianceVendor relianceControls at outsourced providers are covered by SOC 1 Type II reports and complementary user entity controls.
In QULDEXSOC 1 reports and CUECs are tracked per provider.
- Typical evidence
- SOC 1 reports, CUEC mapping
IPEInformation produced by the entityReports used in controls are complete and accurate.
In QULDEXQULDEX tracks this control with an owner, test steps, samples and evidence each period, so testing rolls forward instead of starting over.
- Typical evidence
- Report validation
DeficiencyDeficiency evaluationExceptions are classified as a deficiency, significant deficiency or material weakness.
In QULDEXExceptions become findings with severity and remediation.
- Typical evidence
- Deficiency log
Nothing matches that search.
Control IDs are QULDEX reference labels; your company's control matrix uses its own numbering. Summaries reflect common practice, not a rule list.
How do you run a SOX ITGC programme?
Scope the systems that matter to financial reporting, document the controls, test them through the year, fix exceptions and support the external audit. The cycle repeats every year.
Scope in-scope systems
Identify applications, databases and infrastructure supporting significant accounts.
Document the control matrix
Control descriptions, owners, frequency and test steps.
Collect SOC 1 reports
Map CUECs for each outsourced system.
Test controls
Interim and year-end testing with samples.
Remediate exceptions
Classify deficiencies and fix before year-end.
Support the external audit
Q1–Q3Interim testingQ4Roll-forward and year-endAfterManagement assessment and audit opinion
Durations are QULDEX planning ranges for one annual cycle.
Which documents does SOX ITGC testing need?
Auditors ask for these records each year.
| Document | Area | Where it lives in QULDEX |
|---|---|---|
| In-scope system list | Scoping | Risk register |
| ITGC control matrix | All | Control library |
| User access review sign-offs | APD-03 | Evidence vault |
| Provisioning and removal samples | APD-01, APD-02 | Evidence vault |
| Change populations and samples | PC-01–PC-05 | Evidence vault |
| Backup and restore evidence | CO-02 | Evidence vault |
| SOC 1 reports and CUEC mapping | SOC 1 | Vendor register |
| Deficiency evaluation | Deficiency | CAPA automation |
Control IDs are QULDEX reference labels.
How much effort does SOX ITGC take?
A first-year programme typically takes 3 to 6 months to set up; after that, testing runs through the year. The number of in-scope systems and how automated access and change evidence is drive the effort.
Where the time goes
Bars compare relative effort across an annual cycle.
What changes the effort
- In-scope systems: each adds access and change testing
- Automation: system-generated populations save sampling time
- Outsourcing: SOC 1 gaps need compensating controls
- Prior-year findings: repeat exceptions raise severity
- Existing SOC 2 or ISO 27001: access and change evidence overlaps
How ready are your SOX ITGCs?
Check these eight things first. Nothing you enter leaves this page.
How SOX ITGCs map to SOC 2, ISO 27001 and COBIT
Access and change controls overlap heavily with SOC 2 and ISO 27001, so one control set can serve SOX testing and security certifications.
ITGC crosswalk
| SOX ITGC area | SOC 2 | ISO 27001:2022 | COBIT 2019 | Shared evidence |
|---|---|---|---|---|
| User access provisioning | CC6.2 | A.5.18 | DSS05.04 | Access tickets |
| Access reviews | CC6.3 | A.5.18 | DSS05.04 | Review sign-offs |
| Privileged access | CC6.1 | A.8.2 | DSS05.04 | Admin lists |
| Change management | CC8.1 | A.8.32 | BAI06 | Change samples |
| Backup and recovery | A1.2 | A.8.13 | DSS04 | Restore tests |
| Job monitoring | CC7.1 | A.8.6 | DSS01 | Job logs |
Indicative mapping for planning.
How QULDEX runs SOX ITGC testing from scoping to audit opinion
QULDEX is SOX ITGC testing and audit management software built from EGV Group's audit delivery, used by control owners, internal audit and the external auditors who rely on their work. Pick your role to see who does what.
For IT and business owners of SOX controls.
- ScopeAgree in-scope systemsSystem list linked to accounts
- EvidenceProvide populationsPopulations and samples per period
- ReviewsSign access reviewsRecurring review tasks
- TestFix exceptionsExceptions into CAPA
- VendorsMap SOC 1 CUECsSOC 1 register
- OpinionSupport year-endRoll-forward evidence
For internal audit and SOX programme teams.
- ScopeRun scopingA reusable ITGC matrix
- EvidenceRequest evidenceRequests with due dates
- ReviewsCheck sign-offsReview status
- TestTest controlsTest steps and results
- VendorsAssess gapsGap list
- OpinionEvaluate deficienciesSeverity log
For audit firms performing integrated audits.
- ScopePlanScope in a standard format
- EvidenceRequestView-only evidence with download control and an access log
- ReviewsInspectReview history
- TestReperformWorkpapers
- VendorsRelyVendor evidence
- OpinionConcludeTraceable audit record
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →SOX ITGC questions people ask
What are SOX ITGCs?
IT general controls over the systems that support financial reporting at US-listed companies. They cover access to programs and data, program changes, program development and computer operations, and auditors test them under PCAOB AS 2201.
Which ITGC areas do auditors test?
Mainly access (provisioning, removal, reviews, privileged access, segregation of duties), change management (authorisation, testing, approval, segregation) and computer operations (jobs, backups, incidents).
What is the difference between a significant deficiency and a material weakness?
A material weakness is a deficiency that creates a reasonable possibility of a material misstatement not being prevented or detected on time, and it must be disclosed. A significant deficiency is less severe but important enough to tell the audit committee.
Do SOC 1 reports help with SOX?
Yes. A SOC 1 Type II report on an outsourced provider lets auditors rely on its controls, provided you operate the complementary user entity controls (CUECs) it lists.
How often should user access reviews be done for SOX?
Quarterly is the most common practice for financially significant applications, though frequency depends on risk and your auditor's expectations.
Go deeper on SOX ITGC
Audit sampling size for compliance
How many samples auditors look at for each control frequency.
blog.quldex.comAudit evidence naming convention
A file-naming scheme auditors can follow.
blog.quldex.comMajor vs minor nonconformity, with examples
How auditors grade findings.
blog.quldex.comSOC 2 bridge letter
How SOC reports cover gaps between periods.
References
- Sarbanes-Oxley Act of 2002, Sections 302 and 404. sec.gov
- PCAOB Auditing Standard AS 2201. pcaobus.org
- COSO Internal Control – Integrated Framework (2013). coso.org
- AICPA SOC 1 guide. aicpa-cima.com
Reviewed by
Page history
- : Page first built: ITGC control explorer, annual cycle, readiness check and crosswalk
Find your ITGC exceptions before the auditor does
Answer a short readiness check and get a gap summary by ITGC area. No sales call needed to see the result.