ITGC stands for IT general controls: the baseline controls over how an organization manages access, changes, development and day-to-day operations across its IT environment. They are called “general” because they do not belong to any single business process. Instead, they protect the systems that every process depends on, such as the ERP, the payroll platform, the databases behind financial reporting and the cloud infrastructure that hosts them.
If ITGCs are weak, an auditor cannot easily rely on the automated controls and system-generated reports built on top of them. That is why ITGCs sit at the center of financial statement audits, SOX programs, SOC 1 and SOC 2 reports and many internal audit plans. This guide explains what ITGCs cover, gives practical examples and shows how they are tested.
Why IT General Controls Matter
Most organizations run key business controls inside software. A three-way match in the ERP, an automatic approval limit or a system-calculated revenue report are all application controls. They only work as designed if nobody can quietly change the configuration, grant themselves excessive access or push untested code into production. ITGCs provide that assurance.
In the United States, the PCAOB’s auditing standard for integrated audits, AS 2201, requires auditors of public companies to consider IT risks when evaluating internal control over financial reporting. The COSO Internal Control framework, used by many companies to structure their controls, also includes a specific principle on selecting and developing general control activities over technology. Outside the SOX world, ITGCs appear in SOC 1 reports, in the logical access and change management criteria of SOC 2, and in ISO 27001 Annex A controls.
The Four Core ITGC Domains
Different frameworks group ITGCs slightly differently, but most audit programs use four domains.
1. Access to Programs and Data
Access controls make sure only authorized people can use, change or administer in-scope systems. This is usually the largest domain and the one with the most findings.
- User provisioning based on an approved request from the right manager
- Timely removal of access for leavers and role changes
- Periodic user access reviews performed by system or data owners
- Restricted and monitored privileged and administrator accounts
- Password, MFA and session settings aligned with policy
- Segregation of duties between developers, administrators and business users
2. Program Changes
Change management controls make sure changes to in-scope applications, databases and infrastructure are authorized, tested and approved before they reach production.
- Documented change requests with business justification
- Testing evidence, including user acceptance testing for significant changes
- Approval before deployment by someone other than the developer
- Separation between development, test and production environments
- Emergency change procedures with after-the-fact review
- Monitoring that detects unauthorized changes
3. Program Development and Acquisition
These controls cover new systems and major upgrades: requirements, design review, testing, data migration and go-live approval. Many organizations fold this domain into change management, but auditors look at it separately when a new ERP or finance platform goes live during the audit period.
4. Computer Operations
Operations controls make sure systems run reliably and that processing failures are detected and fixed.
- Job scheduling and monitoring of batch jobs and interfaces
- Backup scheduling, monitoring and periodic restore testing
- Incident and problem management
- Monitoring of system availability and capacity
ITGC Examples by Domain
| Domain | Example control | Typical evidence |
|---|---|---|
| Access | New access to the ERP is granted only after line-manager approval in the ticketing tool. | Sample of tickets matched to user creation dates |
| Access | Leaver accounts are disabled within an agreed timeframe of the HR termination date. | HR leaver list compared with account disable dates |
| Access | Quarterly user access reviews are signed off by system owners. | Review reports, sign-offs and evidence of removals |
| Access | Database administrator activity is logged and reviewed. | Log extracts and review records |
| Change | Production changes require testing and approval by a person independent of the developer. | Change tickets with test results and approvals |
| Change | Developers have no write access to production. | Access listings for production environments |
| Development | Data migration for a new system is reconciled and approved before go-live. | Reconciliation reports and go-live sign-off |
| Operations | Failed backup and batch jobs are investigated and resolved. | Job monitoring logs and incident tickets |
ITGCs vs Application Controls
Application controls operate inside a specific system to process transactions correctly, for example an edit check that blocks an invoice without a purchase order. ITGCs support the environment those controls run in. Auditors usually test ITGCs first: if access or change controls fail, they cannot assume an automated control worked consistently through the year, and they may need to expand testing or look for compensating controls.
How ITGCs Are Tested
Auditors evaluate both the design of a control (would it prevent or detect the risk if it operated as described?) and its operating effectiveness (did it actually operate throughout the period?). Common procedures include:
- Inquiry with control owners about how the control works
- Observation of the control being performed
- Inspection of evidence such as tickets, approvals and review sign-offs
- Reperformance, for example comparing an HR leaver list with system disable dates
Sample sizes depend on how often a control runs and on the audit methodology. A quarterly access review might be tested for every quarter in the period, while a control that operates many times a day is tested on a sample. Auditors also test the completeness and accuracy of system-generated reports used in controls, often called information produced by the entity (IPE). For a deeper look at testing, see our guide to the ITGC audit process and our IT general controls audit and compliance services.
Common Reasons ITGCs Fail
- Leavers keep active accounts, especially in secondary systems or cloud consoles outside single sign-on
- Access reviews are signed off without evidence of a real review or follow-up removals
- Shared or generic administrator accounts with no individual accountability
- Developers able to deploy their own code to production
- Emergency changes that are never reviewed after the fact
- Backup jobs monitored but restore tests never performed
- Key reports used in controls with no check on completeness and accuracy
Most of these issues are process problems rather than technology gaps. Strong privileged access management, automated provisioning tied to HR events and a single change workflow resolve many of them.
How to Get Started With ITGCs
- Scope the systems. Identify applications, databases, operating systems and cloud platforms that support financial reporting or customer commitments.
- Map risks to controls. For each system, document the access, change and operations risks and the controls that address them.
- Assign owners. Every control needs a named owner and a defined frequency.
- Standardize evidence. Decide in advance what evidence each control will produce and where it will be stored.
- Run a readiness test. Test a sample internally or with an independent reviewer before the external audit.
- Fix and monitor. Track remediation and keep testing through the year rather than only at year-end.
If you are preparing for a SOC report, our comparison of SOC 1 vs SOC 2 vs SOC 3 explains where ITGCs fit, and our cybersecurity compliance roadmap shows how they connect with broader security controls.
Key Takeaways
- ITGCs are the baseline controls over access, program changes, program development and computer operations.
- They protect the systems that application controls and financial reports depend on.
- Auditors test both design and operating effectiveness, usually before relying on automated controls.
- Most ITGC failures come from weak leaver processes, superficial access reviews and uncontrolled changes.
Frequently Asked Questions
What does ITGC stand for?
ITGC stands for IT general controls, the baseline controls over access, program changes, program development and computer operations that support the reliability of IT systems.
What are the four main ITGC domains?
Access to programs and data, program changes, program development and acquisition, and computer operations.
What is the difference between ITGCs and application controls?
Application controls operate inside a specific system to process transactions correctly. ITGCs protect the environment those controls run in, so application controls can only be relied on if the related ITGCs are effective.
Are ITGCs only required for SOX?
No. ITGCs are central to SOX programs, but they are also tested in SOC 1 and SOC 2 reports, internal audits and many security frameworks such as ISO 27001.
How often should user access reviews be performed?
Frequency depends on risk and the framework you follow. Many organizations review access to critical financial and production systems quarterly and lower-risk systems less often.
Preparing for an audit? Securis360 helps organizations scope, document and test IT general controls before auditors arrive. Talk to our team about an ITGC readiness review.