An IT general controls audit evaluates whether the controls over access, change management, development and IT operations for in-scope systems are designed properly and operated effectively throughout a period. It is a core part of financial statement audits, SOX 404 programs and SOC 1 and SOC 2 examinations. Knowing how auditors scope systems, which evidence they request and where deficiencies usually appear lets you fix issues before testing starts rather than explaining them afterwards.

If you need a primer on the controls themselves, read What Is ITGC? IT General Controls Explained with Examples first.

Step 1: Scoping the ITGC Audit

Scoping starts with business processes, not technology. Auditors identify significant accounts and processes, the key controls within them, and the systems those controls and reports rely on. Each relevant system is then broken into layers:

  • Application: ERP, billing, payroll, treasury or custom finance applications
  • Database: the databases holding the application’s data
  • Operating system: servers hosting the application and database
  • Infrastructure and cloud: cloud consoles, identity providers, network devices and virtualization platforms
  • Supporting tools: job schedulers, deployment pipelines, ticketing tools and identity management systems

For SaaS applications, auditors usually rely on the provider’s SOC 1 or SOC 2 report for controls the provider operates and test only the customer-side controls, such as user access management and complementary user entity controls (CUECs) listed in the report.

Step 2: Understanding and Walkthroughs

Auditors meet control owners to understand how each control works, who performs it, how often and what evidence it produces. They usually walk through one instance end to end, for example following a single new-joiner request from HR to account creation. Walkthroughs often reveal design gaps, such as approvals happening by chat with no record.

Step 3: Testing Design and Operating Effectiveness

Design testing asks whether the control, if performed as described, would address the risk. Operating effectiveness testing asks whether it actually operated consistently across the period. Sample sizes depend on control frequency and the auditor’s methodology.

Control frequencyExampleTesting approach
Annual or quarterlyUser access reviewOften every instance in the period
Monthly or weeklyBackup restore test, privileged log reviewA sample of instances
Daily or many times a dayChange approvals, batch job monitoringLarger sample from the population
AutomatedPassword configuration, workflow enforcementTest of one instance plus reliance on change controls

Evidence Auditors Commonly Request

  • Complete user listings for each in-scope system, with roles and last login dates
  • HR joiner, mover and leaver lists for the period
  • Access request tickets and approvals
  • User access review reports with reviewer sign-off and evidence of removals
  • Privileged account listings and monitoring evidence
  • Password, MFA and session configuration screenshots or exports
  • Population of production changes, with tickets, testing and approvals
  • Lists of who can deploy to production
  • Backup job logs, restore test results and batch job monitoring records
  • Incident tickets related to in-scope systems

Auditors also check the completeness and accuracy of the populations you provide. If a change list is exported from a ticketing tool, they may ask how you know every production change is in it, for example by comparing it with deployment logs.

How Deficiencies Are Classified

When a control fails, auditors assess its severity. In SOX terminology, issues range from a control deficiency to a significant deficiency to a material weakness, depending on the likelihood and magnitude of a potential misstatement and whether compensating controls exist. An ITGC failure does not automatically become a material weakness, but it can force auditors to perform much more substantive testing and reduce reliance on automated controls.

The Most Common ITGC Deficiencies

Access Management

  • Leavers with active accounts after their departure date, especially in systems outside single sign-on
  • Access reviews that are rubber-stamped, incomplete or missing evidence of follow-up
  • Excessive privileged access, shared admin accounts and service accounts with interactive login
  • Segregation of duties conflicts, such as developers with production access

Change Management

  • Changes deployed without evidence of testing or approval
  • Developers able to approve and deploy their own changes
  • Emergency changes without retrospective review
  • Direct database changes made outside the change process

IT Operations

  • Failed backups or batch jobs not investigated
  • No evidence of periodic restore testing
  • Monitoring alerts with no documented response

Reports and Populations

  • System reports used in controls with no completeness and accuracy validation
  • Incomplete change or user populations

How to Prepare for an ITGC Audit

  1. Confirm scope early with your auditors so there are no late additions.
  2. Document each control with owner, frequency, procedure and evidence location.
  3. Run a self-assessment on a sample before the auditors do.
  4. Reconcile leavers against every in-scope system, not only the directory.
  5. Tighten privileged access following privileged access management best practices.
  6. Fix change management so every production change has a ticket, test evidence and independent approval.
  7. Collect SOC reports for in-scope SaaS providers and map CUECs to your controls.
  8. Remediate early so fixed controls have time to operate before period end.

Organizations preparing for both SOX and security certifications can align efforts using our cybersecurity compliance roadmap.

Key Takeaways

  • An IT general controls audit starts from business processes and maps them to application, database, OS and infrastructure layers.
  • Auditors test both design and operating effectiveness, with sample sizes driven by control frequency.
  • Access, change management and report accuracy are the most common sources of deficiencies.
  • A readiness self-assessment and early remediation reduce findings and audit effort.

Frequently Asked Questions

What is an IT general controls audit?

It is an evaluation of whether controls over access, change management, development and IT operations for in-scope systems are well designed and operated effectively over a period.

Which systems are in scope for an ITGC audit?

Systems that support significant financial processes, key controls or relied-upon reports, including the related applications, databases, operating systems, cloud platforms and supporting tools.

How are SaaS applications handled in an ITGC audit?

Auditors usually rely on the provider SOC 1 or SOC 2 report for provider-operated controls and test customer-side controls such as user access management and complementary user entity controls.

What are the most common ITGC deficiencies?

Terminated users with active access, weak user access reviews, excessive privileged access, unapproved or untested changes, developer access to production and unvalidated system reports.

Does an ITGC deficiency mean a material weakness?

Not necessarily. Severity depends on the potential impact on financial reporting and whether compensating controls exist, but ITGC failures can significantly expand audit testing.

Want fewer surprises in your next ITGC audit? Securis360’s IT general controls audit and compliance services include scoping support, readiness testing and remediation guidance. Book an ITGC readiness assessment.