ITGC (IT General Controls): List of Controls and How to Test Them

Illustration of a security padlock for IT general controls

Topic Recommendations

Share Article

Ready To Improve Your Internal Audit Process?

Discover Audithink's full features and choose a pricing plan that works for your audit team. Start audit transformation now!

What ITGC is, the five general control categories under FISCAM, how it differs from application controls, and audit testing steps and examples.
Table Of Contents

ITGC (IT General Controls) are control policies and procedures that apply to all or most of an organization's information systems, not to a single application. These controls are the foundation that makes controls inside applications trustworthy. Auditors test ITGC to assess whether the IT environment is reliable enough before relying on the data and automated controls above it.

This article summarizes the list of ITGC controls and how to test them, with definitions based on FISCAM from GAO, the U.S. Government Accountability Office's audit manual for information system controls. References were checked as of 16 November 2026. For a broader view of IT auditing, also read the IT audit guide and Information Systems audit.

What Is ITGC in an Audit?

In FISCAM, information system controls are divided into three types. First, user controls, the part of controls performed by people when they interact with the system. Second, application controls, which are embedded directly in application software. Third, general controls.

The manual defines general controls as policies and procedures that apply to all or most of an entity's information systems. This is what is commonly called ITGC in day-to-day practice.

Its function is similar to a building's foundation. If access, program changes, and system recovery are not controlled, automated controls in applications can be bypassed or altered without a trace. That is why auditors usually test ITGC first.

What Is the Difference Between ITGC and Application Controls (ITAC)?

The main difference is scope. ITGC cover the environment in which many systems run. Application controls, often abbreviated ITAC, operate inside one specific application.

AspectITGCApplication controls (ITAC)
CoverageAll or most systemsOne application or business process
PropertiesCreates a reliable environmentControls data input, processing, and output
Example ofAccess management, change approval, backupInput validation, automatic calculations, approval limits in the system
RelationshipSupports the effectiveness of application controlsDepends on ITGC to remain reliable

FISCAM notes that application controls cover controls over data input, processing, and output. The ISACA glossary also defines application controls as policies, procedures, and activities designed to provide reasonable assurance that objectives related to automated solutions are achieved.

What Are the Control Categories in ITGC?

There is no single list used by all auditors. FISCAM groups general controls into five categories, and these five are the easiest to use as an examination framework.

CategoryAuditor key question
Security managementIs there an information security program that is managed and monitored?
Logical and physical accessWho may access systems and data, and is access restricted according to need?
Segregation of dutiesAre conflicting duties kept from being held by the same person?
Configuration managementAre system and program changes approved, tested, and recorded?
Contingency planningCan systems and data be recovered after a disruption?

FISCAM also states that, depending on the engagement objectives, an auditor may decide it is unnecessary to identify control objectives from all five categories. Coverage still follows scope and risk, not simply a checklist.

Some practitioners use four popular domains: access to programs and data, program changes, computer operations, and program development. That split is not discussed in the sources read for this article, so the grouping is deliberately not used as a reference.

What Does a Commonly Tested ITGC Control List Look Like?

The control examples below are organized by the categories above. Form and terminology will differ in each organization, so treat this as a starting point, not a standard list.

  • Security management: an information security policy that is approved and reviewed periodically, and an IT risk assessment that is carried out.
  • Access: requests, approvals, and revocation of user accounts; periodic access rights reviews; management of privileged accounts. A full discussion is in the article system access rights audit.
  • Segregation of duties: restrictions so that developers cannot move programs to production and transaction requesters cannot approve their own transactions.
  • Configuration and change: change approval, pre-release testing, and recording who changed what.
  • Contingency: regular data backup, secure storage of backup media, and a recovery plan that is tested.

For backup, FISCAM includes a control objective that system backups are performed regularly and that media holding backup data and software are protected. Auditors can use wording like this as a benchmark.

How Do You Test ITGC Step by Step?

ITGC testing procedures follow general audit logic: understand, assess design, then test operation. The sequence below is practical for internal audit teams.

  1. Identify the systems and applications relevant to the audit objectives, for example those that produce financial data or support critical processes.
  2. Understand the IT environment, including who manages the infrastructure, databases, and applications.
  3. Map controls to the five categories and select key controls based on risk.
  4. Assess design: whether the control, if it operates, adequately addresses its risk.
  5. Test operation through inquiry, inspection of documents or configurations, observation, and re-performance by the auditor.
  6. Take adequate samples for recurring controls, then record the evidence in the working papers.
  7. Evaluate deficiencies, determine their impact on application controls and the data above them, then report.

For recurring controls such as change approval, sample selection needs careful thought. The technical discussion is in the article audit sampling, and how to judge the sufficiency of evidence is in audit evidence.

What Does a Concrete ITGC Test Look Like?

The table below contains illustrative examples to show testing patterns. The data and figures do not come from a real engagement.

ControlExample test procedureEvidence recorded
Revoking access for departed employeesCompare the list of departed employees with the list of active accountsList from HR, account export, the difference
Program change approvalSelect a sample of changes, then trace the approval and testing ticketsTickets, test records, release notes
Periodic access rights reviewCheck whether the review was done on time by the process ownerReview report and its follow-up
Data backupCheck the schedule, success logs, and recovery test resultsBackup logs and recovery test minutes

The first example shows a common pattern. The auditor compares two data populations, then investigates the difference. This pattern is cheap to perform and often finds accounts that are still active after their owners have left.

Who Tests ITGC and When Is the Right Time?

Internal auditors, IT auditors, and external auditors can all test ITGC, each with different objectives. Internal auditors usually test to assess control effectiveness and readiness for other audits.

Testing time is influenced by the business cycle, major system changes, and prior audit results. A significant system change, such as a migration or the implementation of a new application, is a strong reason to reassess ITGC outside the routine schedule.

One note on editions: the FISCAM read for this article is the 2024 edition (GAO-24-107026). The GAO page states that the 2026 edition was published on 29 June 2026, so details of categories and control objectives should be rechecked against the latest edition if you use it as a formal reference.

ITGC test results should be reported using the same structure as other findings, namely criteria, condition, root cause, and impact. How to write them is covered in the guide to internal audit report.

What Are Common Mistakes in ITGC Testing?

  • Testing all controls without selecting by risk. The result is thick but unfocused.
  • Only asking for screenshots. Evidence from the source system is stronger than an image that can be altered.
  • Ignoring privileged accounts. Administrator and service accounts are often missed in reviews.
  • Not linking ITGC results to application controls. ITGC deficiencies reduce the reliability of the automated controls above them.
  • Samples that are too small or do not represent the period. Controls that changed mid-year need to be tested under both conditions.
  • Not following up. ITGC findings that are not monitored will reappear in the next audit.

How Does Audit Software Help ITGC Testing?

ITGC testing produces many working papers, evidence items, and findings across systems. Audit management software helps organize work programs, working papers, and follow-up tracking so they are not scattered across separate files.

Audithink is internal audit management software. Its features page lists program and working paper templates, management of findings, recommendations, and notices, and follow-up monitoring. The application does not perform technical testing of your systems and does not replace the auditor's judgment.

Frequently Asked Questions about ITGC

What does ITGC mean?

ITGC, or IT General Controls, are control policies and procedures that apply to all or most of an organization's information systems. Unlike application controls, which are embedded in a single application, ITGC create a reliable IT environment for all the applications on top of it.

What is the difference between ITGC and ITAC?

ITGC apply broadly across the IT environment, for example access management, change management, and backup. ITAC, or application controls, are embedded in a single application and control data input, processing, and output. The effectiveness of ITAC depends on ITGC working well.

What are the control categories in ITGC?

GAO's FISCAM groups general controls into five categories: security management, logical and physical access, segregation of duties, configuration management, and contingency planning. Auditors can choose the categories relevant to the engagement objectives and risks.

How do you test ITGC?

The auditor understands the IT environment, selects key controls based on risk, assesses their design, and then tests operation through inquiry, inspection, observation, and re-performance. Samples and evidence are recorded in the working papers, and deficiencies are then evaluated for impact.

Can internal auditors test ITGC themselves?

Yes, as long as the auditor has adequate IT competence or is supported by competent parties. Many organizations use specialist IT auditors or experts for the technical parts, while internal auditors focus on control design, evidence, and follow-up.

How often should ITGC be tested?

Frequency follows risk, system changes, and previous audit results. Many organizations test critical systems every year and reassess when there is a migration or a new application. There is no single frequency that applies to all organizations.

Conclusion

ITGC are the foundation of system reliability. Auditors who understand the five control categories, select key controls based on risk, and test with strong evidence will find it easier to judge whether data and automated controls can be trusted.

If your team wants to tidy up work programs, evidence, and follow-up of IT findings, schedule an Audithink demo.

Find out how the implementation of the audit application can have a positive impact on the company on an ongoing basis.

Consultation on Your Needs

Related Articles

Academic information system security audit
audit evidence management
data analytics audit