ITGC Audit Checklist for SOX: Access, Change Management and IT Operations

ITGC Audit Checklist for SOX: Access, Change Management and IT Operations

var(--variable-LoqRZ1RA_)
var(--variable-LoqRZ1RA_)

An ITGC audit checklist helps finance, IT and compliance teams evaluate whether the technology supporting financial reporting is adequately controlled. For companies subject to Sarbanes-Oxley (SOX) requirements, weaknesses in user access, software changes, or IT operations can undermine automated accounting controls and the reports management relies upon for financial statements.

This guide provides a risk-based checklist of logical access, change management, IT operations, and relevant physical security controls, together with evidence examples, testing methods and an actionable preparation plan. It is designed for CFOs, SOX program owners and IT control owners preparing for internal testing or an independent ICFR audit.

Quick answer: Start by identifying financial reporting applications and the risks they support. Test relevant privileged access and user lifecycle controls, approvals and testing of material system changes, monitoring of significant processing and backups, and applicable physical controls. Preserve evidence demonstrating that the controls actually operated during the review period.

What Is an ITGC Audit and Why Does It Matter for SOX?

Information technology general controls (ITGCs) are foundational procedures that help ensure the systems and data used in financial reporting operate as intended. They typically span logical access, program changes and computer operations. Physical and environmental safeguards may also be relevant when they protect systems that support material financial reporting processes.

The SEC’s risk-based ICFR guidance explains that management should consider ITGCs important to automated or IT-dependent controls addressing financial reporting risks—not automatically test every security process in the company. PCAOB AS 2201 likewise integrates IT risks into the top-down approach to significant accounts, assertions and control selection. Internal Control Over Financial Reporting guide provides the broader context.

ITGCs vs application controls

An application control might automatically prevent posting a journal entry without a balanced debit and credit. ITGCs address whether administrators can bypass that rule, whether changes to the validation logic are approved, and whether underlying processing is reliable. Strong ITGCs support—but do not replace—effective application controls.

What falls outside the SOX ITGC scope?

Not every cybersecurity or operational safeguard is automatically an ICFR key control. A marketing-site availability alert, for example, may be operationally valuable but out of scope if it does not affect relevant financial reporting risks. Conversely, administrator access to the general ledger can be in scope even if the system is hosted by a third party.

How to Scope an ITGC Audit Checklist for SOX

Map systems to significant financial reporting risks

Begin with material accounts and disclosures—such as revenue, cash, inventory, debt and consolidation—then trace transactions, calculations, interfaces and reports to the applications and infrastructure that support them. Record whether a system performs automated controls, produces information used in controls (IPE), or enables material journal entries.

Identify shared infrastructure and service providers

Review ERP platforms, identity providers, databases, reporting warehouses, integration services and relevant cloud environments. For outsourced systems, obtain applicable SOC 1 reports where available, assess the period covered, identify complementary user entity controls (CUECs), and evaluate any gaps or subservice carve-outs. A SOC 2 report alone does not automatically establish effective ICFR controls.

Document risk, control, owner and frequency

A useful scoping memo should explain why each ITGC matters to a financial statement assertion, which control addresses the risk, who operates it, how often, and what evidence is retained. Coordinate scoping with management’s ICFR assessment and with the independent auditor, without assuming the two programs use identical procedures. See ICFR Risk Assessment: How to Scope Key Controls.

Scoping field

Illustrative entry

Financial statement risk

Unauthorized revenue adjustments may misstate reported sales

In-scope system

ERP revenue and general ledger modules

IT dependency

Privileged users can change role permissions and posting rules

Relevant ITGC

Privileged-access review; approved changes

Evidence

Dated access export, reviewer sign-off, change tickets

Owner/frequency

IT security quarterly; change owner per deployment

 

ITGC Audit Checklist: Logical Access Controls

Access controls aim to prevent unauthorized users from altering relevant transactions, reports, system configurations or financial data. The test should cover the systems, users and permissions that can affect ICFR—not simply whether the organization has a password policy.

Provisioning, transfers and terminations

  • New users require documented authorization and roles aligned with their duties.

  • Role changes are approved and incompatible entitlements reassessed.

  • Terminated personnel lose relevant system access promptly under defined policy.

  • Service and shared accounts have assigned owners, restricted purpose and monitoring.

  • Access-review populations reconcile to a complete, accurate system-generated user listing.

Privileged access and segregation of duties

  • Administrative accounts are inventoried and access is restricted to authorized personnel.

  • Privileged or emergency access is logged and independently reviewed where relevant.

  • Conflicting capabilities such as vendor creation and payment approval are evaluated.

  • Periodic access reviews show reviewer analysis, exceptions and follow-up resolution.

  • Authentication and remote access safeguards are designed for relevant financial systems.

Typical evidence: HR onboarding and termination records, access requests, role matrices, user exports, privileged-group listings, approval tickets, review sign-offs, and exception remediation. For testing, select a risk-based sample of lifecycle events and examine timely approvals, provisioning and removal—not inquiry alone.

ITGC Audit Checklist: Change Management

Unauthorized or inadequately tested changes to ERP configurations, interfaces, reports, scripts and automated accounting logic can affect financial reporting even when underlying transactions are otherwise valid.

Changes to code, configurations and reports

  • In-scope changes have documented business justification and authorization.

  • Changes are tested before production; evidence explains the results and exceptions.

  • Development, test and production permissions are appropriately segregated.

  • Production deployment is approved by an authorized person or process.

  • Sensitive accounting master data and report logic changes are controlled where relevant.

Emergency changes and monitoring

  • Emergency changes are identified, documented and subject to timely retrospective review.

  • System change logs are complete enough to support the testing population.

  • Failed or rolled-back deployments are investigated as required.

  • Change exceptions have an owner, resolution date and evidence of closure.

Typical evidence: change tickets, approvals, test results, release logs, code-review records, deployment records, emergency-change registers, and completeness checks against system logs. A clean ticket template is not enough: the auditor needs evidence that control steps actually occurred.

ITGC Audit Checklist: IT Operations

Computer operations controls support dependable processing, data availability and the integrity of financial reporting jobs and interfaces. Their relevance depends on the particular reporting risks and reliance on automated processing.

Scheduled jobs, interfaces and processing

  • Significant batch jobs or interfaces are monitored for failure and exceptions.

  • Processing errors are assigned, investigated and resolved.

  • Critical reconciliations validate completeness and accuracy of transferred data.

  • Operations personnel retain evidence of exception monitoring and escalation.

Backup, recovery and incidents

  • Backups cover relevant financial reporting systems and data.

  • Failures are monitored and followed up according to defined procedures.

  • Recovery testing is performed and documented based on relevant risks.

  • Security or operational incidents affecting financial reporting are assessed and escalated.

  • Recovery objectives and responsibilities are defined for critical systems.

Typical evidence: scheduled-job dashboards, interface reconciliation logs, incident tickets, backup status reports, restore-test documentation, and issue resolution records. A backup success notification does not by itself establish that data can be restored accurately.

ITGC Audit Checklist: Physical Security and Third-Party Hosting

Physical security is relevant when unauthorized physical access to servers, backup media or infrastructure could compromise financial reporting applications and data. The assessment must reflect whether systems are operated on premises, in a colocation facility or by a cloud provider.

On-premises and colocation facilities

  • Data center access is limited to authorized personnel.

  • Visitor access is documented and supervised where appropriate.

  • Physical access rights are reviewed and promptly removed after changes in role.

  • Environmental incidents affecting relevant equipment are monitored and escalated.

Cloud and managed services

  • Identify which controls the provider operates and which remain management responsibilities.

  • Review relevant independent service-organization reports and their scope.

  • Track exceptions, coverage gaps and CUECs affecting financial reporting.

  • Document management’s response to any control gaps.

Sample ITGC Risk-Control Matrix and Audit Evidence Tracker

Domain

Risk / control objective

Key evidence

Test focus

Access

Only authorized users can change GL posting or configurations

User inventory; approvals; access review

Population completeness; approvals; exceptions

Changes

Only approved/tested ERP changes reach production

Change logs; test reports; deployment approval

Trace selected releases end-to-end

Operations

Critical revenue interfaces process completely

Job monitoring; exception tickets; reconciliations

Failure identification and timely resolution

Physical/cloud

Relevant infrastructure remains controlled

Badge logs or SOC 1; CUEC assessment

Provider control coverage and user duties

 

Use a tracker with fields for control ID, control owner, test period, requested evidence, source system, population completeness validation, reviewer, exceptions, remediation status and closure evidence. Mark items as “not applicable” only when the risk assessment supports exclusion.

How to Test ITGC Design and Operating Effectiveness

Step 1: Establish population completeness

Before sampling, determine whether the access listing, change population or incident register includes the relevant full period and systems. An incomplete population can undermine every later test result.

Step 2: Evaluate design effectiveness

Determine whether the control, if executed as described, would prevent or detect the relevant risk on a timely basis. For a quarterly access review, ask whether the reviewer can identify risky privileges and whether follow-up is required—not merely whether a review is scheduled.

Step 3: Test evidence of operation

Inspect approvals, logs, review notes and resolved exceptions; reperform steps when appropriate. Inquiry alone generally provides weaker evidence. The nature and extent of testing should respond to risk, control frequency and relevant professional standards.

Step 4: Assess exceptions and deficiencies

A missed user termination, unapproved change or unresolved interface failure should be evaluated in context. Consider related application controls, potential magnitude and likelihood of misstatement, and whether multiple issues aggregate into a significant deficiency or material weakness. See Material Weakness Remediation Guide.

Step 5: Remediate and retest

Assign accountable owners, implement corrective measures, and gather enough operating history to support management’s conclusion. One corrected access record does not automatically prove that a recurring access-review control now works effectively.

Common ITGC Audit Findings—and How to Avoid Them

Finding

Why it matters

Practical corrective action

Stale privileged accounts

Unauthorized changes to key systems

Remove access; reconcile users to HR; monitor

Access review without scrutiny

Reviewer may overlook risky entitlements

Provide risk-oriented review criteria and evidence

Unapproved production changes

Automated controls may be altered

Require approvals, test results and emergency process

Incomplete change population

Testing may miss significant deployments

Reconcile ticket and deployment logs

Unresolved batch failures

Financial information may be incomplete

Create escalation and reconciliation process

SOC report gaps ignored

Outsourced controls may not meet reliance needs

Evaluate exceptions and implement CUECs

 

ITGC Audit Readiness: A 30-Day Preparation Plan

Days 1–7: Confirm scope and owners

Confirm material reporting processes, in-scope applications, key IT dependencies, control owners and audit timetable. Resolve uncertainty regarding cloud, outsourced and newly implemented systems.

Days 8–14: Collect and validate evidence

Export dated user populations, change logs, operations reports and incident records. Preserve read-only copies, validate report completeness and identify gaps before submitting a PBC package.

Days 15–21: Perform a targeted gap assessment

Walk through selected provisioning, termination, change and operations events. Evaluate both design and operation; prioritize risks affecting material accounts or key automated controls.

Days 22–30: Prioritize remediation and audit coordination

Assign fixes, document any unresolved deficiencies, communicate major findings to finance leadership and the audit committee where appropriate, and prepare a realistic testing and remediation schedule. Consult Audit Evidence and PBC Preparation for document-request organization.

When to Consider ITGC Readiness Assessment or SOX Audit Services

Organizations often seek specialist support when an ERP migration changes key controls, an IPO moves closer, recurring access or change-management findings appear, or an upcoming SOX 404(b) audit requires coordinated evidence across finance and IT. The scope of assistance should reflect the company’s risks, current staffing and independence considerations.

When comparing external providers, ask about issuer audit experience, PCAOB registration where applicable, IT audit capability, scope definition, communication with the audit committee and management responsibilities. Avoid assuming a software platform automatically achieves SOX compliance; it can support evidence collection and workflows but cannot replace judgment, operation or independent evaluation.

MBP Global LLP describes partner-led SEC and public company audit services, together with internal control and SOX-related services. Companies evaluating independent assurance can review MBP Global’s Audit & Assurance Services and discuss a properly scoped engagement. An incumbent independent auditor must observe SEC and PCAOB independence restrictions and cannot assume prohibited management responsibilities over controls it audits.

Frequently Asked Questions About ITGC Audits

What does ITGC stand for in a SOX audit?

ITGC means information technology general controls. They address technology risks relevant to reliable financial reporting, including access, changes and computer operations.

Are ITGC audits mandatory for every public company?

SOX and ICFR obligations depend on filer status and circumstances. Relevant IT controls are considered within the company’s ICFR evaluation; an independent SOX 404(b) attestation is not required for every issuer.

What are the four main ITGC domains?

Common practical categories are logical access, change management, IT operations, and relevant physical/environmental security. Actual SOX scoping is risk-based rather than a requirement to test every category in full.

What evidence should be on an ITGC audit checklist?

Expect relevant user lists and reviews, access approvals, changes and release records, operating job logs, incident records, backup/restoration evidence, and service-provider reports where applicable.

Is a SOC 2 report enough to satisfy SOX ITGC requirements?

Not automatically. The report’s control objectives, scope, period, exceptions, subservice organizations and complementary user controls must be assessed against financial reporting risks. A SOC 1 report may be more directly applicable.

How often should privileged access be reviewed?

Frequency depends on risk, system criticality, the designed control and company policy. There is no one-size-fits-all SOX rule requiring all user reviews on the same schedule.

Can SOX compliance software replace manual control testing?

Software can organize evidence and automate workflows, but control design, exception evaluation and assurance remain necessary. Automated evidence may itself require completeness and accuracy checks.

What happens if ITGC testing identifies a material weakness?

Management must evaluate the impact on ICFR and applicable disclosures. For an issuer subject to an external ICFR audit, a material weakness generally results in an adverse ICFR opinion; it does not automatically mean the financial statements are misstated.

How long does ITGC remediation take?

Duration depends on the control, remediation complexity, frequency and period of effective operation needed to provide evidence. A newly established quarterly control may require different evidence than a daily automated review.

Can the financial statement auditor also implement IT controls?

Independence rules restrict auditors from assuming management roles or providing certain prohibited services to audit clients. The company should separate implementation responsibilities from independent assurance where required.

Conclusion: Turn the ITGC Checklist Into Audit-Ready Evidence

An effective ITGC audit checklist connects IT risks to financial statement reporting, assigns accountable control owners and documents real evidence of control performance. Access, change management, operations and physical/cloud controls should be scoped according to the systems and assertions that matter—not tested as an undifferentiated cybersecurity inventory.

For CFOs and SOX teams, the most useful next step is a documented ITGC risk-control matrix, supported by complete populations, tested evidence and a realistic remediation plan. To discuss independent public company audit or ICFR assurance requirements, contact MBP Global LLP through its Audit & Assurance practice.